Rotate an API key

Agent-driven key rotation: mints a replacement key bound to the SAME account and revokes key_id in one call -- an autonomous agent rotates its own credential without an operator or a human seat in the loop, so usage keeps billing to the account. Scoped to the caller's own customer; key_id need not be the presented key. 404 for an id that doesn't exist, belongs to another tenant, or is already revoked -- indistinguishable, same as delete_key.

scopes, omitted, keeps key_id's own scopes -- rotation replaces a credential, it never widens a narrowed one. Requested or kept, they must be a subset of the PRESENTING key's scopes (key_id need not be the presenting key), else 403 naming the excess.

Requires the account scope.

post/v1/keys/{key_id}/rotate

Request

  • Base URL: https://api.reqbeat.com
  • URL: https://api.reqbeat.com/v1/keys/{key_id}/rotate
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

key_idinteger required

The API key's id, as returned by GET /v1/keys.

Request body

scopesstring[] nullable

Response

Successful Response

idinteger required
keystring required
customer_idstring required
account_idinteger required
tierstring required
scopesstring[] required

Changes

No recorded changes to this operation across all 1 revision of this API.