hosting

DELETE /v1/sites/{siteId}/wordpress/staging/{cloneId}

Delete a site's WordPress staging clone.

Barcha hosting yakuniy nuqtalari

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}/wordpress/staging/{cloneId} \
  -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 staging copy. The **live** site is untouched — this path is declared after the literal `publish` and `reinstall` segments precisely so a request to one of those can never resolve here. `202` and the whole staging state, because the removal continues at the vendor. `404` for a site with no vendor hosting package, and for an id that is not on it. Requires `sites.view` and `sites.panel_access`.

Parametrlar

NomiTuriMajburiyNima bu
siteId (path)UuidHaSite ID (UUIDv7).
cloneId (path)stringHaThe clone id returned by `getSiteWordPressStaging`. The vendor's identifier, carried as a string.

Javob

NomiTuriMajburiyNima bu
permittedbooleanHaWhether this site may use WordPress staging at all — on the resold range the package type's own flag, and on our own fleet the plan's `staging` entitlement.
publish_modesstring<files, db, both>[]HaWhich publish scopes this site's **platform** can actually perform, for `publishSiteWordPressStaging`. A client offers exactly these and no more. ⛔⛔ **This is not a permission a…
publishablebooleanHaWhether the plan also carries **publish to live**, which is a separate permission from creating a staging copy. ⛔ Not folded into `permitted`, because the catalogue sells the tw…
reinstallablebooleanHaWhether the plan carries **reinstalling** the platform software over the staging copy. A fifth question for the same reason as `publishable`: the catalogue sells it separately,…
operationsSiteWordPressStagingOperation[]HaThe site's recent staging operations, newest first — the client's window onto work that runs **after** the request returns. ⛔⛔ **Creating, publishing, deleting and reinstalling…
dataSiteWordPressStagingClone[]HaThe staging copies that exist.

Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar

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