# Push to an app's registered devices

> Push to an app's registered devices: 0 companies fully do it, 9 with a limit, 26 carry the tag. Every listing in Notifications with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/notifications.push-to-devices/
- Markdown: https://www.anchorterminal.com/niches/notifications.push-to-devices/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/notifications.push-to-devices/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/notifications.push-to-devices/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 | 9 | 26 | 10 | 4 |

## What counts as done

One request per batch reaches iOS and Android tokens, the response reports per-token success or a coded failure such as unregistered, and the agent can drop dead tokens from that code alone.

How agents ask for it: send a push to everyone on iOS; notify these device tokens; push to the user's phones

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

- **Amazon SNS (Amazon Web Services, Inc.)**: Platform endpoints wrap APNs and FCM tokens, and SNS disables an endpoint the provider rejects, but a direct publish goes to one endpoint ARN; batches go through a topic with no per-token result in the response.
- **Courier (trycourier.com, Inc.)**: Push goes to tokens synced to the user profile through FCM or APNs, but the send returns only a requestId; per-token results come later from message logs and webhooks.
- **Expo Push Notifications (650 Industries, Inc.)**: One POST takes up to 100 messages for iOS and Android, each ticket in order with status and DeviceNotRegistered on dead tokens. acc-25 got ok receipts while nothing showed on iOS, and there is no idempotency key.
- **Firebase Cloud Messaging (Google LLC)**: Admin SDK sendEachForMulticast takes up to 500 FIDs or tokens with per-item responses in order, and UNREGISTERED (404) marks dead tokens; HTTP v1 itself is one message per request. acc-21 got NotRegistered for a live FID and acc-24 an undefined error code.
- **Knock (Knock Labs, Inc.)**: Push goes to tokens stored as channel data through your APNs or FCM provider, but the trigger returns only a run id; per-token outcomes come later from message statuses and delivery logs, not the response.
- **MagicBell (MagicBell, Inc.)**: Saved APNs, FCM and Expo tokens per user are reached by one broadcast, but the broadcast status gives only summary counts and error messages, not per-token codes.
- **Novu (Noti-Fire Apps Ltd.)**: Push steps send to subscriber device tokens through FCM, APNs, Expo and others, but the trigger response carries a transactionId only; per-token outcomes come from messages and push activity tracking afterwards.
- **OneSignal (OneSignal, Inc.)**: One call reaches up to 20,000 subscription ids on iOS and Android, and the response lists invalid_aliases and invalid_player_ids for unsubscribed targets, but not a per-token code such as unregistered versus invalid payload.
- **SuprSend (SuprStack Inc)**: Push goes to user push tokens through connected FCM and APNs vendors, and FCM errors are documented, but the trigger returns message ids, not per-token results; outcomes come from message logs.

- not this job: ntfy (ntfy LLC): Reaches only devices subscribed to a topic in the ntfy app, not an app's own APNs or FCM tokens, and returns no per-device result.
- not this job: Pingram (Pingram): Mobile Push discontinued on 7 August 2026, though pushTokens still appear in the send schema.
- not this job: Pushover (Pushover, LLC): Reaches devices running the Pushover app by user or group key, not an app's own APNs or FCM tokens.

## What stops agents finishing

- only an app with registered tokens can be reached
- token format migrations (FCM fid) reject valid devices

## Around it

Before: code.app-registers-token. After: notifications.check-delivery.

## Where this comes from

Weight 10 of 100 in Notifications: 4 accounts (acc-21, acc-22, acc-24, acc-25) on FCM and Expo, all developers

As data: https://www.anchorterminal.com/api/v1/use-cases/notifications.push-to-devices.json, or the MCP tool get_use_case with id notifications.push-to-devices. 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
