hosting

POST /v1/migrations/ai-moves/{moveId}/restart

Start this AI Move again from the beginning, as a fresh move.

All hosting endpoints

All developer docs →

Zinn®, our Viking, hammering at his anvil beside an API endpoint sending events to several listeners.

Authentication

Send an API key as a bearer token. The key must carry the hosting.import.manage permission; a key without it is refused with 403, not 404.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/migrations/ai-moves/{moveId}/restart \
  -H "Authorization: Bearer zdk_live_…"

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Owner row 1107#24. The fresh move keeps the same site, the access already given and the same ticket; this one is cancelled (its unfinished copy is stopped) and points to the new one in restarted_as. Nothing at the old host is changed. Refused with 409 once the move is done or cancelled (refusal.aiMove.finished), once its switch-over has started (refusal.aiMove.switchStarted), or when its access was already deleted (refusal.aiMove.accessGone — start a new move instead). Requires hosting.import.manage.

Parameters

NameTypeRequiredWhat it is
moveId (path)stringYes—

Response

NameTypeRequiredWhat it is
idstringYes—
org_idstringYes—
site_idobjectNo—
target_domainstringYes—
product_linestringNo—
stagestring<received, checking_access, needs_access, checking_fit, needs_upgrade, ready_to_copy, copying, verifying, awaiting_cutover, done, needs_staff, cancelled>Yes—
pausedbooleanYes—
taken_overbooleanYesA person from our migration team has taken it over.
platformstringYes—
source_urlsstring[]Yes—
access_kindsstring[]Yes—
access_reportobjectNoPer access kind, ok or the refusal code of the last check.
routestringNoThe route chosen (ssh, cpanel, plesk, directadmin, ftp).
inventoryobjectNo—
fitobjectNoThe plan-fit verdict and any upgrade offered (engine-quoted).
approx_sizestringNo—
move_itemsstring[]No—
cutover_windowstringNo—
timezonestringNo—
ticket_idobjectNo—
migration_job_idobjectNoThe site migration this move started (copying onwards); its rollback state is on GET /v1/sites/{site_id}/migrations.
checksobjectNoThe switch-over verdict: preview, app, passed (both), then live after the switch-over.
go_atobjectNoWhen the GO was given.
needsstring<, access, mailboxes, replace, replace_existing, address_in_use>NoWhat a waiting move is asking the customer for. replace_existing: the domain is already on another site of this organisation (existing_site) — confirm with replace_site_id…
existing_siteobjectNoWhen needs is replace_existing: the site in this organisation that already holds the domain.
preview_urlstringNoThe preview address, while waiting to switch over.
extra_purchase_idobjectNo—
started_by_staffbooleanNo—
created_atobjectYes—
updated_atobjectNo—
completed_atobjectNo—
progressAiMoveProgressYesWhere the move has got (owner row 1105#11). step of steps on the customer's path (a waiting stage sits on the step it waits in); phase of the copy; files, databases,…
healthAiMoveHealthNoThe honest state beside the stage (owner row 1107#24). on_track: inside the time the stage normally takes. slow: past it, still working. self_healing: our AI hit a problem…
restarted_asobjectNoWhen the customer restarted this move: the fresh move that replaced it.
can_restartbooleanNoWhether POST .../restart would start a fresh move now.

Errors this endpoint can return

401 · 404 · 409