List hierarchy nodes (scoped, paged)
/portal/v1/accounts/{accountSlug}/applications/{appSlug}/environments/{envSlug}/nodesReturns one page of the caller's hierarchy for the current Environment as a flat list, each node carrying its parent_node_id and annotated with access_state, can_access, can_manage and its identity counts. A caller rebuilding the tree walks every page and links each node to its parent; a node whose parent is not in the listing is a top of the caller's scope. user principals (dashboard), which need the Console capability covering hierarchy.view, see every node; API-key principals see only what their access_mode/scopes grant — full_access unlocks everything, while scoped keys see nodes reachable via hierarchy.view. context_only nodes are the ancestors shown as the path to the caller's scope. Searches names and slugs with q; sorts by name or created (default, oldest first).
Authentication
AuthorizationJWT access token. Never send alongside X-API-Key: a request carrying both is refused.
env_structure.viewDeveloper ConsoleView the Environment's hierarchy tree and its schema. 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.
Query Parameters
pagenumber Optional Page number (1-based)
takenumber Optional Items per page (1-100, default 20)
qstring Optional Search node names and slugs
sort_byenum Optional Sort column. Defaults to `created`, oldest first.
orderenum Optional Sort direction
Responses
application/json
items *ScopedNodeResponseDto[]pagination *PageMetaDto
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.
Pagination
This endpoint returns a paginated collection. Use the query parameters below to page through results.
pagenumberPage number (1-indexed). Defaults to 1.
takenumberItems per page (1 to 100). Defaults to 20.
Each response includes an items array alongside a pagination object with item_count, page_count, has_previous_page, and has_next_page fields.
Returned object
curl -X GET "https://auth.canopy-io.com/portal/v1/accounts/value/applications/value/environments/value/nodes?page=0&take=0&q=value&sort_by=name&order=asc" \ -H "Authorization: Bearer $CANOPY_TOKEN"
{ "items": [ { "id": "string", "name": "string", "description": "string", "slug": "string", "node_type": "string", "parent_node_id": "string", "status": "string", "access_state": "accessible", "can_access": false, "can_manage": false, "version": 0, "direct_count": 0, "inherited_count": 0 } ], "pagination": { "page": 0, "take": 0, "item_count": 0, "page_count": 0, "has_previous_page": false, "has_next_page": false } }
Tell us how we can improve this guide.