Bind an SSO connection to an organization
/portal/v1/accounts/{accountSlug}/applications/{appSlug}/environments/{envSlug}/organizations/{id}/sso-connectionsBinds an end_user SSO connection to the organization: a login through the connection lands in this organization, joining as a member with default_role_id when the identity is provisioned or is not yet a member, and the session starts here. The connection must already be bound to the organization's Environment (that binding routes the email domain), and the role must be an active, non-system role of the Environment (400 otherwise: rbac.role_inactive or rbac.role_system_not_assignable). A connection binds to one organization per Environment (409). Requires the hierarchy.manage permission at the organization and emits organization.sso_connection.bound.
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 Request body
application/json
sso_connection_idstring Required An end-user SSO connection already bound to the organization's Environment.
default_role_idstring Required The membership role a login through this connection receives when it joins the organization. Must belong to the organization's Environment.
Responses
application/json
data *OrganizationSsoConnectionResponseDto
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/value/sso-connections" \ -H "Authorization: Bearer $CANOPY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "sso_connection_id": "string", "default_role_id": "string" }'
{ "data": { "organization_node_id": "string", "sso_connection_id": "string", "sso_connection": { "id": "string", "name": "string", "type": "saml", "status": "string", "owner_organization_node_id": "string" }, "default_role_id": "string", "default_role": { "id": "string", "name": "string" }, "created_at": "2026-04-20T12:00:00.000Z" } }
Tell us how we can improve this guide.