Database endpoints
Retrieve transaction status
Returns the current state, snapshot tick and isolation level of a transaction.
GET /v1/tenants/{tenant}/tx/{tx_id}
- Identify the transactionUse the ID returned by begin.
- Read its current stateInspect status, isolation level and snapshot tick.
- Choose the next actionContinue or finish according to its reported state.
Before you start
Use your database bearer token.
Begin a transaction and replace TX_ID with its returned tx_id. Finish the transaction with commit or rollback.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
tx_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
Check state for the transaction's current status and isolation for its chosen mode. read_ts identifies its snapshot. Use the same tx_id throughout the operation sequence.
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. |
| 429 | Honor Retry-After when present; back off. |
| 503 | Honor Retry-After when present; check write outcomes. |