Skip to main content
POST /v1/emails/batch and POST /v1/sms/batch accept up to 1,000 messages. Each item is validated and queued independently, so one bad address never rejects the other 999. The batch counts as one request against the rate limit, which is why bulk sends should use it.
Response (200)

Rules

  • Results come back in input order with the item’s index.
  • The response is 200 even when some items fail. Check ok on each.
  • Idempotency-Key applies to the whole batch, not to items. Use tags to reconcile items with your own records.
  • Each item is paid for on its own: allowance first, then the wallet, then overage. Once nothing covers a send, the remaining items fail with allowance_exhausted (or insufficient_credits on pay as you go) and the earlier ones still go out.
  • SMS batches debit credits per item; if credits run out part-way, the remaining items fail with insufficient_credits and the earlier ones still send.
For a newsletter to thousands of people, send batches of 1,000 from a queue in your application, and set "class": "marketing" on every item so each email gets its unsubscribe headers.