Database endpoints
Delete a transactional row
Buffers the deletion of one row, addressed by primary key, in the transaction.
DELETE /v1/tenants/{tenant}/tx/{tx_id}/rows/{schema}/{pk}
- Choose transaction and rowSupply the transaction ID, table and primary key.
- Buffer the deletionStage removal within this transaction.
- Commit or roll backApply the change or discard it deliberately.
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 |
schema | string | Required |
pk | 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
buffered: true means the deletion is staged in this transaction. It is not a committed deletion; finish with commit or rollback.
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. |
| 413 | Split or reduce the request body. |
| 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. |