hosting
DELETE /v1/sites/{siteId}/redirects/{redirectId}
Delete a redirect from a site.
Autentifikatsiya
API kalitini bearer token sifatida yuboring. Kalit sites.view ruxsatiga ega boʻlishi shart; ruxsatsiz kalit 404 emas, balki 403 xatosi bilan rad etiladi.
Bu yakuniy nuqta hech qanday tashkilot identifikatorini qabul qilmaydi. Sizning kalitingiz unga tegishli tashkilotni allaqachon aniqlaydi va javob shunga qarab cheklanadi.
Sinab ko'rish
Qavslardagi har qanday narsani o'z qiymatlaringiz bilan, kalit pleysxolderini эsa boshqaruv panelingizdagi kalit bilan almashtiring.
curl -X DELETE https://api.zinndigital.com/v1/sites/{siteId}/redirects/{redirectId} \
-H "Authorization: Bearer zdk_live_…"Tizimga kirganmisiz? Boshqaruv panelingizdagi API konsoli haqiqiy tashkilot ID raqamingiz va shaxsiy kalitingizni avtomatik to'ldiradi hamda haqiqiy javobni ko'rishingiz uchun so'rovni jonli API orqali bajaradi. Ushbu yakuniy nuqtani API konsolida oching
Tafsilotlar
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`.
Parametrlar
| Nomi | Turi | Majburiy | Nima bu |
|---|---|---|---|
siteId (path) | Uuid | Ha | Site ID (UUIDv7). |
redirectId (path) | string | Ha | The opaque id returned by `listSiteRedirects`. Engine-minted and base64url, so it carries `-` and `_`; percent-encode it rather than assuming it is path-safe. |
Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar
401 · 403 · 404 · 409 · 422 · 429 · 503