OriginChainDB
Database endpoints

Complete a schema migration

Switches a table over to its migrated shape and completes the migration.

POST /v1/tenants/{tenant}/migrations/{id}/cutover

Switch to a migration's new schemaCopying progress alone does not confirm cutover.
  1. Check the migration is readyInspect its current state by ID.
  2. Request the cutoverSwitch the table to the migrated shape.
  3. Confirm CompletedCompare the before and after schema versions.

Before you start

Use your database bearer token.

Connection setup

Use the ID returned by Start a schema migration. Check its state before cutover or abort.

Path parameters

FieldTypeRequired
tenantstringRequired
idstringRequired

Headers

FieldTypeRequiredDescription
x-oc-db-userstringOptionalActing database user (role, grant and row-policy checks). Send with x-oc-db-key.
x-oc-db-keystringOptionalAPI key of the x-oc-db-user user.

Read the result

state: Completed confirms the switch to the migrated schema shape. Compare version_before and version_after; copied-row progress alone was not the cutover confirmation.

Response statuses

HTTP status reference
StatusWhat to do
200OK
400Correct the request before retrying.
401Check the credential and Authorization header.
402Check feature access or available credits.
403Check tenant access, roles and permissions.
404Check the resource ID and API route.
409Resolve the conflict before retrying.
429Honor Retry-After when present; back off.
500Check the outcome before retrying a write.
501Check deployment support for this operation.
503Honor Retry-After when present; check write outcomes.
ยฉ 2026 Silicoyn Technologies Pvt Ltd