Deprecations

The API serves exactly one spelling of every operation: its path under the operation's product namespace, as listed in the endpoint reference. There are no aliases.

The policy

• A moved operation's old spelling is removed in the same coordinated release that ships the new one. There is no transition window, no sunset date, and no Deprecation or Sunset response header.
• A removed spelling is not a redirect. It is a path the API does not serve, so an authenticated request to it answers the ordinary 404 not_found. Without a credential you may see 401 instead, because authentication runs before routing. See Errors.
• A move changes where an operation lives, never what it does. Request and response bodies, ids and Idempotency-Key rules are the same under the new path.
• The published OpenAPI description lists canonical operations only, so a client generated from /api/v1/meta/openapi.json never calls a removed spelling.

Porting an older integration

If a call that used to work now answers 404, re-derive its path from the endpoint reference rather than adjusting the old one. The September 2026 moves are recorded, old path to new, in the API migration record. That page is a historical record: nothing on it is served.