Getting Started with Twilio Accounts and Subaccounts

Twilio Console allows users to create two different types of accounts: Accounts and Subaccounts.


Twilio Accounts (sometimes referred to as "projects" are separate accounts with their own resources and account balance. Many customers use multiple accounts for building out different use cases, segregating data for different development lifecycle phases, or when they need to control user access. New accounts are recommend for creating PCI compliant payment processing apps with the <Pay> TwiML verb, and required for setting up a Twilio Flex instance.

Twilio Accounts can be be created and accessed via Console. For more details, please see our article View and Create New Accounts in Twilio Console.


Subaccounts have their own resources, but are owned by another account, and share that balance. Subaccounts are recommended mainly for independent software vendors (ISVs) to separate usage from their different customers. They may also be a better fit for customers who already have a large number of existing Twilio phone numbers and short codes, or for those using reporting APIs to organize their usage outside of Console.

Subaccounts can be created and accessed via Console, but can also be managed via the REST API. For more details, please see our article View and Create New Twilio Subaccounts.


  Accounts Subaccounts
Who is it for? All Twilio customers  ISVs
Why should you use it? Segregate production and dev environments, new use cases, or new products like Flex and <Pay>. Separate usage from your customers, while keeping only 1 billing account.
How is it billed? Each Account has its own balance. Subaccounts are owned by a single Account with a single shared balance.
Where is it managed? Twilio Console Twilio Console, or the REST API
How many can I have? 10 maximum * 1,000 maximum *

*If you're worried about approaching this limit, please contact our Support team to inquire about raising it.

Have more questions? Submit a request
Powered by Zendesk