Start Provider Cutover
POST/api/integration-instances/:integration_instance/cutover/start
Starts a planned cutover after re-checking the readiness checklist. Sets the status to in_progress, freezes the boundary, switches duplicate protection to link strong matches (the previous setting is restored on complete/cancel), and links or holds every open order placed before the boundary: those are never sent by SKU.io, are linked to the provider's own order as it appears, and move to needs-attention after 72 hours without one.
integrations:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body (optional):
acknowledge_blocked(boolean) — start despite blocked ordersmanual_submit(boolean) — start although auto-dispatch is off (orders will be submitted manually)acknowledge_native_import(boolean) — for a provider that cannot report its order syncs (disconnect.requires_acknowledgement): the operator confirmed the provider no longer imports from the channel. Needed in addition to a quiet disconnect check
Errors: 422 when the cutover is not planned, or naming every failing blocking checklist key (e.g. native_import_stopped).
Returns the full cutover state.
Required permission: integrations.update. A token also needs its integrations scope.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.