Update hierarchy schema for the active Environment
/portal/v1/accounts/{accountSlug}/applications/{appSlug}/environments/{envSlug}/hierarchy-schemaReplaces the active Environment's hierarchy schema wholesale with the supplied node_types, allowed_children map, max_depth (1–16), and root_node_type (which must be one of node_types). The update targets the Environment resolved from the principal context. Pass the Environment's current version in the If-Match header for optimistic locking — a stale value returns 409. The persisted schema is re-read and returned in the response. Requires the hierarchy.manage permission.
Authentication
AuthorizationJWT access token. Never send alongside X-API-Key: a request carrying both is refused.
applications.manageDeveloper ConsoleCreate, edit, and delete Applications and Environments. 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 Headers
if-matchrequired
Request body
application/json
node_typesstring[] Required Allowed node types (e.g. ['region', 'district', 'team']). Order is informational, not structural — parent/child rules are governed by `allowed_children`. Names starting with `canopy:` are reserved; with organizations enabled the list starts with `canopy:organization`.
allowed_childrenobject Required Map from node type to allowed child node types. An empty array makes that type a leaf: nothing may be created or moved beneath it. A type the map does not mention accepts any child.
max_depthnumber Required Maximum nesting depth (root counts as depth 1).
root_node_typestring Required Node type used when the root node is auto-created. Must be one of `node_types`.
Responses
application/json
data *HierarchySchemaResponseDto
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/hierarchy-schema" \ -H "if-match: value" \ -H "Authorization: Bearer $CANOPY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "node_types": [ "string" ], "allowed_children": { "region": [ "district" ], "district": [ "team" ], "team": [] }, "max_depth": 0, "root_node_type": "string" }'
{ "data": { "node_types": [ "string" ], "allowed_children": {}, "max_depth": 0, "root_node_type": "string" } }
Tell us how we can improve this guide.