Offboarding

Offboarding a domain is an operational step, not a single API call. The /v1 surface does not currently expose a connection-delete endpoint.

Disconnecting a domain

To take a domain off your product, the customer removes the edge records at their DNS provider (the CNAME/A records that pointed the hostname at the edge). Once those records no longer resolve to the edge:

• the domain stops being served — the edge only proxies hosts that resolve to it;
• Monitor observes the change and fires domain.record_missing, so your integration can react (e.g. mark the domain disconnected in your own system).

If you applied records through a delegated rail (OAuth or an API token), removing them is done in the customer's DNS provider the same way — the platform never retained a credential to do it for them.

Current limitations

• There is no DELETE /v1/connections/{id} and no archive state; a connection row persists after the domain is removed from DNS.
• The pending → propagating → live → failed lifecycle is forward-only; the poller promotes connections but does not demote a live one whose records were later removed. Use Monitor drift events to detect that case.

See Capabilities & limitations for the full, honest list of what is automated versus operational.