compute

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

Remove a website from a server.

Autentifikimi

Drgoni një çelës API si një token mbajtës. Çelësi duhet të ketë lejen sites.delete; një çelës pa të refuzohet me 403, jo 404.

Ky pikëndalim nuk pranon id të organizatës. Çelësi juaj tashmë identifikon organizatën së cilës i përket dhe përgjigjja kufizohet vetëm për atë.

Provoje

Zëvendësoni çdo gjë brenda kllapave këndore me vlerat tuaja dhe vendbanuesin e çelësit me një çelës nga paneli juaj.

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> }'

Jeni kyçur? Konsola e API-së në panelin tuaj plotëson ID-në tuaj reale të organizatës dhe çelësin tuaj, dhe ekzekuton kërkesën kundrejt API-së live, kështu që ju mund të shihni përgjigjen aktuale. Hapni këtë pikë fundore në konsolën e API-së

Detajet

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

Parametrat

Emri	Lloji	Kërkohet	Çfarë është kjo
`serverId (path)`	`Uuid`	Po	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`	Po	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…

Trupi i kërkesës

Emri	Lloji	Kërkohet	Çfarë është kjo
`confirm_domain`	`string`	Po	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.

Gabimet që ky pikëndalim mund të kthejë

401 · 403 · 404 · 422 · 429 · 503

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