You can create a batch of journal requests by using this endpoint. This is enabled on JNLC type Journals for now only.
Every single request must be valid for the entire batch operation to succeed.
In the case of a successful request, the response will contain an array of journal objects with an extra attribute error_message in the case when a specific account fails to receive a journal.
Idempotency: When the Idempotency-Key header is supplied, this endpoint is
idempotent. Multiple requests with the same key and identical request body will
create only one batch. A subsequent request returns the previously created
batch with the same response (no duplicate is created). If the same key is used
with a different request body, the API returns 422 Unprocessable Entity.
Recommended for production: Always supply Idempotency-Key when creating
journal batches. This allows safe retries on timeouts, network errors, or 5xx responses
without risking duplicate batches. Use a client-generated unique value (e.g. UUID).