Update Sub-Account API Key
Updates the label and scopes for an API key owned by a sub account. Updated scopes are validated against the child account.
Authorizations
API key for authentication
Path Parameters
Parent account ID
Sub account ID
API key ID
Body
- Option 1
- Option 2
- Option 3
At least one non-null field must be provided, and at least one provided value must differ from the current value. Omitted or null fields are left unchanged.
Human-readable label for the API key. Omit to keep the existing label.
1 - 255Array of scope strings to grant to this API key
1Replacement list of allowed source IPs (CIDR blocks or bare IPv4/IPv6 addresses; canonicalized and de-duplicated, at most 100 entries, allow-all prefixes 0.0.0.0/0 and ::/0 rejected). Omit the field or send null to leave the existing list unchanged; send an empty array to clear it (key usable from any IP); send a non-empty array to replace it.
Response
Sub-account API key updated successfully
Object type identifier
api_key Unique identifier for the API key
When the API key was created
When the API key was last updated
Account ID this API key belongs to
Human-readable label for the API key
Public portion of the API key
Scopes granted to this API key
Source IPs allowed to authenticate with this API key, as canonical CIDR blocks (a bare address is stored as a /32 for IPv4 or /128 for IPv6). Always present; an empty array means the key may be used from any source IP. When non-empty, an authenticated request whose client IP is not covered by an entry is rejected with HTTP 403 on every v2 endpoint, regardless of the key's scopes.
When the API key was last used (updates every 5-10 minutes)
Secret key. Only returned when an API key is created, including exact idempotent replays of create requests within the 5-minute secret-bearing replay window. Store it immediately; list, get, update, and delete responses omit it.

