Update an organization
/portal/v1/accounts/{accountSlug}/applications/{appSlug}/environments/{envSlug}/organizations/{id}Updates an organization's name, description, metadata, and/or external_id (null clears it; a value already used by another organization in the Environment answers 409 organization.external_id_conflict) by id. The slug is frozen at create and never changes. Supports optimistic concurrency via the If-Match header carrying the organization's current version (409 on a version mismatch). Requires the hierarchy.manage permission at the organization and emits organization.updated.
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.
idstring Required Headers
If-MatchOptimistic-lock version of the resource. Send the `version` field returned on read; the server rejects with 409 if the row has changed since.
Request body
application/json
namestring Optional New organization name. The slug does not change.
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, unique per Environment. `null` clears it.
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 PATCH "https://auth.canopy-io.com/portal/v1/accounts/value/applications/value/environments/value/organizations/value" \ -H "If-Match: "3"" \ -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.