Skip to main content
POST
Scope: nft:orders Issues a new key for the same program, with the same scopes. No body; an Idempotency-Key is required. Call it with your current key.
  • The old key keeps working for 24 hours (previous_key.expires_at), then answers 401. Move every server to the new key within that window.
  • Store key.secret straight away. If the response is lost, call again with the same old key and the same Idempotency-Key within 10 minutes, before you use the new key: you get the same new key and secret back. After that (or once the new key has made a call) the replay is 409 ALREADY_ROTATED, so a leaked old key can never fetch the new one.
  • A key is rotated once. Rotating it again with a different Idempotency-Key is 409 ALREADY_ROTATED, with the successor; rotate the new key next time.
  • Your webhook moves with the rotation. The new key takes over the old key’s webhook (same URL, same secret), and the old key’s stops, so deliveries never pause and you change nothing.
  • If you rotated because a key may have leaked, call Revoke the previous key with the new key once every server uses it.
string
required
8-128 characters of A-Za-z0-9_-.

Response

201 (200 with "idempotent_replay": true on a replay).
object
The new key: id, name, secret (cb_live_..., shown only here) and created_at.
object
The key you called with: id and expires_at, 24 hours from now.
boolean
Present and true on a replay.

Errors