TextMessageBatchSubmissionResponse
The 202 submission response: the batch summary, one pre-created message per created recipient, and the rejected entries.
text_messages 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_text_messages lists every submitted recipient Resia did not create, each with its
0-based submission position. text_messages and rejected_text_messages together account
for every submitted recipient.
A repeated Idempotency-Key returns the same batch again — the same batch ID, the same
text_message_id values, and the same recipients reported as rejected.
- countsType: TextMessageBatchCountsrequiredProperties: 6
How the batch's recipients are distributed across states right now.
- createdType: stringFormat: date-time
_at requiredWhen Resia accepted the batch.
- fromType: string
_phone _number requiredThe sender number every message in the batch texts from.
- 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 recipients the batch created. Equal to the submitted count minus the rejected entries; zero when every recipient was rejected.
- completedType: stringFormat: date-timenullable
_at When the batch reached a terminal state, or null while it is still in progress.
- rejectedType: array of BatchRejectedEntry …1000
_text _messages Properties: 4Every submitted recipient Resia did not create, each with its 0-based submission position and the reason. Empty when every recipient was created.
- textType: array of TextMessageBatchItem …1000
_messages Properties: 5One item per created recipient, in submission order (one cutover exception — see TextMessageBatchItemPage), each with its final text_message_id. Empty when every submitted recipient was rejected.

