Create a new Sub-Account API
Create a new sub-account using the Bolna API to define separate workspaces with custom configurations for enterprise-level management.
enterprise feature.You can read more about our enterprise offering here Bolna enterprise.Concurrency
Every sub-account is created with a concurrency envelope:min_concurrency— concurrency guaranteed to this sub-account even when the organization is at capacity. Use0for no guarantee.max_concurrency— the sub-account’s hard cap. Omit it for an elastic sub-account that can burst into the organization’s unused capacity; set0to pause the sub-account.
400 if the per-account minimums or maximums would exceed the organization’s envelope. See Concurrency management for how guarantees, caps, and shared capacity work together.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Payload for creating a new sub-account
Name of the sub-account
"alpha-007"
Guaranteed concurrency reserved for this sub-account even when the organization is at capacity. 0 means no guarantee.
5
Hard cap on this sub-account's concurrency. Omit (or send null) for an elastic account that can burst into the organization's unused capacity. 0 pauses the sub-account.
20
The sub-account is stored in a separate database
Database host for multi_tenant sub-account
"prod-alpha-007-db-east-1.my-database.com"
Database name for multi_tenant sub-account
"alpha-007_db"
Database port for multi_tenant sub-account
5432
Database root user for multi_tenant sub-account
"alpha-007_user"
Database root password for multi_tenant sub-account
"alpha-007_password"
Response
Sub-account create response
Unque identifier for the created sub-account
Name of the sub-account
"alpha-007"
ID of the user who created the sub-account
Organization ID the sub-account belongs to
Sub-account API Key used to interact with sub-account resources like agents, executions, batches, etc.
^sa-[a-f0-9]{32}$"sa-b33f4fbf011d4661a273a46b11d185f8"
Whether the sub-account is being stored in a separate database
false
Database host if the sub-account is multi_tenant:true
null
Database name if the sub-account is multi_tenant:true
null
Database port if the sub-account is multi_tenant:true
null
Database root user if the sub-account is multi_tenant:true
null
Database root password if the sub-account is multi_tenant:true
null
Guaranteed concurrency reserved for this sub-account even when the organization is at capacity. 0 means no guarantee.
5
Hard cap on this sub-account's concurrency. Omit (or send null) for an elastic account that can burst into the organization's unused capacity. 0 pauses the sub-account.
20
Timestamp of sub-account creation
"2025-01-23T01:14:37Z"
Timestamp of sub-account updation
"2025-01-23T01:14:37Z"

