Skip to main content
You must use a main account API key to create sub-accounts. Sub-account API keys cannot create new sub-accounts (no nesting) and receive HTTP 403 if they try.

Create a Sub-Account

Parameters

Response

The API key is only returned in the creation response. Store it securely.
The apiKey field is only included in the creation response. If you lose it, you’ll need to create a new API key for the sub-account.

Credit Limits

Credit limits act as a spending cap in cents. When a sub-account’s totalSpent reaches the creditLimit, all messaging is blocked.
Credit limits protect your balance from unexpected usage. You can update or remove them at any time via PATCH /v1/sub-accounts/:id.

External IDs

The externalId field lets you map sub-accounts to your own system:
This is useful for:
  • Mapping sub-accounts to your CRM records
  • Billing reconciliation
  • Audit trails

Metadata

Store arbitrary key-value data with the sub-account:

One Main Account Rule

Each team is limited to one main account. All additional projects must be sub-accounts.
If you try to create a second main account, the API returns an error:

Next Steps

Managing Sub-Accounts

Update credit limits, rotate API keys, and monitor spending

Deletion & Deactivation

Deactivate sub-accounts and understand the grace period