{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/notifications.push-to-devices/",
    "json": "https://www.anchorterminal.com/niches/notifications.push-to-devices/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/notifications.push-to-devices/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/notifications.push-to-devices/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 9 | 26 | 10 | 4 |\n\n## What counts as done\n\nOne 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.\n\nHow agents ask for it: send a push to everyone on iOS; notify these device tokens; push to the user's phones\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n- 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.\n- not this job: Pingram (Pingram): Mobile Push discontinued on 7 August 2026, though pushTokens still appear in the send schema.\n- 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.\n\n## What stops agents finishing\n\n- only an app with registered tokens can be reached\n- token format migrations (FCM fid) reject valid devices\n\n## Around it\n\nBefore: code.app-registers-token. After: notifications.check-delivery.\n\n## Where this comes from\n\nWeight 10 of 100 in Notifications: 4 accounts (acc-21, acc-22, acc-24, acc-25) on FCM and Expo, all developers\n\nAs 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.\n",
  "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"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Push to an app's registered devices",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Push to an app's registered devices",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/notifications.push-to-devices/",
    "published": "",
    "section": "agents",
    "title": "Push to an app's registered devices: who does it | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/notifications.push-to-devices/"
  },
  "tokens": {
    "markdown": 1200,
    "slim": 330
  },
  "version": 1
}
