GET /v1/sites/deleted

ማረጋገጫ

የAPI ቁልፉን እንደ bearer token ይላኩ። ቁልፉ የsites.view ፈቃድ ሊኖረው ይገባል፤ ይህ ፈቃድ የሌለው ቁልፍ በ404 ሳይሆን በ403 ውድቅ ይደረጋል።

ይህ ኤንድፖይ መክፈቻ (endpoint) የድርጅት መታወቂያ (organisation id) አይወስድም። የእርስዎ ቁልፍ (key) እሱ የሚመለከተውን ድርጅት አስቀድሞ ይለያል፣ እና ምላሹም ለዚሁ የተወሰነ ነው።

ሞክሩት

በቅንፍ ውስጥ ያለውን ማንኛውንም ነገር በራስዎ እሴቶች ይተኩ፣ እና ቁልፍ ቦታ ያዢውን ከዳሽቦርድዎ በመጣ ቁልፍ ይተኩ።

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

ገብተዋል? የመቆጣጠሪያ ማዕከልዎ ውስጥ ያለው የኤፒአይ ኮንሶል ትክክለኛውን የድርጅት መታወቂያዎን እና የራስዎን ቁልፍ ይሞላል፣ እና ትክክለኛውን ምላሽ ማየት እንዲችሉ ጥያቄውን በቀጥታ ከሚሰራው ኤፒአይ ጋር ያካሂደዋል። ይህን ኤንድፖይንት በAPI ኮንሶል ውስጥ ይክፈቱ

ዝርዝሮች

Every site deleted from the principal's orgs, newest first, with **an unambiguous date for when its backup is purged and the site becomes permanently unrecoverable** (`purge_due_at`). ⛔ **`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.

መለኪያዎች

ምላሽ

ይህ ማብቂያ ሊመልሳቸው የሚችሉ ስህተቶች

401 · 403 · 429