Skip to main content
PATCH
Update an existing key’s name or expires_at. Send only the fields you want to change — you must include at least one of them, or the request is rejected with 400. The key’s secret is never changed and is never returned, so editing a label or expiry doesn’t interrupt anything authenticating with the key. A successful update returns 204 No Content.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

Identifier of the API key to update (a UUID).

Body

application/json

Provide at least one of name or expires_at.

name
string

New label for the key. If supplied it must be non-empty (400 otherwise). Omit to leave the current label unchanged.

Example:

"production-pipeline-v2"

expires_at
string<date-time>

New expiry timestamp (RFC 3339). Use this to extend, shorten, or set an expiry on a previously non-expiring key. Omit to leave the current expiry unchanged.

Example:

"2027-01-31T23:59:59Z"

Response

API key updated. The response body is empty.