Stream events (Server-Sent Events)
GET
https://fomodata.devServer-Sent Events stream of realtime events, filtered like webhooks. Frames: id: <cursor>, event: <type>, data: <Event JSON>; a : ping comment every 15 s.
Reconnect with the Last-Event-ID header (browsers do this automatically) to resume after the last cursor — up to 1,000 missed events within your plan's history window are replayed first.
Counts toward your plan's concurrent stream connections (WebSocket + SSE). Test keys only receive test-mode events (sandbox data, livemode: false).
Example request
curl -N 'https://fomodata.dev/v1/events/stream?types=thesis.created&token=$RUN&handle=@milo&chain=robinhood' \
-H "Authorization: Bearer $FOMODATA_API_KEY"Parameters
Query parameters
typesstring- Comma-separated event types (default: all).
tokenstring- Comma-separated token refs ($SYMBOL, address, chain:address or tk_ id).
handlestring- Comma-separated Fomo handles.
chainstring- Comma-separated chains.
from_cursorstring- Resume after this cursor (an event frame's
id).Last-Event-IDtakes precedence.
Response
200 text/event-stream of Event objects
text/event-stream
A long-lived stream of id / event / data frames. See Server-Sent Events.
Errors
| Status | When |
|---|---|
401 | Missing, invalid, revoked or expired API key |
403 | Insufficient scope, live access not approved, or history limit |
404 | Not found (or feature disabled) |
422 | Validation failed |
429 | Rate limit or quota exceeded |
503 | Upstream unavailable |
All errors use the standard envelope. See error codes for every code value.