hosting

GET /v1/site-imports/platform

What the archived site was built on, and what a restore can recover.

Dukkan hosting wuraren ƙarshe

Tabbatar da Asali

Aika maɓallin API azaman alamar ɗauka (bearer token). Dole ne maɓallin ya kasance yana da izinin sites.view; idan babu shi, za a ƙi amfani da maɓallin tare da lambar 403, ba 404 ba.

Wannan wurin ƙarewa ba ya buƙatar ID na ƙungiya. Maɓallin ku ya riga ya gano ƙungiyar da yake ciki, kuma an iyakance amsa a kanta.

Gwada

May gurbin komai da ke cikin kusurwa da ƙimar ka, kuma may gurbin maballi da maballi daga allon sarrafa ka.

curl -X GET https://api.zinndigital.com/v1/site-imports/platform?domain=<domain>&day=<day> \
  -H "Authorization: Bearer zdk_live_…"

An shiga? Na'urar sarrafa API da ke cikin sashin kulawarka tana cika ainihin lambar ƙungiyarka da maɓallinka naka, sannan tana gudanar da buƙatar a kan ainihin API don haka zaka iya ganin amsar gaske. Buɗe wannan tashar a cikin na'urar kula da API

Bayani

⚖️ **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`.

Sigogi

SunaNau'iAna buƙataAbin da yake
domain (query)stringEhThe archived domain, e.g. `example.com`. `www.` is ignored.
day (query)stringEhThe 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…

Martani

SunaNau'iAna buƙataAbin da yake
domainstringEh
daystringEhThe snapshot day this verdict is about, `YYYY-MM-DD`.
statestring<pending, ready, stale, error>EhThe 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…
platformstring<wordpress, joomla, drupal, magento, shopify, wix, squarespace, blogger, typo3, prestashop, opencart, dotnetnuke, frontpage, static_html, unknown>Eh⛔ `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…
confidenceintegerEh`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_dynamicbooleanEhTrue 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".
gainsstring[]EhCodes 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…
lossesstring[]EhCodes for what a web archive cannot contain, so cannot come back — `admin`, `database`, `plugins`, `checkout`, `forms`, and so on.
suggested_outputstring<static, wordpress>EhA 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…
errorstringA'aWhy the last probe failed; empty when it did not.
probed_atstringA'a

Kuskuren da wannan matsaya za ta iya maido wa

401 · 403 · 422 · 429