hosting
GET /v1/site-imports/platform
What the archived site was built on, and what a restore can recover.
인증
Bearer 토큰으로 API 키를 전송하세요. 키는 반드시 sites.view 권한을 가지고 있어야 하며, 권한이 없는 키는 404가 아닌 403으로 거부됩니다.
이 엔드포인트는 조직 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