CallBatchSubmissionResponse
The 202 submission response: the batch summary, one pre-created call per created item, and the rejected entries.
calls keeps submission order, with one cutover exception: A batch that was partly processed when Resia moved to per-item IDs (2026-08-25) can order its items differently — match items by to_phone_number or client_reference.
rejected_calls lists every submitted entry Resia did not create, each with its 0-based
submission position. calls and rejected_calls together account for every submitted entry.
A repeated Idempotency-Key returns the same batch again — the same batch ID, the same
call_id values, and the same entries reported as rejected.
- callType: string
_agent _id min length:1max length:512requiredThe Call Agent every call in the batch follows.
- countsType: CallBatchCountsrequiredProperties: 8
How the batch's calls are distributed across states right now.
- createdType: stringFormat: date-time
_at requiredWhen Resia accepted the batch.
- idType: stringmin length:1max length:512required
Identifier of the batch.
- statusType: BatchStatusenumrequired
The batch's derived lifecycle state.
valuesin_progresscompletedcanceled - totalType: integermin:0required
How many calls the batch created. Equal to the submitted count minus the rejected entries; zero when every entry was rejected.
- callsType: array of CallBatchItem …1000Properties: 5
One item per created call, in submission order (one cutover exception — see CallBatchItemPage), each with its final call_id. Empty when every submitted entry was rejected.
- completedType: stringFormat: date-timenullable
_at When the batch reached a terminal state, or null while it is still in progress.
- fromType: stringnullable
_phone _number The caller number used, or null when the default was used.
- rejectedType: array of BatchRejectedEntry …1000
_calls Properties: 4Every submitted entry Resia did not create, each with its 0-based submission position and the reason. Empty when every entry was created.

