hosting
GET /v1/site-imports/platform
What the archived site was built on, and what a restore can recover.
Kimlik Doğrulama
Bearer token olarak bir API anahtarı gönderin. Anahtar sites.view iznine sahip olmalıdır; bu izne sahip olmayan bir anahtar 404 ile değil, 403 ile reddedilir.
Bu uç nokta hiçbir organizasyon kimliği almaz. Anahtarınız zaten ait olduğu organizasyonu tanımlar ve yanıt bu organizasyonla sınırlandırılır.
Dene
Köşeli parantez içindeki her şeyi kendi değerlerinizle ve anahtar yer tutucusunu panonuzdan bir anahtarla değiştirin.
curl -X GET https://api.zinndigital.com/v1/site-imports/platform?domain=<domain>&day=<day> \
-H "Authorization: Bearer zdk_live_…"Oturum açtınız mı? Panonuzdaki API konsolu, gerçek organizasyon kimliğinizi ve kendi anahtarınızı otomatik olarak doldurur ve isteği canlı API üzerinde çalıştırarak gerçek yanıtı görmenizi sağlar. Bu uç noktayı API konsolunda açın
Ayrıntılar
⚖️ **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`.
Parametreler
| Ad | Tür | Zorunlu | Ne olduğu |
|---|---|---|---|
domain (query) | string | Evet | The archived domain, e.g. `example.com`. `www.` is ignored. |
day (query) | string | Evet | 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… |
Yanıt
| Ad | Tür | Zorunlu | Ne olduğu |
|---|---|---|---|
domain | string | Evet | — |
day | string | Evet | The snapshot day this verdict is about, `YYYY-MM-DD`. |
state | string<pending, ready, stale, error> | Evet | 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> | Evet | ⛔ `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 | Evet | `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 | Evet | 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[] | Evet | 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[] | Evet | 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> | Evet | 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 | Hayır | Why the last probe failed; empty when it did not. |
probed_at | string | Hayır | — |
Bu uç noktanın dönderebileceği hatalar
401 · 403 · 422 · 429