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
- Check the migration is readyInspect its current state by ID.
- Request the cutoverSwitch the table to the migrated shape.
- Confirm CompletedCompare the before and after schema versions.
Before you start
Use your database bearer token.
Use the ID returned by Start a schema migration. Check its state before cutover or abort.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
id | string | Required |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API 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
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 404 | Check the resource ID and API route. |
| 409 | Resolve the conflict before retrying. |
| 429 | Honor Retry-After when present; back off. |
| 500 | Check the outcome before retrying a write. |
| 501 | Check deployment support for this operation. |
| 503 | Honor Retry-After when present; check write outcomes. |