Niches · Messaging APIs

Confirm a message reached the person, and say why not

Two or three companies' docs show a full fit.

3companies, full fit
15companies, fit with a limit
42companies carry the tag
10share of the category's work
10first-hand accounts

What counts as done

For each message id, a final state (delivered, failed, undelivered, read where the channel has it) with the carrier or Meta error code, readable by API without a webhook.

Measured, for our own tests: the final state is readable within 5 minutes of sending. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: did my text go through, why didn't the customer get the message, which of the blast failed

Does the job 3

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Bird API + MCP A
Bird B.V.
Read endpoints return each message's status (delivered, undelivered, failed, expired, rejected) with last_error codes, and the delivery-errors guide maps provider codes; no webhook needed. No time to final state is documented, against the 5-minute bar. source
ClickSend SMS API + MCP D
ClickSend Pty Ltd
GET /v3/sms/receipts/{message_id} returns a message's delivery receipt by API, and receipt rules push the same; no webhook needed. No time to final state is documented, against the 5-minute bar. source
Plivo API B
Plivo Inc.
Retrieve a Message returns message_state (queued, sent, failed, delivered, undelivered, read) and a Plivo error_code by API, without a callback. No time to final state is documented, against the 5-minute bar. source

Does the job, with a limit 15

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
Status webhooks give sent, delivered, read and failed. Reading a message's state by API needs the Inbox API (GET /api/v1/messages/{id} with waba_payload errors), which is Premium only; the plain Messaging API is webhook only in the pages read. source
AWS End User Messaging BB
Amazon Web Services, Inc.
Delivery events with carrier status go to CloudWatch, Firehose or SNS event destinations; no GetMessage-style call returns a message's final state, so the agent queries its own log destination. source
Bandwidth Messaging API + MCP BB
Bandwidth Inc.
listMessages filters by messageId and returns messageStatus (DELIVERED, FAILED, UNDELIVERED and others) with errorCode, readable by API without a callback; the webhooks page explains codes such as 9902. Final state within 5 minutes isn't promised; error 9902 means no receipt came at all. source
Infobip API + MCP BB
Infobip Ltd
Delivery and seen reports can be pushed or fetched, with a failure status code per message. acc-22 shows a message left in PENDING_ENROUTE with no final state. source
Kudosity B
Known Pty Ltd
GET /v2/sms/{id}, /v2/mms/{id}, /v2/rcs/messages/{id} and /v2/whatsapp/messages/{id} read each message's state by API; DLR callbacks also push it. No time to final state is documented, against the 5-minute bar. source
Linq BB
Linq App Inc.
A message can be retrieved by id with error codes such as 4001 delivery failed and 4006 delivery uncertain, but SMS has no delivery receipts, so SMS sends never reach a final delivered state. source
Photon C
Something Great Inc.
WhatsApp status updates arrive in the event stream with cursors; for iMessage the pages read describe events but no per-message final state by id. source
Prelude B
DING SAS
Delivery and failure come by webhook, retried up to 2 weeks; for Verify, Get a phone verification reads the outcome. No Notify read endpoint for a message's state was found. source
Sendblue B
Round One, Inc.
GET /api/v2/messages filters by status and returns error_code; status callbacks also fire. Sendblue notes DELIVERED means the carrier accepted it, and no time to final state is given. source
Sinch Messaging APIs + MCP B
Sinch AB (publ)
Delivery reports (QUEUED_ON_CHANNEL, SUCCESS or FAILURE, READ) are per message by callback; the stored message read by GET carries no final delivery state in the spec read. source
Telnyx API + MCP BB
Telnyx LLC
Retrieve a message returns status and errors by API, but only for messages up to 10 days old; finalized webhooks also report it. No time to final state is documented. source
Twilio API + MCP A
Twilio Inc.
GET on a Message returns status (delivered, undelivered, failed) and error_code without a webhook, and acc-20 polled precisely that. No time to final state is promised; queued messages can wait up to 10 hours. source
Vonage Messages API + MCP B
Vonage Holdings Corp.
Final states come by status webhook; the Messages API has no GET for a message, and reading records by API means the separate Reports API, priced at $550 a month. source
Wati D
Clare.AI Limited
Delivered, read and failed arrive by webhook (Sent Message is DELIVERED, Template Message FAILED, Session Message Failed); messages can be read per conversation, but no per-message status read by id was found. source
YCloud B
YCloud International Pte. Ltd.
Final states arrive by whatsapp.message.updated webhooks; the v2 spec read has no GET for a WhatsApp or SMS message by id, so state can't be read back without a webhook. source

Doesn't do this job 2

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

ListingWhy
Telegram Bot API D
Telegram Messenger Inc.
Bots get no delivery or read receipts; a successful sendMessage response is the only signal. source
WhatsApp Business Platform (Cloud API) B
Meta Platforms, Inc.
Message status arrives only by the messages webhook; no endpoint reads a message's final state by id, so the criterion of reading it by API without a webhook can't be met. source

What stops agents finishing

  • send returns 200 and an id while the failure arrives only later by webhook, or never
  • no API to read a message's final state, only callbacks
  • error codes not linked back to the message or task that sent it

Around it

Before: messaging.send-notification, messaging.bulk-send. After: messaging.send-notification, crm.log-activity.

Where this comes from

Weight 10 of 100 in Messaging APIs: 10 of 69 accounts; silent failures after an accepted send recur across Twilio, AWS, Infobip, 360dialog and the WhatsApp Cloud API

The same as data: /api/v1/use-cases/messaging.confirm-delivery.json, or the MCP tool get_use_case with id messaging.confirm-delivery. 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.