Skip to main content
PATCH
Update API key

Authorizations

Authorization
string
header
required

Use a JWT bearer token or a Veryfront API key in the Authorization header.

Path Parameters

id
string<uuid>
required

Body

application/json
name
string
Required string length: 1 - 255
expires_at
string | null

Response

API key updated successfully

id
string<uuid>
required
project_id
string<uuid> | null
required
user_id
string<uuid>
required
name
string
required
key_prefix
string
required
last_used_at
string | null
required
expires_at
string | null
required
created_at
string
required
updated_at
string
required
status
enum<string>
required
Available options:
active,
expired,
revoked
revoked_at
string | null
required
scopes
string[]
required
scope
enum<string>
required

Whether the key is restricted to one project or applies to the account. An account-wide key acts with its owner’s project roles, limited by the key’s scopes. Unlike project-scoped keys, it can inherit the owner’s administrative authority: write can allow API key creation, and delete can allow project deletion.

Available options:
account,
project