Get the service-provider values for an organization's SSO connection
/api/v1/organizations/{id}/sso-connection/service-providerThe values an administrator enters into the identity provider for this connection: for SAML the ACS URL, entity id, and metadata URL; for OpenID Connect the redirect URI. They are on the origin the API advertises in its own metadata and requests. Requires hierarchy.view or canopy:organization.manage at the organization.
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
data *ServiceProviderDetailsResponseDto
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. 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/sso-connection/service-provider" \ -H "X-Canopy-Environment: value" \ -H "X-API-Key: $CANOPY_API_KEY"
{ "data": { "protocol": "saml", "acs_url": "string", "entity_id": "string", "metadata_url": "string", "redirect_uri": "string" } }
Tell us how we can improve this guide.