Rename API token
Rename API token
Rename one of the authenticated user’s API tokens. Always allowed, regardless of plan.
PATCH
Rename API token
Authorizations
API key authorization. Pass your API key in the Authorization header as a Bearer token. Both new (gsk_*) and legacy (gsk-) API keys are accepted, e.g. Authorization: Bearer gsk_... or Authorization: Bearer gsk-....
Path Parameters
Body
application/json
Example:
"production-key"
Response
API token renamed successfully
Example:
"apiToken_abc123"
Example:
"ci-pipeline"
Public identifier of the key (the uuid in gsk__)
Display-only public head of the key (gsk_<keyId>). Contains no secret; safe to show truncated as gsk_<keyId>….
Example:
"gsk_3d4d7d38-a5ec-4d9f-94a6-5a3f61db9d7d"