Rotate the presenting API key

Issues a new secret for the ServiceAccount API key that authenticates this request; the old secret is invalidated immediately. Only ServiceAccount API keys may call it; sessions, including sessions minted by a ServiceAccount, are refused with 403. No scope is required. Idempotency-Key is required. The new secret is returned once. If the response is lost, retrying cannot recover it, because the old secret no longer authenticates: another authorized administrator (a Person admin, or a ServiceAccount that manages this ServiceAccount's keys) must rotate the key. There is no automatic recovery. When two rotations of the same key race, one succeeds and the other fails with 409.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Headers
string
required
length between 1 and 255
^[\x21-\x7e]{1,255}$

REQUIRED. Rejects a duplicate rotation sent at the same time with the same key. It cannot recover a lost response: the old secret stops working as soon as the rotation succeeds. Use 1-255 printable ASCII characters.

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json