hosting
GET /v1/site-imports/platform
What the archived site was built on, and what a restore can recover.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/site-imports/platform?domain=<domain>&day=<day> \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 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… |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
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 to… |
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 than… |
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 feature… |
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… |
error | string | 否 | Why the last probe failed; empty when it did not. |
probed_at | string | 否 | — |
此端点可能返回的错误
401 · 403 · 422 · 429