hosting

DELETE `/v1/sites/{siteId}/edge-domains/{hostname}`

Stop serving this hostname from the deploy target.

Authentication

Send an API key as a bearer token. The key must carry the hosting.deploy.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X DELETE https://api.zinndigital.com/v1/sites/{siteId}/edge-domains/{hostname} \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Detaches the hostname at the provider and forgets it here. The DNS records are deliberately left in place: they are in the customer's zone, and a name that has stopped serving is a fixable state while a record we silently deleted is not. Requires `hosting.deploy.manage`.

Parameters

Name	Type	Required	What it is
`siteId (path)`	`Uuid`	Yes	Site ID (UUIDv7).
`hostname (path)`	`string`	Yes	The bound hostname, lower-cased and without a trailing dot.

Errors this endpoint can return

401 · 403 · 404 · 422 · 429

DELETE /v1/sites/{siteId}/edge-domains/{hostname}