External API
Migrate from /api/ext
How existing integrations should move to /api/v1.
The older external API namespace remains available:
/api/extNew integrations should use:
/api/v1What Changed
The documented namespace changed. The current route behavior is otherwise compatible for the existing external surface:
| Old | New |
|---|---|
/api/ext/me/tenants | /api/v1/me/tenants |
/api/ext/workspaces | /api/v1/workspaces |
/api/ext/spots | /api/v1/spots |
/api/ext/users | /api/v1/users |
/api/ext/categories | /api/v1/categories |
/api/ext/statuses | /api/v1/statuses |
/api/ext/priorities | /api/v1/priorities |
/api/ext/teams | /api/v1/teams |
/api/ext/templates | /api/v1/templates |
/api/ext/tags | /api/v1/tags |
/api/ext/tasks | /api/v1/tasks |
/api/ext/task-comments | /api/v1/task-comments |
/api/ext/task-assignments | /api/v1/task-assignments |
/api/ext/task-tags | /api/v1/task-tags |
/api/ext/task-logs | /api/v1/task-logs |
/api/ext/task-approval | /api/v1/task-approval |
/api/ext/task-acknowledgment | /api/v1/task-acknowledgment |
HTTP methods, request payloads, response shapes, API-key headers, scopes, and tenantId requirements are unchanged by the namespace migration.
Migration Steps
- Change the base path from
/api/extto/api/v1. - Keep the same authentication header.
- Keep passing
tenantIdwhere required. - Verify reference-data reads.
- Verify task reads and writes in a safe tenant or sandbox.
- Update external system logs and runbooks to use
/api/v1.
Compatibility Window
/api/ext is compatibility-only. Do not build new features against it. Any future removal should be announced in the API changelog.