Remove one of the organization's domain claims
/api/v1/organizations/{id}/domains/{domain}Removes a domain claim from the organization; the bound connection stops routing and admitting that domain on the next login. Emits an sso.domain.removed audit row and returns 204; responds 404 when the organization holds no claim for that domain.
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.manageHierarchyCreate, update, and delete 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 domainstring 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
Delete the claim. Sign-ins for that domain stop routing to the organization's connection on the next attempt.
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.
curl -X DELETE "https://auth.canopy-io.com/api/v1/organizations/value/domains/value" \ -H "X-Canopy-Environment: value" \ -H "X-API-Key: $CANOPY_API_KEY"
HTTP/1.1 204 Delete the claim. Sign-ins for that domain stop routing to the organization's connection on the next attempt. (empty body)
Tell us how we can improve this guide.