wss://scrape.st/ws for bidirectional, real-time data streaming across all sources. WebSocket delivers full SourceEvent payloads for every tracked source.
Connection
Query Parameters
Append to the WebSocket URL:Event categories (types)
Every message carries a top-level event field naming its category. By default
a connection only receives source events — opt into derived events explicitly:
types falls back to source.
Event Flow
WhenuseFastX=true, you receive two events per post:
fast-x— Arrives ~50ms after posting. Contains basic post data (text, author, timestamp) before GraphQL enrichment.x— Arrives ~200-500ms after posting. FullResolvedXPostwith engagement counts, media, entities, quoted posts.
ignoreFullPayload=true to skip the second event.
Keepalive
The server pings idle connections every 30 seconds. Connections with no activity for 60 seconds are terminated. To keep your connection alive, respond to pings (automatic in most WebSocket libraries) or send a manual ping:Reconnection
WebSocket does not auto-reconnect. Implement retry logic:Payload Shape
Every message carries anevent category and a stable id. A plain source
event looks like: