Deactivate a Sub-Account (API)
TheDELETE /v1/sub-accounts/:id endpoint deactivates a sub-account immediately. All API keys are revoked and messaging stops.
Deactivation via the API revokes all API keys and sets the sub-account status to
pending_deletion. It schedules the same 14-day deletion as the dashboard: the sub-account is removed after 14 days unless it is restored from the dashboard first. Calling it again on a sub-account already pending_deletion changes nothing. To pause a sub-account without scheduling deletion, set its status to inactive with PATCH /v1/sub-accounts/:id instead (see Managing).Delete a Sub-Account (Dashboard)
Permanent deletion is available from the Zavu dashboard and follows a 14-day grace period to prevent accidental data loss.How It Works
1
Schedule deletion
From the dashboard workspace switcher, select the sub-account and choose “Delete”. This schedules deletion but does not remove any data yet.
2
API keys are revoked
All API keys for the sub-account are revoked immediately. The sub-account can no longer send or receive messages.
3
Email notifications
The team owner receives email notifications at multiple intervals:
4
Restore or wait
During the 14-day grace period, you can restore the sub-account from the dashboard. After 14 days, all data is permanently deleted.
Restoring a Deleted Sub-Account
If you change your mind during the 14-day grace period:- Open the dashboard workspace switcher
- Find the sub-account marked as “Pending Deletion”
- Click “Restore”
active status. You’ll need to create new API keys since the originals were revoked.
Deletion Rules
- You cannot delete the last active sub-account in a team. At least one project must remain active.
- The main account follows the same deletion rules as sub-accounts.
- Scheduled reminder emails are automatically cancelled if the sub-account is restored.
Deactivation vs Deletion
Next Steps
Creating Sub-Accounts
Create new sub-accounts to replace deactivated ones
Managing Sub-Accounts
Monitor spending and manage API keys