TextMessageBatchCreateRequest
Submit up to a thousand recipients that all receive the same text and media from one owned sender.
A batch accepts a mix of good and bad recipients. Each recipient is checked on its own: one Resia cannot text — a destination its policy refuses, a malformed number, or a destination repeated within the batch — is reported in the 202 response as a rejected entry, and the rest of the batch is still created. A batch in which every recipient is rejected still returns 202, with an empty batch and every recipient in the rejected list. The text is preserved exactly as given.
- fromType: string
_phone _number requiredAn owned sender number the batch texts from.
- textType: stringmax length:1600required
Text shared by every recipient, preserved exactly as supplied. Nonempty text must not be blank. An empty string requires at least one media URL.
- textType: array of TextMessageBatchEntryRequest 1…1000
_messages requiredProperties: 2The recipients to text, in submission order. Duplicate destinations are allowed: the first is created and each later one is reported as a rejected entry.
- mediaType: array of string
_urls min length:1Format: uriOrdered HTTPS media URLs shared by every recipient. Keep each URL accessible to the carrier until the messages leave the queue.
- tagsType: TagsnullableProperties: 1
Labels copied onto every message this batch creates. Any keys and values. Filter GET /v1/text-messages by one key and value pair.

