Put market-moving posts into your strategy before the crowd
TweetStream streams monitored X posts, account signals, token matches, OCR, and live prices over one WebSocket.
Route by t and op: content envelopes carry author, text, timestamps, and media; meta envelopes carry OCR text plus detected tokens, markets, and prices.
Payload shape your bot can inspect
[
{
"v": 1,
"t": "tweet",
"op": "content",
"id": "2064689031777615872",
"ts": 1781095200123,
"d": {
"tweetId": "2064689031777615872",
"kind": "post",
"text": "New token live. CA: 9xQeWvG816bUx9EP...",
"createdAt": 1781095199900,
"receivedAt": 1781095200108,
"author": {
"handle": "@marketdesk",
"name": "Market Account"
},
"media": [
{
"type": "image",
"url": "https://pbs.twimg.com/media/sample-token-chart.jpg"
}
]
}
},
{
"v": 1,
"t": "tweet",
"op": "meta",
"id": "2064689031777615872",
"ts": 1781095200340,
"d": {
"tweetId": "2064689031777615872",
"ocr": {
"text": "ticker $EDGE, liquidity rising"
},
"detected": {
"tokens": [
{
"symbol": "EDGE",
"contract": "9xQeWvG816bUx9EP...",
"chain": "solana",
"priceUsd": 0.0042,
"sources": ["text", "ocr"]
}
]
}
}
}
]- 167ms median server detection
- 5 trial accounts
- 300K X API Post reads cost ~$1,500/mo; Minimum covers 50 accounts for $199/mo
167ms median server detection is measured from production event timestamps as server receive time minus tweet snowflake timestamp. Geolocate your consumer near the endpoint for the shortest delivery path.
The 3-day trial uses the same detection pipeline as paid plans with 5 tracked accounts and 1 WebSocket connection. Minimum continues at $199/mo after trial with 50 monitored accounts and 3 connections unless you manage or cancel from the dashboard.
Need code first? Open the quickstart guide
What the WebSocket feed includes
Built for the accounts that move crypto and prediction markets: one event stream from first post to enriched signal, without a polling or scraper stack.
Tweet alerts that catch the state change
Stream new posts, updates, deletes, pins, and unpins from the accounts in your watchlist, including author fields, media, links, and quote or reply context when available.
Account profile and follow events
Use account event envelopes for profile updates, follow notifications, and unfollow notifications instead of building a separate account-monitoring job.
Trading enrichment
OCR, token detection, exchange references, prediction-market detection, and live price context are attached when TweetStream detects a signal.
A practical WebSocket protocol
Every message uses the same envelope shape, so bots can route tweet, account, and control events without custom parsing for each feature.
Why teams use TweetStream as a Twitter monitor API
- No polling loop to tune, babysit, or rebuild when traffic spikes
- Published server-detection methodology
- Crypto-specific enrichment your team would otherwise build after ingest
- Flat monitored-account limits instead of metered reads for every workflow
Built for the monitored-account workflow
Most crypto teams do not need every public post. They need the small set of accounts that moves price to reach their systems quickly and cleanly.
- Pick the handles. Add the accounts your desk, bot, or Discord channel already watches.
- Open one socket. Authenticate once and receive live JSON envelopes for tweet, account, and control events.
- Route the signal. Send alerts into trading logic, dashboards, Discord, or history replay without maintaining a scraper stack.
Open the WebSocket in minutes
You only need the endpoint and protocols:
WebSocket endpoint: wss://ws.tweetstream.io/ws
Protocols: tweetstream.v1, tweetstream.auth.token.YOUR_API_KEY
See the WebSocket quickstart guide for full examples.
Where this fits
Use TweetStream when speed, payload shape, and enrichment matter more than broad social listening. If you need official write access, compliance archives, or every X API endpoint, use the official X API alongside TweetStream.
X/Twitter monitor API questions
Is TweetStream the official X/Twitter API?
No. TweetStream is an independent monitored-account alert API. It is built for teams that need fast WebSocket delivery and trading enrichment from selected X/Twitter accounts.
Is this a WebSocket firehose for every public tweet?
No. TweetStream streams alerts from the accounts and filters you configure. That keeps the feed focused and avoids forcing your bot to process broad social noise.
What events can I receive over WebSocket?
TweetStream sends tweet content, tweet metadata, tweet updates, delete, pin, and unpin operations where available, account profile updates, follow and unfollow events, and control responses for handle-management actions.
Why use TweetStream instead of polling?
Polling adds delay, retry logic, rate-limit handling, and parsing work. TweetStream keeps one WebSocket connection open and pushes monitored-account events as they arrive.