Skip to main content
Receive data from X, Telegram, and Discord the instant it’s captured — via WebSocket or SSE. All streams deliver the same SourceEvent payload used by webhooks.

WebSocket

Full-duplex, bidirectional — authenticate via x-api-key header. Supports ping/pong keepalive, fast-x mode, and payload filtering.

Server-Sent Events

Unidirectional, auto-reconnect — public stream (no auth, truncated) or private stream (token auth, full data).

At a Glance

Stream Payload

All streams deliver the same SourceEvent shape — identical to what webhooks receive:
See X, Telegram, or Discord for full payload examples per source.

Query Parameters

Both WebSocket and SSE support these query parameters:
fast-x delivers post data within ~50ms of posting, before the full GraphQL enrichment pass. The enriched x payload follows shortly after with complete metadata (engagement counts, media, entities).

Quick Start

1

WebSocket

Connect with your API key for full bidirectional streaming.
2

Public SSE (no auth)

Open a stream instantly — no API key needed. Data is truncated.
3

Private SSE (full data)

Generate a token, then connect for full payloads.