hosting

POST /v1/sites/{siteId}/vendor-snapshots/restore

Restore a site from a vendor restore point.

כל נקודות הקצה מסוג hosting

אימות

שלחו מפתח API כאסימון נושא (bearer token). על המפתח לכלול את הרשאה hosting.backup.manage; מפתח שאינו כולל אותה יידחה בסטטוס 403, ולא 404.

נקודת קצה זו אינה דורשת מזהה ארגון. המפתח שלך כבר מזהה את הארגון שאליו הוא שייך, והתגובה מוגבלת אליו בלבד.

נסה זאת

החלף כל דבר בסוגריים זוויתיים בערכים משלך, ואת מציין מיקום המפתח במפתח מלוח הבקרה שלך.

curl -X POST https://api.zinndigital.com/v1/sites/{siteId}/vendor-snapshots/restore \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "scope": <string<web, database, mailbox>>, "timestamp": <string> }'

מחובר? קונסולת ה-API בלוח הבקרה שלך מזינה את מזהה הארגון האמיתי שלך ואת המפתח שלך, ומריצה את הבקשה מול ה-API הפיזי כך שתוכל לראות את התגובה בפועל. פתח נקודת קצה זו במסוף ה-API

פרטים

Rolls the website, one database or one mailbox back to a named restore point. `202` and the whole surface's new state, for the same reason `takeSiteVendorSnapshot` returns it: the platform performs the restore afterwards and the client polls on `in_progress`. ⛔ **This is the destructive one, and its own path is part of how it is gated.** It overwrites the customer's live files and database, so it is deliberately not a verb on the collection that takes backups — it must not be reachable by sending a slightly different body to the endpoint beside it. A restore always **names its restore point**, never "the latest": `timestamp` is one of the values `getSiteVendorSnapshots` returned, and the engine re-checks it against the live listing before anything is sent, so a value a client composed cannot reach the vendor. `temp_mailbox` applies to mailboxes only, where the platform restores into a `temp-` prefixed mailbox instead of overwriting the original; it is offered as a choice rather than assumed. The action is audit-logged **after** the platform accepts it, so the trail never claims a restore a refusal never started. `404` for a site with no vendor hosting package, or one that is not the caller's; `422` for a restore point that is no longer in the listing or a scope that cannot be restored. Requires `hosting.backup.manage`.

פרמטרים

שםסוגנדרשמה זה
siteId (path)UuidכןSite ID (UUIDv7).

גוף הבקשה

שםסוגנדרשמה זה
scopestring<web, database, mailbox>כןWhat to restore.
timestampstringכןThe restore point's handle, exactly as `getSiteVendorSnapshots` reported it.
item_idstringלאWhich database or mailbox. Empty for the website.
temp_mailboxbooleanלאMailboxes only. The platform restores into a `temp-` prefixed mailbox instead of overwriting the original, which is the safe default for mail — offered as a choice rather than a…

תשובה

שםסוגנדרשמה זה
availablebooleanכןWhether the site's hosting platform has a timeline surface at all. False is **our** gap, and nothing the customer can do changes it.
permittedbooleanכןWhether the vendor package type includes it. False is answered by an upgrade.
probooleanכןWhether the package carries the paid tier rather than the included one.
attachedbooleanכןWhether a Timeline Storage service is actually attached to the package. False is the third "no", and it is neither of the other two.
can_back_upbooleanכןWhether `takeSiteVendorSnapshot` would be accepted right now. Read rather than recomputed from the three flags above, so a screen never offers a button the engine refuses.
has_dead_webbooleanכןWhether the platform reports the website's timeline as broken. It is surfaced rather than hidden: a customer whose restore points stopped being taken needs to know before they n…
in_progressbooleanכןWhether any snapshot or restore job is running. This is what a client polls on, and only while it is true.
webSiteVendorSnapshotItemכןThe website's timeline, or null when the platform holds none.
databasesSiteVendorSnapshotItem[]כןEach database's timeline.
mailboxesSiteVendorSnapshotItem[]כןEach mailbox's timeline.

שגיאות שנקודה קצה זו עשויה להחזיר

401 · 403 · 404 · 422 · 429 · 503