Ingests a batch of up to 1,000 transactions. Each transaction is validated against the workspace Transaction Definition for its type, linked to the relevant customer, persisted, and forwarded for transaction monitoring. The monitoring runs of these transactions send no process_run_start or process_run_end events. Returns HTTP 200 once the batch is accepted, even when individual items are rejected. Check the failed count and errors array in the response body. Returns HTTP 503 when the batch could not be accepted because a platform dependency was unavailable; retry the whole batch with the same transaction_id values. transaction_id is the idempotency key: always set it so a retry after a timeout or error is safe. A transaction sent without it is stored under a new random ID on every attempt, so a retry creates a duplicate. The idempotency-key header is ignored.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||