OriginChainDB
Database endpoints

Roll back a transaction

Discards every write buffered in the transaction and closes it.

POST /v1/tenants/{tenant}/tx/{tx_id}/rollback

Discard the transaction's pending changesThis does not undo writes previously sent outside this transaction.
  1. Identify the transactionUse the ID holding the unwanted buffered writes.
  2. Roll back the transactionDiscard the writes and close it.
  3. Confirm rolled_backTreat the transaction as finished after confirmation.

Before you start

Use your database bearer token.

Connection setup

Begin a transaction and replace TX_ID with its returned tx_id. Finish the transaction with commit or rollback.

Path parameters

FieldTypeRequired
tenantstringRequired
tx_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

rolled_back: true confirms the transaction's buffered writes were discarded and the transaction closed. It does not undo operations previously sent outside that transaction.

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.
503Honor Retry-After when present; check write outcomes.
© 2026 Silicoyn Technologies Pvt Ltd