# Send the same templated message to a list

> Send the same templated message to a list: 0 companies fully do it, 17 with a limit, 41 carry the tag. Every listing in Messaging APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/messaging.bulk-send/
- Markdown: https://www.anchorterminal.com/niches/messaging.bulk-send/index.md (~1,650 tokens)
- Slim: https://www.anchorterminal.com/niches/messaging.bulk-send/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/messaging.bulk-send/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

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

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 17 | 41 | 4 | 5 |

## 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

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.

- **360dialog WhatsApp API + MCP (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.
- **AWS End User Messaging (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.
- **Bandwidth Messaging API + MCP (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.
- **Bird API + MCP (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.
- **ClickSend SMS API + MCP (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.
- **Infobip API + MCP (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.
- **Kudosity (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.
- **Plivo API (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.
- **Prelude (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.
- **Sinch Messaging APIs + MCP (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.
- **Telegram Bot API (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.
- **Telnyx API + MCP (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.
- **Twilio API + MCP (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.
- **Vonage Messages API + MCP (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.
- **Wati (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.
- **WhatsApp Business Platform (Cloud API) (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.
- **YCloud (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.

- not this job: Linq (Linq App Inc.): No batch send, and Linq's best practices say to design inbound-first and not use iMessage for cold outreach.
- not this job: Photon (Something Great Inc.): Inbound-first by design, with 50 new conversations a line a day and Apple flagging bursts; no batch send.
- not this job: Sendblue (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.

## 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

As data: https://www.anchorterminal.com/api/v1/use-cases/messaging.bulk-send.json, or the MCP tool get_use_case with id messaging.bulk-send. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
