Create Sub-Account API Key
Creates an API key owned by the sub account. Parent credentials must belong to the parent account and include sub-account-api-keys:write; sub-account credentials cannot manage nested API keys. The returned secret_key authenticates as the child account and should be stored immediately.
Bootstrap example:
- Create the sub account with
POST /v2/accounts/{account_id}/sub-accountsand a uniqueIdempotency-Key. - Create the bootstrap child API key with this endpoint and a different unique
Idempotency-Key. - Store the one-time
secret_keyfrom the201response. Exact idempotent replays within 5 minutes return the samesecret_key. - Use that child secret with the child
sub_account_idas theaccount_idon ordinary v2 routes.
Authorizations
API key for authentication
Headers
Optional idempotency key for safe request retries. Must be a unique string for each logical request.
Requests with the same key will return the same response. Keys for non-secret responses expire after 24 hours.
API-key create responses include a one-time secret_key, so their encrypted replay responses expire after 5 minutes.
255Path Parameters
Parent account ID
Sub account ID
Body
Response
Sub-account API key created 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
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.

