hosting

POST /v1/migrations/discover

Identify a host from its hostname, with no site yet.

すべての hosting エンドポイント

すべての開発者向けドキュメント

認証

ベアラー トークンとして API キーを送信します。このエンドポイントでは仕様に特定の権限が記載されていないため、キーに必要な最小限の権限を付与し、推測するのではなくレスポンスを確認してください。

このエンドポイントは組織IDを受け付けません。お使いのキーによって所属する組織がすでに特定されており、レスポンスはその組織にスコープされます。

試してみる

アングルブラケット内のすべてをご自身の値に置き換え、キーのプレースホルダーをご利用中のダッシュボードのキーに置き換えてください。

curl -X POST https://api.zinndigital.com/v1/migrations/discover \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "host": <string> }'

ログインしていますか?ダッシュボード内のAPIコンソールでは、実際の組織IDやお客様ご自身のキーが自動入力され、ライブAPIに対してリクエストが実行されるため、実際のレスポンスを確認することができます。 API コンソールでこのエンドポイントを開く

詳細

The org-scoped twin of POST /v1/sites/{siteId}/migrations/discover. Same workflow, same 202-plus-poll shape, and the same owner ruling behind it: signed-in customers only, never a prospect — the hostname is attacker-supplied by construction and "probe this for me" is the classic shape of a request to reach something the caller cannot. It exists because the customer it serves has no sites at all, which is exactly the customer being asked "which control panel do you log in to?" by a form they cannot answer. hosting.import.manage is an org permission, so every run still has a named actor and an org to rate-limit; only the site-level anchor is dropped, and nothing about the ruling rested on it. POST rather than GET, and not because of a secret — there is none in the body. It knocks on a third party's administrative ports, which is an act rather than a lookup, and must not be repeated by a browser prefetch, a CDN revalidation or a back button. Name the organisation with X-Zinn-Org when you belong to more than one; a caller in exactly one org may omit it.

リクエスト本文

名前タイプ必須これがその内容です
hoststringはいThe server address the current host gave them, e.g. server123.theirhost.com. A hostname, not a web address — no scheme and no path. The customer's own domain works too when it…

返信

名前タイプ必須これがその内容です
outcomestring<pending, identified, unidentified, unreachable>はいpending while the discovery workflow is still probing — poll getMigrationDiscovery until it is one of the other three (D19865). ⛔ Three answers and never a boolean.…
hoststringはいThe hostname as it was normalised, which may differ from what was typed.
sourcestringはいThe best candidate's MigrationSource, or "" when there is none.
portintegerはいThe login port for that source, which is not necessarily the port the evidence came from: a banner read from cPanel's plaintext 2082 reports 2083, because that is where the…
confidenceintegerはい
confidentbooleanはいMay the credential form be pre-filled from this?
candidatesMigrationDiscoveryCandidate[]はい
expectationsstring[]はいMachine codes for what to expect from the winning source — e.g. ftp_files_only. ⛔ Expectations, not a capability claim: the authoritative answer comes from the credentialed…
routesMigrationDiscoveryRoute[]はいEvery way in that was tried. Read it when a panel is firewalled — a host with 2083 closed and 22 open can still have everything moved.
proxy_frontedbooleanはいThis address is a CDN in front of a website, not a hosting account — several different panels' login ports accepted a connection at once and none of them answered with its own…
refusedstringはいA customer-readable reason the hostname was rejected before any packet went out — a private address, an unresolvable name. "" otherwise.
agent_usedbooleanはいWhether a language model was asked to read the sign-in page. It is asked only when the deterministic table produced no confident panel.
agent_unavailablestringはいMachine code when the model was asked and could not answer (ai_unavailable, ai_timeout, …). "" when it was not asked or it answered. ⛔ The deterministic answer stands either…
discovery_idstringはいThe recorded run, for support. "" when the row could not be written — which never costs the customer their answer.

このエンドポイントが返すエラー

401 · 403 · 422 · 429 · 503