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.

  • How the batch's recipients are distributed across states right now.

    Properties: 6
  • When Resia accepted the batch.

  • The sender number every message in the batch texts from.

  • Identifier of the batch.

  • The batch's derived lifecycle state.

    values
    in_progresscompletedcanceled
  • How many recipients the batch created. Equal to the submitted count minus the rejected entries; zero when every recipient was rejected.

  • When the batch reached a terminal state, or null while it is still in progress.

  • Every submitted recipient Resia did not create, each with its 0-based submission position and the reason. Empty when every recipient was created.

    Properties: 4
  • One 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.

    Properties: 5