hosting

GET /v1/site-imports/platform

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

Ҳамаи нуқтаҳои ниҳоии hosting

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати sites.view бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

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

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли 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…

Ҷавоб

НомНамудТалаб карда мешавадИн чӣ аст
domainstringБале
daystringБалеThe snapshot day this verdict is about, `YYYY-MM-DD`.
statestring<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…
platformstring<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…
confidenceintegerБале`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_dynamicbooleanБале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".
gainsstring[]Бале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…
lossesstring[]БалеCodes for what a web archive cannot contain, so cannot come back — `admin`, `database`, `plugins`, `checkout`, `forms`, and so on.
suggested_outputstring<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…
errorstringНеWhy the last probe failed; empty when it did not.
probed_atstringНе

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 422 · 429