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.Documentation Index
Fetch the complete documentation index at: https://docs.zavu.dev/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
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
