Niches · Notifications

Prove a message was sent and find why one was not

Two or three companies' docs show a full fit.

2companies, full fit
8companies, fit with a limit
0companies carry the tag
8share of the category's work
3first-hand accounts

What counts as done

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.

How agents ask for it: did the user get the alert, why didn't my push arrive, show the delivery log for this message

Does the job 2

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

ListingWhy
Courier B
trycourier.com, Inc.
GET /messages/{id} and /history give status (including UNROUTABLE with reason UNSUBSCRIBED or FILTERED), timeline and the provider's raw response; message history is kept 30 days on Developer and Business, 365 on Enterprise. source
SuprSend BB
SuprStack Inc
List Messages filters by message_id, idempotency_key, workflow, channel and status (delivered, seen, delivery_failed, failure_by_vendor) with vendor errors; logs are kept 30 days on Free and 90 on Essentials and Business. source

Does the job, with a limit 8

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
Amazon SNS BB
Amazon Web Services, Inc.
Delivery status logging to CloudWatch covers platform endpoints, HTTPS, Lambda, SQS and Firehose once configured with IAM, but there is no lookup by MessageId in the SNS API and email is not covered. source
Expo Push Notifications B
650 Industries, Inc.
getReceipts by ticket id returns status and details.error such as DeviceNotRegistered, but ok means only APNs or FCM accepted it, receipts are cleared after 24 hours, and acc-25 saw ok with nothing delivered. source
Firebase Cloud Messaging BB
Google LLC
No lookup by message id in the API. Delivery is aggregated per app by the FCM Data API (Android only), and per-message events need a BigQuery export. source
Knock A
Knock Labs, Inc.
Messages carry queued, sent, delivered, undelivered, bounced and not_sent, and list_delivery_logs returns the provider request and response, kept 30 days (90 on Enterprise). A preference skip shows in the workflow debugger; an API field for it was not found. source
MagicBell C
MagicBell, Inc.
GET /broadcasts/{id} returns status, error messages and failure counts, and GET /events gives coded events with logs, but events filter only by pagination and no retention period is stated. source
Novu B
Noti-Fire Apps Ltd.
Retrieve an event returns execution logs and each step's message, and messages filter by transactionId. The activity feed is kept 1 day on Free and 7 on Pro, the blocker the map names. source
OneSignal BB
OneSignal, Inc.
View message returns per-message counts and outcomes; per-subscription history is a CSV export kept 7 days, only if enabled beforehand, and sends under 1,000 recipients record no received event. source
Pingram C
Pingram
GET /logs/status takes up to 25 trackingIds and returns channel, status and time, but for email and SMS only; retention is read per account by API and not stated in docs. source

Doesn't do this job 2

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

ListingWhy
ntfy C
ntfy LLC
Messages are cached 12 hours for polling, but there is no per-message delivered or failed status to look up. source
Pushover C
Pushover, LLC
Only emergency-priority sends get a receipt (last_delivered_at, acknowledged, kept one week); a normal send returns a request id with no status lookup. source

What stops agents finishing

  • log kept 1 day on a free plan
  • receipt says ok while the device shows nothing

Around it

Before: notifications.send-user-event, notifications.push-to-devices. After: support.answer-ticket.

Where this comes from

Weight 8 of 100 in Notifications: 3 accounts (acc-14, acc-23, acc-25) where the sender could not see what happened; acc-25 had ok receipts and no notification

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

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.