POST /sms/batch to submit multiple independent SMS messages in one HTTP request. A batch can contain between 1 and 50 messages.
Send a batch
The preferred request shape is a top-level JSON array:messages:
Response ordering
A successful request returns202 Accepted. Every item in data corresponds to the request item at the same zero-based index:
Atomic acceptance
Before committing a batch, Dugble validates every destination, sender ID, body, metadata value, and schedule. It also resolves each destination country and calculates the SMS segment count. The messages and their durable delivery jobs are then created in one transaction. If any item is invalid or the transaction fails, none of the messages are committed.Atomic acceptance does not guarantee atomic delivery. Once accepted, each SMS has its own provider and carrier delivery lifecycle.
Best practices
- Use one idempotency key for the complete batch request.
- Preserve request ordering when storing returned IDs.
- Split workloads larger than 50 messages into independent requests with independent keys.
- Group messages by business operation rather than combining unrelated sends.
- Retrieve individual messages when you need delivery details.