Pin account to a version
Pin the authenticated account’s default API version to target_version. Pins are forward-only: you can move to a newer version, but a target_version older than your current pin is rejected with 400. An unsupported target_version also returns 400. The call is idempotent — pinning to the version you are already on is a safe no-op. On success the API returns 200 with your previous_version and current_version. Once pinned, the X-Api-Version header becomes optional on later requests (your pin is the default), though the header still wins per-request when sent. See the Versioning guide for the full resolution order.
Authorizations
Access token from POST /auth (the data.access_token value).
API key issued by Kira. Required on every request, including /auth.
Headers
Optional. The date-versioned API version to apply for this request (e.g. 2026-04-14). When sent it always wins, even over your pinned account default. When omitted, the API uses your account's pinned version if set, otherwise a baseline default.
"2026-06-01"
Body
The date-versioned API version to pin your account to (e.g. 2026-04-14). Must be a supported version and not older than your current pin — downgrades and unknown versions return 400.
"2026-06-01"
Response
Account pinned. Returns your version pin before and after the upgrade.