Activate an SSO connection
/api/v1/sso/connections/{id}/activatePromotes a connection from configuring to active after validating that the type's required fields are present (SAML: entity id, SSO URL, signing cert; OIDC: discovery URL, client id, client secret). Returns 400 when configuration is incomplete and 404 when the connection is not found. Emits an sso.connection.activated audit row and returns the updated connection.
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.
sso.manageAccountCreate, update, and delete SSO connections, verified domains and SCIM tokens. 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 Responses
application/json
data *SsoConnectionResponseDto
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 POST "https://auth.canopy-io.com/api/v1/sso/connections/value/activate" \ -H "X-API-Key: $CANOPY_API_KEY"
{ "data": { "id": "string", "account_id": "string", "scope": "admin", "type": "saml", "name": "string", "status": "configuring", "owner_organization_node_id": "string", "owned_by_organization": false, "saml_metadata_url": "string", "last_test_sign_in": { "test_id": "string", "outcome": "success", "reason": "string", "email": "string", "domain_outcome": "accepted", "completed_at": "2026-04-20T12:00:00.000Z" }, "saml_entity_id": "string", "saml_sso_url": "string", "saml_slo_url": "string", "saml_signing_cert": "string", "saml_signature_algorithm": "string", "saml_want_assertions_signed": false, "saml_name_id_format": "string", "force_authn": false, "oidc_discovery_url": "string", "oidc_client_id": "string", "oidc_scopes": [ "string" ], "has_oidc_client_secret": false, "jit_provisioning_enabled": false, "attribute_mapping": {}, "last_login_at": "2026-04-20T12:00:00.000Z", "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.