POST /v1/sites/{siteId}/migrations/discover

Pagpapatotoo

Magpadala ng API key bilang isang bearer token. Kailangang taglayin ng key ang pahintulot na hosting.import.manage; ang key na wala nito ay tatanggihan gamit ang 403, hindi 404.

Ang endpoint na ito ay hindi nangangailangan ng id ng organisasyon. Natutukoy na ng iyong key ang organisasyong kinabibilangan nito, at nakatuon ang tugon dito.

Subukan ito

Palitan ang anuman sa loob ng mga panaklong na may anggulo ng iyong sariling mga halaga, at ang placeholder ng key na may key mula sa iyong dashboard.

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

Nakalagda? Ang API console sa iyong dashboard ay awtomatikong naglalagay ng iyong tunay na ID ng organisasyon at sariling susi, at pinapatakbo ang kahilingan laban sa live na API upang makita mo ang aktwal na tugon. Buksan ang endpoint na ito sa console ng API

Mga Detalye

Takes a hostname and **no credential**, and answers which control panel the host is running, on which port, and what we would expect to be able to take off it. It exists because the step before it used to be a dropdown asking a prospect to choose "cPanel / WHM" or "DirectAdmin" and to know their own control-panel port — which the customer who is leaving a host they are unhappy with frequently cannot answer, and a form that cannot be filled in is a migration that is postponed for ever. It runs unauthenticated TCP connects and reads public sign-in pages. Five protocol fingerprints decide first (`cpsrvd` in a `Server:` header, `PLESKSESSID`, and so on — facts about software, not a list of hosting brands that would rot); a language model is asked to read the page **only** when that table is not confident, and its answer is weighted evidence that cannot outrank a protocol banner. `agent_used` says whether it was asked. `outcome` is three-valued and never a boolean: `identified`, `unidentified` (something answered and we cannot place it — a candidate for the managed migration) and `unreachable` (nothing answered at all — usually a typo or a firewall). Those have opposite remedies, so folding them would hand both populations the same wrong advice. `routes` lists every way in that was tried and whether it answered, with `checked` distinguishing "closed" from "we never got to try". Read it when a panel is firewalled: a host with 2083 closed and 22 open can still have its files, databases and mail moved. **Nothing we do installs anything on the source** — no migration plugin, no backup plugin, no agent — so a host that forbids those blocks none of it. ⛔ `POST` although it creates nothing and carries no secret: it knocks on a third party's administrative ports, which is an act rather than a lookup, and must not be repeated by a prefetch or a back button. A bad hostname or a dead host is an `outcome`, not an error. Requires `hosting.import.manage`.

Mga Parameter

Katawan ng kahilingan

Tugon

Mga error na maibabalik ng endpoint na ito

401 · 403 · 404 · 422 · 429 · 503