Subaccount
Was ist Subaccount?
Dieser Eintrag liegt derzeit nur auf Englisch vor.
A subaccount is a full organization of its own created under a parent organization — with its own plan, API keys, users, senders, and wallet — linked to the parent by a single parent pointer (nesting stops there: a subaccount cannot parent another). It lets a platform, agency, or reseller separate billing, traffic, and per-resource attribution between its own customers without giving up control of the parent organization.
More detail
Every API key is issued against exactly one organization, and the auth layer resolves that key to its org — parent or subaccount — on every request, so traffic, billing, and per-resource attribution stay partitioned between subaccounts.
The parent funds each subaccount with credit transfers into its separate wallet and can cap it with `monthly_spend_cap_cents`, so each subaccount runs under its own budget ceiling without the parent's own sends sharing that wallet.
Because a subaccount cannot parent another, the hierarchy stays one level deep — that is the entire tenancy tree Orbit enforces, no recursive nesting to audit.
Häufige Fragen
- Does a subaccount have separate billing from its parent?
- Yes — each subaccount has its own plan and its own wallet, funded by credit transfers the parent initiates, so in-flight sends and charges never pool across subaccounts. The parent can also enforce a monthly spend cap on each subaccount's usage.
- Can a subaccount itself have subaccounts?
- No — the tenancy tree on Orbit is one level deep by design. A parent organization can own one or more subaccounts, but a subaccount cannot parent another, which keeps attribution and billing visibility simple to audit.
See also
Build it on Orbit
Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.