Sends up to 10,000 transactions of a single type as an NDJSON stream: one JSON object per line,
Content-Type: application/x-ndjson.

🚧

Test environment: 50 transactions per batch

On https://api-test.brinta.com a batch accepts only 50 lines. Lines after the 50th are
not processed and do not appear in the summary or the results. Production accepts up to 10,000.

The transaction type comes from the path, so every line in a batch has the same type:

Each line is the body you would send to the single-resource endpoint, with two differences:

• transaction_external_id is required. It correlates results with your records and
  deduplicates retries.
• type must not be sent. A line that includes it fails with error_field: "type".

Brinta reads, validates and queues the lines as they arrive, then responds 202. Lines that
fail validation are recorded as failed and are not processed. The response carries the
batch_id; read the outcome with GET /batches/transactions/{batch_id} and
GET /batches/transactions/{batch_id}/results.

🚧

Lines over the limit are not read

The limit is 10,000 non-empty lines in Production and 50 in Test. Lines after the limit,
or past the request size limit, are not processed and do not
appear in the summary or the results. Split larger loads into several batches and check
that summary.total matches the number of lines you sent.