Available in version 0.14.2 and later.
batch_id via the single update endpoint, not the bulk inflight endpoints.
Bulk commit
To bulk commit in one request, use:Bulk commit inflight
transactions array.
- Using the queue
- Skipped queue
From Blnk Core 0.15.0, bulk commit and void go through the queue by default.
queued status means the job is queued, not committed. Parents stay INFLIGHT until workers create APPLIED children.Per item results:Failures are per-item. One does not block the batch.
200 Queued
APPLIED child records for each committed item. Verify outcomes with webhooks or polling - same as single commit and void.Bulk void
To bulk void in one request, use:Bulk void inflight
transaction_ids array, not the transactions shape used by bulk commit.
Each request accepts a maximum of 100 IDs in the transaction_ids array.
- Using the queue
- Skipped queue
By default, Blnk uses the queue to process each item. The response returns immediately; the
queued status means the job is queued, not committed. Parents stay INFLIGHT until workers create APPLIED children.Per item results:200 Queued
Error handling
Structured errors are available from Blnk Core 0.15.0 and later.
400 when the request body fails validation before processing starts. Per-item failures return 200 with failed entries in results[]; one failed item does not block the batch.
- Request validation
- Per-item results
Bulk commit expects a
transactions array. Bulk void expects transaction_ids. Sending the wrong shape returns TXN_BULK_EMPTY because unrecognized fields are dropped.400 Bad Request
TXN_COMMIT_AMOUNT_EXCEEDED apply when you use Update inflight instead of these bulk endpoints.
See Commit & void inflight - Error handling and API error codes.