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
| Feature | WebSocket | Public SSE | Private SSE |
|---|---|---|---|
| Endpoint | wss://scrape.st/ws | https://scrape.st/stream | https://scrape.st/stream?token= |
| Auth | x-api-key header | None | Token via /stream/token |
| Payload | Full SourceEvent | Truncated (first 100 chars) | Full SourceEvent |
| Direction | Bidirectional | Server → Client | Server → Client |
| Reconnect | Manual (implement yourself) | Automatic (EventSource built-in) | Automatic |
| Sources | X, Telegram, Discord | fast-x, Telegram, Discord | fast-x, Telegram, Discord |
Stream Payload
All streams deliver the sameSourceEvent shape — identical to what webhooks receive:
Query Parameters
Both WebSocket and SSE support these query parameters:| Parameter | Type | Description |
|---|---|---|
useFastX | boolean | Receive fast-x push events immediately (before GraphQL enrichment) |
ignoreFullPayload | boolean | Skip full enriched X payloads — only receive fast-x + other sources |
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).