Create an organization
/portal/v1/accounts/{accountSlug}/applications/{appSlug}/environments/{envSlug}/organizationsCreates an organization from a name (slug auto-derived, display-only) with optional description, metadata, and external_id (your own id for it, unique per Environment; a repeat answers 409 organization.external_id_conflict, so create-then-store is idempotent). The Environment must have organizations enabled (409 organization.not_enabled otherwise); the container is independent of the access model, so flat and hierarchy Environments both hold organizations. Requires the hierarchy.manage permission and emits organization.created.
Authentication
AuthorizationJWT access token. Never send alongside X-API-Key: a request carrying both is refused.
env_organizations.manageDeveloper ConsoleSwitch the organizations container on and off and create, rename, and delete organizations. Granted through an administrator role in the Admin Workspace; a valid token without it is refused with 403.
Path Parameters
accountSlugstring Required The Account's slug. An unknown one answers 404.
appSlugstring Required The Application's slug within the Account.
envSlugstring Required The Environment's slug within the Application.
Request body
application/json
namestring Required Organization name. The slug is auto-derived from it at create and never changes afterwards.
descriptionstring Optional Organization description
metadataobject Optional Free-form metadata stored on the organization, returned as sent.
external_idstring Optional Your own id for this organization (the account id in your database), unique per Environment. Look the organization up with `GET /api/v1/organizations?external_id=...`; a second create with the same value answers 409, so create-then-store is idempotent.
Responses
application/json
data *OrganizationResponseDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
application/json
error *ApiErrorBodyDto
Errors
When the request can't be completed, the response body includes a stable error code you can branch on, and a correlation_id (also sent as the X-Correlation-Id header). Quote the correlation id when you contact support: it identifies the exact request in Canopy's logs.
account.capability_requiredForbiddenThe signed-in user's administrator roles do not grant the capability this endpoint requires.
Ask an account administrator to grant a role carrying the capability named in the Authentication section, then retry.
Returned object
curl -X POST "https://auth.canopy-io.com/portal/v1/accounts/value/applications/value/environments/value/organizations" \ -H "Authorization: Bearer $CANOPY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "name": "string", "description": "string", "metadata": {}, "external_id": "string" }'
{ "data": { "id": "string", "name": "string", "description": "string", "slug": "string", "metadata": {}, "external_id": "string", "member_count": 0, "pending_invite_count": 0, "created_at": "2026-04-20T12:00:00.000Z", "updated_at": "2026-04-20T12:00:00.000Z", "version": 0 } }
Tell us how we can improve this guide.