Niches · Messaging APIs

Send the same templated message to a list

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
17companies, fit with a limit
41companies carry the tag
4share of the category's work
5first-hand accounts

What counts as done

Every opted-in recipient gets one personalised message, per-recipient results come back, and a retry resends only the failed subset, at a cost quoted before sending.

How agents ask for it: text everyone on this list, send the campaign on WhatsApp, blast the members about tonight

Does the job, with a limit 17

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
360dialog WhatsApp API + MCP D
360dialog GmbH
One template send per recipient, each with its own id and status webhook, so failures can be resent; no batch endpoint, no idempotency key and no price quote before sending. Marketing sends through /messages cost 7 per cent more. source
AWS End User Messaging BB
Amazon Web Services, Inc.
One destination per SendTextMessage, at 1 request a second by default, with no idempotency token and no price quote; the agent loops and tracks MessageIds itself. source
Bandwidth Messaging API + MCP BB
Bandwidth Inc.
No batch endpoint found; several numbers in `to` makes a group message, so the agent sends one per recipient and tracks each by callback or listMessages. No idempotency key in the spec and no price quote. source
Bird API + MCP A
Bird B.V.
POST /v1/sms/batches sends up to 100 messages with per-message results and an Idempotency-Key, so only failures need resending. Cost is priced after acceptance, so no quote before the send. source
ClickSend SMS API + MCP D
ClickSend Pty Ltd
One send takes a messages array or a list_id with custom_string per message, and /v3/sms/price quotes the batch first. No idempotency key is documented, so a retried batch can double-send. source
Infobip API + MCP BB
Infobip Ltd
One request sends to many recipients with a bulkId and a messageId and status per message, so failures can be resent. No idempotency key, so a whole retried request can double-send. source
Kudosity B
Known Pty Ltd
Sends are one recipient each (WhatsApp says so explicitly) with message_ref, and an Idempotency-Key header is defined, but the spec lists it on no operation and there is no price quote. source
Plivo API B
Plivo Inc.
dst takes several numbers separated by <, with message UUIDs per recipient, but there is no idempotency key and no price quote before sending. source
Prelude B
DING SAS
Send bulk messages takes recipients with their own variables and returns a result per recipient in order, so only failures need resending. No idempotency key or price quote was found. source
Sinch Messaging APIs + MCP B
Sinch AB (publ)
Conversation API sends one message per request and request_id is not used for idempotency, so a retry can double-send; the batch SMS API sits under /docs/sms/, which robots.txt closes. source
Telegram Bot API D
Telegram Messenger Inc.
Free sends at about 30 messages a second (up to 1,000 with paid broadcasts at 0.1 Stars each), one call per chat so each returns its own result; no idempotency key, and only subscribers who started the bot. source
Telnyx API + MCP BB
Telnyx LLC
One send per recipient with an Idempotency-Key, so retries resend only failures safely, and a daily spend limit caps a runaway loop; no batch SMS endpoint or price quote was found. source
Twilio API + MCP A
Twilio Inc.
One create per recipient gives each its own SID and status, so failures can be retried, and prices can be read first; there is no idempotency key, and acc-20's blast went undelivered from an unregistered number. source
Vonage Messages API + MCP B
Vonage Holdings Corp.
One message per POST with its own message_uuid; no idempotency key in the spec and no price quote, so a retried batch can double-send. source
Wati D
Clare.AI Limited
Send template messages takes many recipients with per-recipient errors, broadcasts list recipients, and POST /broadcasts/estimate-cost quotes a broadcast. No idempotency key, and Wati warns that requested recipients can be absent from the result. source
WhatsApp Business Platform (Cloud API) B
Meta Platforms, Inc.
One send per recipient with its own id and status webhook, and a max price can be set on marketing messages; a new portfolio reaches 250 recipients a day, and no idempotency key exists. source
YCloud B
YCloud International Pte. Ltd.
One enqueue per recipient with an externalId for reconciliation, queued to Meta at 60 a second; no idempotency key, so a blind retry can duplicate, and no price quote. source

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
Linq BB
Linq App Inc.
No batch send, and Linq's best practices say to design inbound-first and not use iMessage for cold outreach. source
Photon C
Something Great Inc.
Inbound-first by design, with 50 new conversations a line a day and Apple flagging bursts; no batch send. source
Sendblue B
Round One, Inc.
New contacts are capped at 50 a line a day and 15 an hour, with no batch endpoint; Sendblue is built for one-to-one threads. source

What stops agents finishing

  • unregistered sender drops the blast
  • a new WhatsApp business portfolio reaches only 250 recipients a day
  • no idempotency, so a batch retry double-sends

Around it

Before: lead-data.prospect-list-by-filter, crm.segment. After: messaging.confirm-delivery.

Where this comes from

Weight 4 of 100 in Messaging APIs: 5 of 69 accounts; few first-hand reports, and Show HN campaign tools were left out as promotional

The same as data: /api/v1/use-cases/messaging.bulk-send.json, or the MCP tool get_use_case with id messaging.bulk-send. Other jobs in this category: /api/v1/niches?category=messaging.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.