• 228 destinations
  • No KYC, ever
  • Bitcoin, Monero, USDT and 4 more

API and integration

Batch endpoint

A batch endpoint accepts many messages in one API request, each with its own recipient and text, and returns an individual result per message so that one invalid row does not fail the whole send.

Sending a campaign as ten thousand single requests is slow, and it runs into the rate limit long before it finishes. A batch endpoint takes many messages in one call: shared defaults at the top, such as the sender, a campaign tag, a schedule and a pace, and below them the messages, each with its own recipient and text and any overrides.

Validation happens at two levels. A malformed request, broken JSON or a missing list, is refused as a whole and nothing is queued. A well-formed one is judged message by message: valid messages are accepted and queued, while invalid ones, an unsupported prefix or a number that is not E.164, come back rejected with their error in the same list. A success status on the request therefore means the batch was processed, not that every message was accepted, and the response has to be read item by item. Pairing the batch with an idempotency key stops a retry after a timeout from queuing it twice.

Example

A hypothetical clinic sends three reminders in one batch. Two numbers are valid; the third has a prefix no route serves. The response reports two accepted, with message ids, and one rejected, with its error. The clinic corrects the third number and sends it on its own, rather than resending the batch, which would duplicate the first two.

Common mistakes

  • Reading a success response as "all sent" without checking the per-message results.
  • Resending a whole batch after a partial rejection.
  • Putting urgent codes in the same batch as a slow, paced campaign.

At SMSMeteor: POST /v1/messages/batch takes up to 1,000 messages per request. Batch-level from, campaign, send_at, window and pace (per_minute or over_hours) apply to every message that does not override them. A malformed request is refused as a whole; invalid items return as rejected with their error and are never billed, while valid ones are queued. The response carries batch_id, accepted, rejected, total_price and messages[], and a batch counts as one request against the rate limit. See the batch reference and how rejections are listed.

Go further

See the term in practice.An email address opens the account, the rate card is public, payment is crypto, the test key is free.
Start sending