# Prove a message was sent and find why one was not (slim)

> Prove a message was sent and find why one was not: 2 companies fully do it, 8 with a limit, 0 carry the tag. Every listing in Notifications with the reason and a source.

- Full: https://www.anchorterminal.com/niches/notifications.check-delivery/index.md (~1,200 tokens) · this version ~280 tokens · JSON https://www.anchorterminal.com/niches/notifications.check-delivery/index.json · canonical https://www.anchorterminal.com/niches/notifications.check-delivery/
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-15
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Two or three companies' docs show a full fit. Full fit: 2 companies, with a limit: 8, tagged: 0. Weight 8, 3 accounts.

Done when: A lookup by the id returns each channel's status (sent, delivered, failed, skipped by preference) with the provider's error and timestamps, kept for at least the period the docs state.
yes: courier (trycourier.com, Inc.)
yes: suprsend (SuprStack Inc)
caveat: amazon-sns (Amazon Web Services, Inc.)
caveat: expo-push-notifications (650 Industries, Inc.)
caveat: firebase-cloud-messaging (Google LLC)
caveat: knock (Knock Labs, Inc.)
caveat: magicbell (MagicBell, Inc.)
caveat: novu (Noti-Fire Apps Ltd.)
caveat: onesignal (OneSignal, Inc.)
caveat: pingram (Pingram)

Data: https://www.anchorterminal.com/api/v1/use-cases/notifications.check-delivery.json
