Transaction batch failures
API Reference
Transaction batch failures
Download CSV or JSON of failed transaction rows for a batch import job.
GET
Transaction batch failures
Endpoints
β¦/failures.csvβ CSV file download (Content-Disposition: attachment)β¦/failuresβ JSON body
Authentication
transactions:create, entities:bulk_import, events:create.
HTTP responses
| Status | When |
|---|---|
200 | Job found (CSV download or JSON body) |
401 | Not authenticated |
403 | Missing batch-import permission |
404 | Unknown jobId or job belongs to another organization |
CSV columns
| Column | Description |
|---|---|
external_id | Transaction externalId |
code | Stable failure code β catalog |
error | Human-readable message (same as message in JSON) |
code column) are normalized on download when possible.
JSON response
Always
true when job exists.Batch job id.
transaction_batchqueued | running | completed | failed | β¦Row failures:
{ externalId, code, message }. Empty when all rows succeeded or job failed entirely before per-row collection.Present when
status=failed for whole-batch errors (e.g. INVALID_ENTITY_REFERENCES): { code, message, details? }.true when more than 500 failures exist.Total failed rows stored for the job.
Default
batchErrorHandling=rollback_all aborts the batch on first insert error β often no row-level failures are stored. Use continue_collect_errors or stop_keep_success to populate this endpoint. Entity reference errors with validateExistingEntity=true fail the whole job (jobFailure), not individual CSV rows.