Skip to main content
Sub-accounts let you provision isolated messaging environments for each of your customers. Each sub-account gets its own API key, usage tracking, and optional spending cap — while all charges are billed to your team’s balance.

Quick Start

1

Create a sub-account

2

Save the API key

The response includes the sub-account’s API key. This is only shown once.
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

Each team can have only one main account. All additional projects must be created as sub-accounts. If you need a separate main account, create a new team.
  • 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 0 for 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