Legacy HTTP API
Write docs with Legacy QL
Perform one or more write operations (updates, upserts, or removals) in a single atomic transaction. This endpoint ensures all operations either succeed or fail together, maintaining data consistency.
POST
Authorizations
Authentication using either an API key or JWT token in the Authorization header
Headers
Optional transaction ID that ensures write consistency. The operation will only proceed if the Big Peer's transaction ID is at least this value, preventing concurrent modification issues.
Body
application/json
Request to execute one or more write commands in a transaction
Array of write commands to execute in the transaction
Response
200
application/json
The write operations completed successfully. Returns results for each command, including the new transaction ID and counts of affected documents.
Response containing results of executing a write transaction
Array of results for each write command executed in the transaction
Was this page helpful?