Cancel a bulk request
Sets cancellation_requested_at so the running job exits cleanly to cancelled on its next heartbeat. Idempotent — re-cancelling just bumps the timestamp.
Authorizations
Path Parameters
Response
Cancellation requested
Full bulk request payload, returned by show, list, cancel, and retry endpoints.
pending = queued, processing = records being inserted, completed = all rows processed, failed = job errored, cancelled = cancellation honored on a heartbeat
pending, processing, completed, failed, cancelled Origin of the request (e.g. bulk_api, csv, nacha)
Records skipped due to on_conflict: skip matching an existing external_id
processed_items / total_items as a percentage (0-100)
Original filename for CSV/NACHA uploads. Null for API-submitted requests.
Heartbeat timestamp from the worker; used to detect stuck jobs
Set by POST /bulk_requests/{id}/cancel; the worker exits at its next heartbeat
True while a CSV/NACHA upload is still being parsed (before rows are enqueued)
True if the request has been processing for more than 5 minutes without a heartbeat
Free-form structured error context (e.g. row indices, validation errors)
If this request is a retry, the ID of the original (parent) bulk request
Conflict policy applied when an external_id already exists in the stream
skip, error Data stream the request targets, when applicable