Use this endpoint to upload a transaction file (CSV, JSON, or XML) for ingestion into a reconciliation context. The file is parsed, validated, and transactions are extracted for matching.
Bearer token authentication (format: "Bearer {token}")
A unique identifier for tracing the request across services.
Optional idempotency key for safe retries. Also accepts Idempotency-Key as an alternative header name. If the same key is sent again and the original request was already processed, the cached response is returned with X-Idempotency-Replayed: true.
See Retries and idempotency for details.
The unique identifier of the reconciliation context.
The unique identifier of the reconciliation source.
Indicates that the request was accepted for processing.
The response includes the X-Idempotency-Replayed header.
If the value is false, the request was just processed. If the value is true, the response is a replay of a previously processed request.
See Retries and idempotency for more details.
Ingestion job details
When the job completed in RFC3339 format (if completed)
"2025-01-15T10:35:00.000Z"
Context ID this job belongs to
"019c96a0-10a0-72d2-9fb0-2b7de8093182"
Creation timestamp in RFC3339 format
"2025-01-15T10:30:00.000Z"
Number of rows that failed processing
x >= 05
Original file name
"transactions_2024.csv"
Unique identifier for the job
"019c96a0-10ce-75fc-a273-dc799079a99c"
Source ID this job ingests data into
"019c96a0-108c-7a74-8e31-3789daffe1ed"
When the job started in RFC3339 format (null for QUEUED jobs)
"2025-01-15T10:30:00.000Z"
Current status of the job
QUEUED, PROCESSING, COMPLETED, FAILED "PROCESSING"
Total number of rows in the file
x >= 01000