POST /api/v2/accounts/create-child
Availability
Creates a new account under your organization. Requires theADMIN role on
the organization and an accepted package with an unused account slot. If your
account is standalone, the package must include at least two account slots. You
must also be its direct administrator and explicitly confirm creation of a new
organization. Present the consequences below and send the confirmation as
exactly true.
The organization created by this conversion is a billing and access container,
not a Buyer or Seller account. Your current contract and billing authority
move to it, and you become its first administrator. The existing account keeps
its role, resources, and direct members; organization administrators can manage
both accounts, while direct account members gain no organization authority.
Any account-specific standing remains an override; otherwise the account
inherits organization standing. Detachment is not self-service because it
requires a dedicated legal, billing, standing, and administrator migration.
Only a newly created SELLER account receives a new storefront.
A new BUYER account can enter Buyer Setup immediately. Its demo, real-work,
direct-spend, and Apostra-spend capabilities are derived from Organization
proof, Terms, plan/entitlements, standing, and transaction route; no separate
admission flips the Account live.
The confirmation controls whether a fresh standalone conversion may begin. If
a matching idempotencyKey receipt has already committed the organization and
account hierarchy, retrying with that same key resumes required administrator
access, contract transfer, deprecated Buyer compatibility projections, and account-view repairs even
when confirmOrganizationConversion is omitted or false. The retry cannot
cancel or reverse authority that has already moved. Reusing the key with
incompatible input still returns 409 Conflict.
Request
Parameters
Response
buyerAccessPosture remains in this response only as a deprecated compatibility
projection and must not be used for authorization. Read Buyer Setup capabilities.
Errors
400 VALIDATION_ERROR— missingname/customerRole, or a malformedcustomerDomain.401 UNAUTHORIZED— authentication is missing or invalid.403 ACCESS_DENIED— caller is not an administrator, or the organization has no active package granting account capacity.409 CONFLICT— no account slot remains, a fresh standalone conversion omittedconfirmOrganizationConversion: trueor sentfalse, or the request reused an idempotency key with incompatible input. A matching same-key retry after the hierarchy committed resumes instead of returning this confirmation error.
Related
Account tasks
All account operations
Delete account
Remove an empty account
List accounts
See the new account