List the roles an organization may assign
/api/v1/organizations/{id}/rolesThe active, assignable roles the organization can use, the Environment's and its own, for choosing a member's role or an invitation's and for the organization's roles page. Each carries grantable, whether the caller may grant it at the organization node under the grant ceiling (always true for the developer's key), and holder_count, how many people in the organization hold it at its node or beneath. System roles are left out, since they cannot be assigned. Requires hierarchy.view, or canopy:organization.manage, canopy:access.manage or canopy:roles.manage at the organization node. The response is an unpaginated { items } array.
Authentication
Authorization Option A JWT access token. Never send alongside X-API-Key: a request carrying both is refused.
X-API-Key Option B API key for management-tier access. Never send alongside an Authorization header: a request carrying both is refused.
hierarchy.viewHierarchyView hierarchy nodes. A scoped API key must hold it as a scope; a full-access key holds every scope within its Environment except the named-only and account scopes; a developer's token needs the Console capability that covers it. A credential without it is refused with 403.
Path Parameters
idstring Required Headers
X-Canopy-EnvironmentThe id of the Environment this request acts in. Required with an account API key, which belongs to the Account and names its Environment per request; an Environment key may send it only to name its own Environment. A missing header for an account key answers `400` (`api_key.environment_required`), one naming no Environment of the key's Account `400` (`api_key.environment_not_found`), and one naming another Environment than an Environment key's own `400` (`api_key.environment_mismatch`).
Responses
application/json
items *OrganizationRoleResponseDto[]
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. A request refused by an authorization check answers 403 with the code authorization.denied, and its data names the denial_reason and the permission checked.
authorization.deniedForbiddenThe credential does not hold the permission this operation checks: a scoped API key without the scope, a developer without the Console capability that covers it, or a permission granted somewhere other than the node the request targets. The error's data names the permission.
Add the permission named in the Authentication section to the key's scopes, or ask an account administrator to grant the covering capability, then retry. For a node-scoped operation, make sure the grant reaches the node you are acting on.
Returned object
curl -X GET "https://auth.canopy-io.com/api/v1/organizations/value/roles" \ -H "X-Canopy-Environment: value" \ -H "X-API-Key: $CANOPY_API_KEY"
{ "items": [ { "id": "string", "name": "string", "scope": "environment", "organization_node_id": "string", "organization_name": "string", "template_id": "string", "description": "string", "is_system_role": false, "system_key": "string", "is_active": false, "created_at": "2026-04-20T12:00:00.000Z", "updated_at": "2026-04-20T12:00:00.000Z", "version": 0, "permission_count": 0, "member_count": 0, "administers": false, "grantable": false, "holder_count": 0, "is_default_member": false } ] }
Tell us how we can improve this guide.