Add a custom auth domain
/portal/v1/accounts/{accountSlug}/applications/{appSlug}/environments/{envSlug}/auth-domainAdds a custom auth domain (e.g. auth.yourapp.com) to this Environment so its identity-auth API and hosted pages can be served first-party from the customer's own host. Parks it pending with a TXT-challenge token; the customer publishes the DNS records, then calls verify.
Authentication
AuthorizationJWT access token. Never send alongside X-API-Key: a request carrying both is refused.
sso.manageSecurityManage SSO connections, domains, and directory sync. Granted through an administrator role in the Admin Workspace; a valid token without it is refused with 403.
Request body
application/json
domainstring Required The hostname to serve this Environment's auth from, e.g. auth.yourapp.com. Must be a subdomain you control.
Responses
application/json
data *AuthDomainResponseDto
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.
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/{accountSlug}/applications/{appSlug}/environments/{envSlug}/auth-domain" \ -H "Authorization: Bearer $CANOPY_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "domain": "auth.yourapp.com" }'
{ "data": { "id": "string", "domain": "auth.yourapp.com", "tls_status": "pending", "dns_verified_at": "2026-04-20T12:00:00.000Z", "active": false, "dns_records": [ { "type": "CNAME", "name": "string", "value": "string" } ] } }
Tell us how we can improve this guide.