Skip to main content
PATCH
cURL
This is a partial update — send only the fields you want to change. The following can be updated:
  • name
  • min_concurrency — guaranteed concurrency floor (0 = no guarantee)
  • max_concurrency — hard cap; omit to leave unchanged, send null to make the sub-account elastic, 0 to pause it
Only organization admins can update sub-accounts. Omitting a concurrency field leaves it unchanged; the edit is rejected with 400 if it would break the organization’s concurrency 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.

Path Parameters

sub_account_id
string<uuid>
required

The sub-account ID (UUID).

Body

application/json

Fields to patch on the sub-account.

name
string

Name of the sub-account

Example:

"alpha-007"

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

Response

Updated sub-account