Create sub account
Opens a workspace for a client, beneath this one.
posthttps://api.integrable.cloud/api/workspace/sub-accounts
- Authentication
- Bearer token
- Retries
- Idempotency-Key
- Body
- application/json
- Version
- 2026-09-03
Nobody is added to it. The client gets access by accepting an invitation; until then the agency administers it through this workspace, or by entering it with POST /api/auth/switch-organization. See app/domains/tenancy/service.py for why a membership would be the wrong mechanism.
A plan feature: 402 plan_feature_required below Agency. Existing client workspaces are never taken away by a downgrade - only opening new ones is gated.
Headers#
Request body#
Responses#
Errors#
Failures use one envelope on every endpoint, described in Retries, versioning and limits. The codes you are most likely to meet here:
validation_error· 422 — The payload was well-formed JSON but failed schema validation.unauthenticated· 401 — The request carried no API key, or one the API could not verify.forbidden· 403 — The key is valid, but it is not allowed to do this — either the scope is missing or the resource belongs to another workspace.idempotency_key_reused· 422 — This `Idempotency-Key` was used before, for a request with a different body.rate_limited· 429 — Too many requests in the current window. The limit is per workspace, and some endpoints add a per-agent limit on top.
More Workspace endpoints#
Something unclear or missing? Tell us and we’ll fix it.