hosting

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

Delete a redirect from a site.

Dukkan hosting wuraren ƙarshe

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin sites.view; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

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

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

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`.

Sigogi

SunaNau'iAna buƙataAbin da yake
siteId (path)UuidEhSite ID (UUIDv7).
redirectId (path)stringEhThe opaque id returned by `listSiteRedirects`. Engine-minted and base64url, so it carries `-` and `_`; percent-encode it rather than assuming it is path-safe.

Kuskuren da wannan matsaya za ta iya maido wa

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