hosting
GET /v1/site-imports/platform
What the archived site was built on, and what a restore can recover.
المصادقة
أرسل مفتاح واجهة برمجة التطبيقات (API key) كرمز حامل (bearer token). يجب أن يحمل المفتاح إذن sites.view؛ والمفتاح الذي لا يملكه يُرفض بالرمز 403 وليس 404.
لا يقبل هذا الطرف أي معرف للمؤسسة. يحدد مفتاحك بالفعل المؤسسة التي ينتمي إليها، وتكون الاستجابة محصورة في نطاقها.
جربه الآن
استبدل أي شيء بين أقواس زاوية بقيمك الخاصة، والعنصر النائب للمفتاح بمفتاح من لوحة تحكمك.
curl -X GET https://api.zinndigital.com/v1/site-imports/platform?domain=<domain>&day=<day> \
-H "Authorization: Bearer zdk_live_…"هل سجلت الدخول؟ تقوم وحدة تحكم واجهة برمجة التطبيقات في لوحة التحكم الخاصة بك بربط معرف مؤسستك الحقيقي ومفتاحك الخاص، وتنفذ الطلب مقابل واجهة برمجة التطبيقات المباشرة لتتمكن من رؤية الاستجابة الفعلية. افتح هذه النهاية الطرفية في وحدة تحكم API
التفاصيل
⚖️ **Owner ruling 2026-09-08.** A web-archive capture holds rendered HTML and nothing else — no database, no PHP, no administrator — so a Joomla, Drupal or Magento site cannot be restored *as* that application. This endpoint says what the archive was, so the restore form can state plainly, **before the customer commits**, what they get back (`gains`) and what is gone (`losses`). Every value is a machine code the client localises; the engine composes no sentences (they could only ever be English). ⛔ A cached read, like `/v1/site-imports/snapshots`, and for a related but different reason: one home-page fetch measured 1.13 s live on 2026-09-08, which is affordable once and not affordable per viewer of a shared aged-domain list. A miss starts a durable probe and answers `202` with `state: "pending"`; poll it. `state` has the same four values as the snapshot index and they are not interchangeable. Requires `sites.view`.
المعلمات
| الاسم | النوع | مطلوب | ما هو هذا |
|---|---|---|---|
domain (query) | string | نعم | The archived domain, e.g. `example.com`. `www.` is ignored. |
day (query) | string | نعم | The snapshot day being considered, `YYYY-MM-DD`. Required, because a domain's platform changes over its life — a 2009 capture and a 2019 capture of one domain routinely answer d… |
الاستجابة
| الاسم | النوع | مطلوب | ما هو هذا |
|---|---|---|---|
domain | string | نعم | — |
day | string | نعم | The snapshot day this verdict is about, `YYYY-MM-DD`. |
state | string<pending, ready, stale, error> | نعم | The same four values `ArchiveSnapshotIndex.state` carries, and the same rule — `pending` ("nobody has looked") and `error` ("we looked and the archive refused") lead a customer… |
platform | string<wordpress, joomla, drupal, magento, shopify, wix, squarespace, blogger, typo3, prestashop, opencart, dotnetnuke, frontpage, static_html, unknown> | نعم | ⛔ `unknown` and `static_html` are different answers and must not be collapsed: the first is "we could not tell", the second is "this was hand-written HTML, so there was nothing… |
confidence | integer | نعم | `0` nothing seen · `1` a signature (an asset path or a script global) · `2` the page's own `<meta name="generator">`. Carried so a client can say "looks like" on a `1` rather th… |
was_dynamic | boolean | نعم | True when the site was an application rather than a set of pages — i.e. when the customer must be told something beyond "here are your pages back". |
gains | string[] | نعم | Codes for what the restore DOES recover. Stated as explicitly as the losses: a panel that lists only what is missing reads as "this will not work", and it is describing a featur… |
losses | string[] | نعم | Codes for what a web archive cannot contain, so cannot come back — `admin`, `database`, `plugins`, `checkout`, `forms`, and so on. |
suggested_output | string<static, wordpress> | نعم | A recommendation the customer may override, never a forced choice. WordPress in, WordPress out — it is the one platform whose content we can genuinely re-home, because our WXR w… |
error | string | لا | Why the last probe failed; empty when it did not. |
probed_at | string | لا | — |
الأخطاء التي يمكن أن تُرجعها نقطة النهاية هذه
401 · 403 · 422 · 429