Home / Blog / Guides

Guides

The FOMO Notifications API: Whale Alerts, Price Spikes, and Profit Milestones

fomoapi.io exposes FOMO's mobile push notifications over a plain REST endpoint (/v2/notifications) and a realtime WebSocket (/ws/alerts). This post shows the real signals FOMO surfaces (whale buys and sells, price spikes, trade opens and closes, profit milestones, follows), how to filter them by type, and how to build an alert bot that reacts in real time.

Pixel-art realtime data stream carrying event pulses and alerts from servers to connected clients.

FOMO pushes alerts to its mobile app: a token is up 2x since it was verified, a whale just bought, a top trader opened or closed a position. Those pushes are a signal, and fomoapi.io exposes them over an API. GET /v2/notifications returns the push history; WS wss://api.fomoapi.io/ws/alerts streams activity live. This is the endpoint-first post: the real signals, the filters, and a realistic alert bot.

What FOMO actually pushes

/v2/notifications returns FOMO's mobile push notifications, distinct from the full activity firehose at /v2/alerts. The pushes include price alerts (for example "TOKEN up 2x since verification"), trade opens and closes, whale buys and sells, profit milestones, and follows. Many carry FOMO's own notification_type (like PRICE_SINCE_LISTED or LARGE_BUY); some pushes have none and are still returned.

curl "https://api.fomoapi.io/v2/notifications?limit=50" \
  -H "authorization: Bearer YOUR_API_KEY"

Narrow to one signal with notificationType, and page back through history with since (ISO or unix):

curl "https://api.fomoapi.io/v2/notifications?notificationType=LARGE_BUY&limit=50" \
  -H "authorization: Bearer YOUR_API_KEY"

Setting notificationType returns only the typed pushes that match; untyped pushes are excluded while the filter is on. Leave it off to see everything FOMO pushed.

REST for history, WebSocket for realtime

/v2/notifications is the right call to backfill or poll on a schedule. To react the instant something happens, open the WebSocket instead:

const ws = new WebSocket("wss://api.fomoapi.io/ws/alerts?key=YOUR_API_KEY");
ws.onmessage = (m) => {
  const e = JSON.parse(m.data);
  if (e.type !== "alert") return;
  // e carries token, tokenAddress, chainId, chain, source
  console.log(e.chain, e.token, e.source);
};

You can scope the stream to one trader with ?trader=<handle>, to one chain with ?chain=robinhood (chainId 4663), to one token, or to ?type=buy|sell|thesis. The WebSocket is realtime on any paid plan; a free key gets 7 days of realtime from creation, then drops to a 15-second-delayed feed. The full activity feed and the push feed are complementary: see Real-Time Memecoin Trade Alerts over WebSocket for the raw trade stream.

Building an alert bot

A whale-alert or milestone bot is a short loop. Take each realtime event, keep the ones you care about, resolve the trader, and post to Discord or Telegram:

  1. Connect the WebSocket with a chain and type filter (for example Robinhood Chain buys).
  2. On each event, apply a size threshold (a whale gate) or match a notification_type.
  3. Enrich: call GET /v2/users/<handle> for the trader's wallets and PnL so your alert carries a real track record, not just a name.
  4. Deliver the formatted message to your channel.

That is the whole pipeline. For a worked example, see Build a FOMO Whale-Alert Bot. The notifications endpoint is the same building block behind The FOMO Family API.

Get started

A free key unlocks /v2/notifications and 7 days of realtime WebSocket. Get one at /dashboard, read the reference at /docs, and see streaming limits at /pricing.

FOMO API is an independent, unofficial data layer for fomo.family. It is not affiliated with, endorsed by, or sponsored by fomo.family, fomoscan, or Robinhood.

Ship on fomo.family trader data

Both-chain wallets, PnL and holdings, plus two live streams: the app feed on every plan, the on-chain stream on Growth. One API.

Get an API key

FAQ

What is the FOMO notifications API?
It is the /v2/notifications endpoint on fomoapi.io, which returns FOMO's mobile push notifications: price alerts, trade opens and closes, whale buys and sells, profit milestones, and follows. It is distinct from /v2/alerts, which is the full activity firehose of every buy, sell, and thesis.
What notification types can I filter by?
Many pushes carry FOMO's own notification_type, such as PRICE_SINCE_LISTED or LARGE_BUY, and you narrow to one with ?notificationType=. Some pushes have no type and are still returned; setting the filter simply limits results to the typed pushes that match.
How do I get realtime whale alerts?
Open the WebSocket at wss://api.fomoapi.io/ws/alerts and filter with ?type=buy and a size threshold in your handler, optionally scoped with ?chain= or ?trader=. It is realtime on any paid plan; a free key is realtime for 7 days from creation, then 15-second-delayed.
Can I build a crypto trading alert bot on this?
Yes. Connect the WebSocket, filter events by chain, type, or size, enrich each with GET /v2/users/{handle} for the trader's wallets and PnL, and post to Discord or Telegram. A free key covers /v2/notifications plus 7 days of realtime to prototype with.
Is this affiliated with fomo.family?
No. fomoapi.io is an independent, unofficial data layer for fomo.family and is not affiliated with, endorsed by, or sponsored by fomo.family, fomoscan, or Robinhood.