compute

DELETE `/v1/compute/servers/{serverId}/packages/{packageId}`

Remove a website from a server.

Autentifikatsiya

API kalitini bearer token sifatida yuboring. Kalit sites.delete 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/compute/servers/{serverId}/packages/{packageId} \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "confirm_domain": <string> }'

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

Deletes the hosting package and everything on it - files, databases, certificates and settings. **Irreversible at the provider.** Two things happen first, and both are promises to the customer rather than implementation detail. A **final backup is taken before anything is deleted**, and is kept for the retention window the site lifecycle policy states (30 days as seeded); if that backup cannot be taken, the deletion is **refused** with 422 and nothing is removed. And the **domain is left parked** - no zone is deleted, no record is removed and no name is released, so a customer moving a site between machines keeps the name pointed where it is. Resolved by organisation, server and package together, so a package id belonging to another tenant returns 404 rather than 403 - the same reason every other compute surface answers 404 for a machine that is not yours. A package this platform holds no site record for is refused: we cannot back up what we have no record of, and deleting it would break the retention promise silently. That is the state of any website created in the provider's own panel. Requires `sites.delete`. ⛔ **This operation carries a request body on `DELETE`**, the same idiom and the same reasoning as `deleteSite`: RFC 9110 permits it, and the typed confirmation must travel with the request that acts on it, because a "confirm" call followed by an unconfirmed delete is two requests and the second one is the whole vulnerability. `confirm_domain` is compared against the package's primary domain and a mismatch is `422`.

Parametrlar

Nomi	Turi	Majburiy	Nima bu
`serverId (path)`	`Uuid`	Ha	The server's id, as `listComputeServers` reports it. Ours (UUIDv7), minted when the order row was written — never the provider's own identifier for the machine.
`packageId (path)`	`string`	Ha	The provider's package identifier, as `listComputeServerPackages` reports it in `id` — deliberately not ours, because this addresses the thing on the machine. It is not a ca…

Soʻrov tanasi

Nomi	Turi	Majburiy	Nima bu
`confirm_domain`	`string`	Ha	The package's primary domain, typed by the customer. Compared exactly against the domain the provider reports for the package; anything else is `422` and nothing is deleted.

Ushbu yakuniy nuqta qaytarishi mumkin bo'lgan xatolar

401 · 403 · 404 · 422 · 429 · 503

DELETE /v1/compute/servers/{serverId}/packages/{packageId}