hosting

GET /v1/sites/deleted

List my deleted sites, and when each stops being recoverable.

All hosting endpoints

All developer docs →

Authentication

Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X GET https://api.zinndigital.com/v1/sites/deleted \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Sites deleted from the principal's orgs in the last 90 days, newest first, with an unambiguous date for when its backup is purged and the site becomes permanently unrecoverable (purge_due_at). ⚖️ Only rows that still have an action (owner ruling 2026-09-15, D26270). A record deleted more than 90 days ago, a record already purged (the data is gone) and a record already restored (the site is back in GET /v1/sites) are never returned. The bound is enforced here rather than by a client, because a client filter over a cursor-paginated list is a claim about one page. The staff list, GET /v1/admin/deleted-sites, is not bounded. ⛔ purge_due_at is computed by the engine from the live retention policy and must never be recomputed by a client. It comes from the same function the purge sweep selects on, so the date shown and the date acted on cannot drift. A client adding deleted_at + 30 would be a second hardcoded number, and it would be wrong the moment an operator edits the policy (D-W15-10b). ⛔ restorable is a measurement, not a status. It reflects a real check that the backup object exists in storage, so it is false — with reason_code: no_backup — for a site whose backup row claims success over bytes that were never written. A restore button over a backup that does not exist is worse than no button. Requires sites.view only: knowing which of your own sites were deleted, and by when they become unrecoverable, is not a privileged fact.

Parameters

NameTypeRequiredWhat it is
cursor (query)stringNoOpaque cursor from a previous page's page.next_cursor.
limit (query)integerNoMaximum items to return (page size).
within_days (query)integerNoOnly sites deleted in the last N days (at most the 90-day window). The sites list's collapsed "Recently deleted" panel asks for within_days=7&limit=5 (owner decision D11,…

Response

NameTypeRequiredWhat it is
dataDeletedSite[]Yes—
pagePageMetaYes—

Errors this endpoint can return

401 · 403 · 429