hosting

DELETE `/v1/sites/{siteId}/redirects/{redirectId}`

Delete a redirect from a site.

Authentication

Send an API key as a bearer token. The key must carry the sites.view 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}/redirects/{redirectId} \
  -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

Removes one rule. As with the create, the vendor call is a whole-set write, so the engine reads the rules, drops this one and sends the rest back — the surviving rules are carried, never dropped as a side effect of removing one. `404` for a site with no managed hosting package, and for an id that is not on it. Requires `sites.view` and `sites.panel_access`.

Parameters

Name	Type	Required	What it is
`siteId (path)`	`Uuid`	Yes	Site ID (UUIDv7).
`redirectId (path)`	`string`	Yes	The opaque id returned by `listSiteRedirects`. Engine-minted and base64url, so it carries `-` and `_`; percent-encode it rather than assuming it is path-safe.

Errors this endpoint can return

401 · 403 · 404 · 409 · 422 · 429 · 503

DELETE /v1/sites/{siteId}/redirects/{redirectId}