Quick Start
1
Create a sub-account
2
Save the API key
The response includes the sub-account’s API key. The API returns it once
and has no way to return it again — store it when you receive it. If you
lose it, open the sub-account in the dashboard and show the key from its
API Keys screen, or create another key for it.
3
Your customer sends messages
Your customer uses their API key to send messages:
Guides
Creating Sub-Accounts
Provision sub-accounts with credit limits, external IDs, and metadata
Managing Sub-Accounts
Update settings, rotate API keys, and monitor spending
Deletion & Deactivation
Deactivate sub-accounts and understand the 14-day deletion grace period
Important Rules
- Sub-accounts share the team’s balance but are fully isolated
- Each sub-account has its own API keys, senders, phone numbers, contacts, and usage tracking
- Credit limits are optional — omit or set to
0for unlimited spending - When a credit limit is reached, the sub-account’s messages are blocked
- Deactivating a sub-account revokes all its API keys immediately
