Sends unique SMS or MMS messages to multiple recipients in a single API call. Unlike broadcast (which sends the same message to all recipients), batch allows a different body and/or mediaUrl per recipient. The recipients array must contain between 10 and 5,000 entries with unique phone numbers. Each recipient must have at least a body or a mediaUrl. Mixed SMS and MMS messages are supported within the same batch — recipients with a mediaUrl are sent as MMS, others as SMS. The sender number (from) must be an active number assigned to your account. The batch is queued as a background job — the response includes a batch id and initial status of queued. An optional idempotencyKey can be provided at the batch level and/or per recipient to prevent duplicate sends. If no idempotencyKey is provided, a unique one is auto-generated. Idempotency keys are tracked for 48 hours after a successful send — failed sends do not consume the key and can be retried.
Content compliance: Each recipient's message content is validated against messaging compliance rules (SHAFT, phishing, etc.). If any recipient's content violates these rules, the entire batch is rejected with error code 33019.
Rate limit: 5 requests per minute. Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. When the limit is exceeded, a 429 response is returned with a Retry-After header.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||