About SubAccounts
SubAccounts enable partner organizations (called parent accounts) to provision isolated, white-labeled PandaVideo environments for their own clients. Each sub-account has its own videos, players, and credit balance — but is managed and billed through the parent account.
Interested in SubAccounts?SubAccounts is part of a specific plan. If you'd like to join this plan or learn more about the feature, get in touch with Panda Video support through your dashboard: https://dashboard.pandavideo.com.br/#/videos.
The parent/sub-account model
- A parent account creates sub-accounts and controls their credit, storage, and traffic limits.
- Each sub-account is a full PandaVideo workspace (videos, folders, players, domains).
- Sub-accounts are linked via
parent_organization_id— this is the trust anchor for all authorization checks. - API calls that target a sub-account always require the parent's API token, never the sub-account's own token.
Lifecycle & states
A sub-account goes through the following states (field: status):
| Status | Value | Meaning |
|---|---|---|
| Creating | creating | Being provisioned after creation |
| Active | active | Fully operational |
| Inactive | inactive | Disabled by parent (stored as blocked on the backend) |
| Blocked | blocked | Disabled by PandaVideo (billing) |
| Error | error | Provisioning/billing error — the only state from which a sub-account can be deleted |
Limits & billing
- Credits are the internal billing unit — each video-processing minute costs a certain number of credits.
- The parent transfers credits to sub-accounts (
POST /user/limit/transfer_creditswithtype: transfer). - The parent can redeem unused credits back (
type: redeem). - A sub-account cannot purchase credits on its own — all billing flows through the parent.
Sub-accounts cannot:Purchase credits, manage their own billing, create other sub-accounts, or access the parent account's resources. They operate within the boundaries set by the parent.
Authorization summary
All actions below require the parent's API token.
| Action | Method & Path |
|---|---|
| Create sub-account | POST /organizations?action=create-sub-account |
| Update sub-account | PUT /organizations/update_subaccount |
| Delete sub-account | DELETE /organizations?action=delete-sub-account |
| Transfer / redeem credits | POST /user/limit/transfer_credits |
| List usage & limits | GET /user/limit/sub_accounts_usage |
| Create live stream key | POST /live_stream_key |
| Update / reset live stream key | PUT /live_stream_key/{id} |
| Delete live stream key | DELETE /live_stream_key/{id} |
| Manage sub-account API key | POST/GET/DELETE /user/apikey |
What's next
- Create SubAccount — provision a new isolated workspace for a client
- Update SubAccount — change name, limits, or status
- Delete SubAccount — remove a sub-account (only in
errorstatus) - Transfer Credits — move credits between parent and sub-accounts
- List SubAccounts Usage — check credit balances and limits
- Create / Update / Delete Live Stream Key — manage a sub-account's live keys
- Create / Get / Delete SubAccount API Key — manage programmatic access for a sub-account