vobiz-sub-accounts
Installation
SKILL.md
Vobiz Sub-Accounts skill
Use this when the user wants to isolate environments (dev/staging/prod), separate teams (sales vs support), or carve their account into business units with independent credentials, numbers, and CDR streams under the same parent invoice — and, for customer_use sub-accounts, verify each customer's own KYC before it can place calls.
Difference from Partner sub-accounts
| Sub-Account | Partner customer account | |
|---|---|---|
| Parent | Your own account | Partner account |
| Billing | Rolled into parent invoice | Separate wallet, transferred from partner |
| KYC | personal_use inherits parent's; customer_use does its own |
Requires its own KYC |
| API | /api/v1/accounts/{auth_id}/sub-accounts/* |
/api/v1/partner/accounts/* |
If the user wants to resell to external customers, they need the Partner API (see vobiz-partner-api skill). Sub-accounts are for internal segmentation or for vending a customer_use tenant that runs its own KYC.
Two credential pairs (the rule that prevents most bugs)
- Parent
X-Auth-ID/X-Auth-Token(MA_…): used for all provisioning and administration — CRUD on sub-accounts, all KYC calls, buying/assigning numbers. The sub-account is named by{sub_auth_id}in the URL. - Sub-account
auth_id/auth_token(SA_…): returned once at creation; the sub-account's runtime key for placing/receiving calls and pulling its own CDRs.