Skip to main content
POST
cURL
This is an enterprise feature.You can read more about our enterprise offering here Bolna enterprise.
Only organization admins can create sub-accounts.

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. Use 0 for 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; set 0 to pause the sub-account.
The request is rejected with 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

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Payload for creating a new sub-account

name
string
required

Name of the sub-account

Example:

"alpha-007"

min_concurrency
integer
required

Guaranteed concurrency reserved for this sub-account even when the organization is at capacity. 0 means no guarantee.

Example:

5

max_concurrency
integer

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.

Example:

20

multi_tenant
boolean
default:false

The sub-account is stored in a separate database

db_host
string

Database host for multi_tenant sub-account

Example:

"prod-alpha-007-db-east-1.my-database.com"

db_name
string

Database name for multi_tenant sub-account

Example:

"alpha-007_db"

db_port
string

Database port for multi_tenant sub-account

Example:

5432

db_user
string

Database root user for multi_tenant sub-account

Example:

"alpha-007_user"

db_password
string

Database root password for multi_tenant sub-account

Example:

"alpha-007_password"

Response

Sub-account create response

id
string<uuid>

Unque identifier for the created sub-account

name
string

Name of the sub-account

Example:

"alpha-007"

user_id
string<uuid>

ID of the user who created the sub-account

organization_id
string<uuid>

Organization ID the sub-account belongs to

api_key
string

Sub-account API Key used to interact with sub-account resources like agents, executions, batches, etc.

Pattern: ^sa-[a-f0-9]{32}$
Example:

"sa-b33f4fbf011d4661a273a46b11d185f8"

multi_tenant
boolean

Whether the sub-account is being stored in a separate database

Example:

false

db_host
string

Database host if the sub-account is multi_tenant:true

Example:

null

db_name
string

Database name if the sub-account is multi_tenant:true

Example:

null

db_port
string

Database port if the sub-account is multi_tenant:true

Example:

null

db_user
string

Database root user if the sub-account is multi_tenant:true

Example:

null

db_password
string

Database root password if the sub-account is multi_tenant:true

Example:

null

min_concurrency
integer

Guaranteed concurrency reserved for this sub-account even when the organization is at capacity. 0 means no guarantee.

Example:

5

max_concurrency
integer

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.

Example:

20

created_at
string<date-time>

Timestamp of sub-account creation

Example:

"2025-01-23T01:14:37Z"

updated_at
string<date-time>

Timestamp of sub-account updation

Example:

"2025-01-23T01:14:37Z"