TransferCustomDomainAPI moves a custom domain to another organization the
caller also administers, without touching its CDN hostname or certificate — the serving cutover is atomic with the move and incurs no re-validation downtime.
Authorizations
An Erdo API key (erdo_api_...) or scoped token (erdo_token_...).
Path Parameters
Body
The caller must be an admin of both the org that owns the domain and the target org — a manager credential steering between its managed orgs satisfies both.
Response
Success response
provider — shown until (and after) the domain validates, so a stuck domain can be re-checked against what should exist.
"pages.acme.com". It is the identifier every other custom-domain endpoint takes.
disabled (e.g. a CAA record blocking certificate issuance); empty otherwise.
(RFC 3339); empty if never checked yet.
customer's DNS records), "pending_cert" (ownership verified, certificate issuing), "active" (serving), "failed" (validation or issuance error — see error_reason), or "disabled" (deregistered upstream). This is read from the same record the serving path consults, kept reconciled against the CDN by a monitoring job.

