{
  "listings": [
    {
      "slug": "bird",
      "name": "Bird API + MCP",
      "company": "Bird B.V.",
      "grade": "A",
      "fit": "yes",
      "why": "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": "https://bird.com/docs/guides/sms/sending-sms.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/bird"
    },
    {
      "slug": "clicksend",
      "name": "ClickSend SMS API + MCP",
      "company": "ClickSend Pty Ltd",
      "grade": "D",
      "fit": "yes",
      "why": "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": "https://github.com/ClickSend/clicksend-python-v2/blob/HEAD/docs/SmsApi.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/clicksend"
    },
    {
      "slug": "plivo",
      "name": "Plivo API",
      "company": "Plivo Inc.",
      "grade": "B",
      "fit": "yes",
      "why": "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": "https://plivo.com/docs/messaging/api/messages.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/plivo"
    },
    {
      "slug": "360dialog",
      "name": "360dialog WhatsApp API + MCP",
      "company": "360dialog GmbH",
      "grade": "D",
      "fit": "caveat",
      "why": "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": "https://docs.360dialog.com/docs/messaging/webhook.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/360dialog"
    },
    {
      "slug": "aws-end-user-messaging",
      "name": "AWS End User Messaging",
      "company": "Amazon Web Services, Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://docs.aws.amazon.com/sms-voice/latest/userguide/llms.txt",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/aws-end-user-messaging"
    },
    {
      "slug": "bandwidth",
      "name": "Bandwidth Messaging API + MCP",
      "company": "Bandwidth Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://dev.bandwidth.com/spec/messaging.yml",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/bandwidth"
    },
    {
      "slug": "infobip",
      "name": "Infobip API + MCP",
      "company": "Infobip Ltd",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://www.infobip.com/docs/api/platform/messages-api",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/infobip"
    },
    {
      "slug": "kudosity",
      "name": "Kudosity",
      "company": "Known Pty Ltd",
      "grade": "B",
      "fit": "caveat",
      "why": "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": "https://developers.kudosity.com/openapi/public-openapi.yaml",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/kudosity"
    },
    {
      "slug": "linq",
      "name": "Linq",
      "company": "Linq App Inc.",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://docs.linqapp.com/channel/imessage/guides/messaging/protocol-selection/index.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/linq"
    },
    {
      "slug": "photon",
      "name": "Photon",
      "company": "Something Great Inc.",
      "grade": "C",
      "fit": "caveat",
      "why": "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": "https://photon.codes/docs/advanced-kits/whatsapp/events.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/photon"
    },
    {
      "slug": "prelude",
      "name": "Prelude",
      "company": "DING SAS",
      "grade": "B",
      "fit": "caveat",
      "why": "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": "https://docs.prelude.so/notify/v2/documentation/webhook.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/prelude"
    },
    {
      "slug": "sendblue",
      "name": "Sendblue",
      "company": "Round One, Inc.",
      "grade": "B",
      "fit": "caveat",
      "why": "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": "https://docs.sendblue.com/getting-started/sending-messages/index.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/sendblue"
    },
    {
      "slug": "sinch",
      "name": "Sinch Messaging APIs + MCP",
      "company": "Sinch AB (publ)",
      "grade": "B",
      "fit": "caveat",
      "why": "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": "https://developers.sinch.com/docs/conversation/callbacks.md",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/sinch"
    },
    {
      "slug": "telnyx",
      "name": "Telnyx API + MCP",
      "company": "Telnyx LLC",
      "grade": "BB",
      "fit": "caveat",
      "why": "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": "https://developers.telnyx.com/public/llms/messaging.txt",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/telnyx"
    },
    {
      "slug": "twilio",
      "name": "Twilio API + MCP",
      "company": "Twilio Inc.",
      "grade": "A",
      "fit": "caveat",
      "why": "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": "https://www.twilio.com/docs/messaging/api/message-resource.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/twilio"
    },
    {
      "slug": "vonage",
      "name": "Vonage Messages API + MCP",
      "company": "Vonage Holdings Corp.",
      "grade": "B",
      "fit": "caveat",
      "why": "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": "https://developer.vonage.com/api/v1/developer/api/file/messages?format=json",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/vonage"
    },
    {
      "slug": "wati",
      "name": "Wati",
      "company": "Clare.AI Limited",
      "grade": "D",
      "fit": "caveat",
      "why": "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": "https://docs.wati.io/llms.txt",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/wati"
    },
    {
      "slug": "ycloud",
      "name": "YCloud",
      "company": "YCloud International Pte. Ltd.",
      "grade": "B",
      "fit": "caveat",
      "why": "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": "https://docs.ycloud.com/openapi/endpoints/ycloud-api-v2.yaml",
      "confidence": "medium",
      "url": "https://www.anchorterminal.com/tools/ycloud"
    },
    {
      "slug": "telegram-bot",
      "name": "Telegram Bot API",
      "company": "Telegram Messenger Inc.",
      "grade": "D",
      "fit": "no",
      "why": "Bots get no delivery or read receipts; a successful sendMessage response is the only signal.",
      "source": "https://core.telegram.org/bots/api",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/telegram-bot"
    },
    {
      "slug": "whatsapp-cloud-api",
      "name": "WhatsApp Business Platform (Cloud API)",
      "company": "Meta Platforms, Inc.",
      "grade": "B",
      "fit": "no",
      "why": "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": "https://developers.facebook.com/documentation/business-messaging/whatsapp/webhooks/overview.md",
      "confidence": "high",
      "url": "https://www.anchorterminal.com/tools/whatsapp-cloud-api"
    }
  ],
  "marks": "yes: the docs show it does the job as the success test says. caveat: it does the job with a limit an agent should know. no: it doesn't do this job. unchecked: we couldn't read it.",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "useCase": {
    "accounts": 10,
    "after": [
      "messaging.send-notification",
      "crm.log-activity"
    ],
    "area": "communication",
    "asks": [
      "did my text go through",
      "why didn't the customer get the message",
      "which of the blast failed"
    ],
    "before": [
      "messaging.send-notification",
      "messaging.bulk-send"
    ],
    "blockers": [
      "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"
    ],
    "capabilities": [
      "messaging.inbound"
    ],
    "category": "messaging",
    "categoryName": "Messaging APIs",
    "checked": "2026-11-15",
    "companies": {
      "fit": 3,
      "fitWithLimit": 15,
      "tagged": 42
    },
    "competition": "few",
    "fits": [
      "bird",
      "clicksend",
      "plivo"
    ],
    "fitsWithLimit": [
      "360dialog",
      "aws-end-user-messaging",
      "bandwidth",
      "infobip",
      "kudosity",
      "linq",
      "photon",
      "prelude",
      "sendblue",
      "sinch",
      "telnyx",
      "twilio",
      "vonage",
      "wati",
      "ycloud"
    ],
    "id": "messaging.confirm-delivery",
    "listings": {
      "caveat": 15,
      "no": 2,
      "notRead": 0,
      "tagged": 42,
      "unchecked": 0,
      "yes": 3
    },
    "name": "Confirm a message reached the person, and say why not",
    "status": "draft",
    "success": "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: the final state is readable within 5 minutes of sending.",
    "url": "https://www.anchorterminal.com/api/v1/use-cases/messaging.confirm-delivery.json",
    "weight": 10,
    "weightBasis": "10 of 69 accounts; silent failures after an accepted send recur across Twilio, AWS, Infobip, 360dialog and the WhatsApp Cloud API"
  }
}
