Skip to main content
PATCH
Change an API key's scopes

Authorizations

Authorization
string
header
required

Pass your secret key in the Authorization header as a Bearer token: Authorization: Bearer sk_test_... (sandbox) or Bearer sk_live_... (production).

Keys are created in the developer portal and the plaintext secret is shown exactly once at creation. Treat them like passwords — never embed them in mobile apps or front-end code.

Path Parameters

api_key_id
string
required

Body

application/json
scopes
string[]
required

The complete scope set the key should carry from now on.

Minimum array length: 1

Response

The updated key.

id
string
required

Plain UUID v4 (e.g. 15a81d54-0471-...). No prefix is applied today. SDKs should treat the value as opaque.

Example:

"15a81d54-0471-4f3c-9c1f-2f0a0c7b8d31"

environment
enum<string>
required
Available options:
sandbox,
live
prefix
string
required

First few characters of the key, safe to display in lists and logs (the rest is irrecoverable after creation).

Example:

"sk_test_a89d15d0"

scopes
enum<string>[]
required
Available options:
read:clients,
write:clients,
read:connections,
write:connections,
read:accounts,
read:transactions,
read:statements,
write:statements,
read:checks,
manage:webhooks,
read:webhooks,
write:webhooks,
read:api-keys,
write:api-keys
status
enum<string>
required
Available options:
active,
revoked
created_at
string<date-time>
required
last_used_at
string<date-time> | null
revoked_at
string<date-time> | null