Live monitoring product
Real-Time Twitter WebSocket API: Tweets, Follows & Deletes
The 1322 Twitter WebSocket API monitors a custom list of X accounts and pushes tweets, replies, quotes, retweets, follow changes, profile changes, pins and deletions as structured events. Standard delivery typically operates in a 150-250ms range; selected accounts on the manually provisioned Ultimate lane typically operate around a 100ms average. REST handles the tracked list, WebSocket is included, no X developer account is required, X plans start at $250 per month for 100 accounts, and a full-product trial is available.
- Operating range
- 150-250ms typical; selected Ultimate accounts around 100ms
- Plans
- From $250/month
- Evaluation
- One-day trial, on request
- Updated
Start with X (Twitter)
The entry plan is $250/month for up to 100 tracked accounts. WebSocket delivery is included in every X / Twitter plan. The dashboard, REST management, Telegram and signed-webhook routing are available according to the purchased source and enabled delivery features.
Need to validate the payload and operating range first? The one-day evaluation, set up on request after the team reviews it, runs the actual product with a capped tracked list, no card and no purchase commitment.
A real-time Twitter monitor for account watchlists
Use 1322 when the job is to monitor a known list of X (Twitter) accounts and move each public event into a trading system, alert bot, Discord server, Telegram chat, or webhook workflow without operating your own X polling stack.
Best fit
- Trading desks and crypto teams watching KOLs, founders, politicians, exchanges, and project accounts
- Developers who need structured Twitter events over WebSocket instead of periodic timeline polling
- Operators who want one tracked-account list shared by the dashboard, REST API, and managed alert routes
Know before buying
- This is a live Twitter monitor, not a historical tweet archive or bulk search API
- Standard X plans include WebSocket delivery; the lower-latency Ultimate lane is manually provisioned
- Only accounts on your private tracked list consume capacity, and the list can be changed without reconnecting the stream
How to monitor specific Twitter accounts in real time
Whether you call it a Twitter account monitor, a tweet tracker or a live Twitter monitor, the job is the same: know the moment a specific account posts, and get the post into the place you act. There are four ways to do it, and they differ in how the post reaches you, not only in how fast.
| Approach | How fast | Cost shape | Where the post lands |
|---|---|---|---|
| Phone notifications from the X app | Whenever the app notifies you | Free | One person's phone; nothing a bot can read |
| Official X API Filtered Stream | Push; X documents approximately 4-5 s P99 | Pay-per-use per post read, with a monthly cap | Your own consumer code |
| Polling APIs or scrapers | Bounded by your poll interval | Per call, or your own infrastructure | Your own code, and your own fixes when it breaks |
| 1322 tracked-account feed | Push; 150-250ms typical, selected Ultimate accounts around 100ms | From $250/month for 100 accounts, WebSocket included | WebSocket, REST, a hosted live feed; Discord, Telegram and webhooks by configuration |
1322 figures are observed operating figures, not an SLA. Compare named providers or see the hosted live feed with keyword highlighting and sound alerts.
What 1322 monitors on X (Twitter)
- New tweets, delivered progressively (mini → update → expanded → full) so you get the earliest signal then the enriched version
- Replies, quote tweets, and retweets with the referenced/nested post
- Profile updates (name, bio, avatar, banner, verification)
- Follow / unfollow events
- Tweet deletions and pin / unpin changes
- Two delivery lanes: Normal and Ultimate (lower-latency)
How the event moves
Real-time delivery: X plans include a source-specific WebSocket stream and REST account management. Discord, Telegram, and signed-webhook routes depend on account configuration and enabled features. Base URL https://api.1322.io. The feed is filtered to the accounts on your tracked list; manage that list through REST, Discord, or the dashboard.
Example X WebSocket frame: tweet.mini.update (trimmed)
{
"type": "tweet.mini.update",
"tweet": {
"id": "1889012345678901234",
"type": "TWEET",
"created_at": 1790345001000,
"author": { "id": "44196397", "handle": "example" },
"body": { "text": "gm", "urls": [], "mentions": [] },
"media": { "images": [], "videos": [] }
}
}Cybertruck production ramping hard.
The hosted live feed renders the same event.
The Ultimate figure is a typical operating average for selected accounts, not an SLA. X Ultimate is provisioned manually and is intentionally not a self-serve checkout option.
Common questions
How fast are events?
Typically 150-250ms from when the tweet appears to when you receive it.
Can 1322 monitor specific Twitter accounts in real time?
Yes. Add the public X accounts you care about to a private watchlist, then receive their supported events through your WebSocket and configured alert routes.
WebSocket or REST?
Both. Use the WebSocket for push delivery and the REST API to manage tracked accounts and fetch state.
How do I choose which accounts to track?
Manage your tracked-account list via the REST API, the Discord bot, or the dashboard. The stream auto-updates to match.
Can I get historical tweets / backfill?
No. 1322 is a real-time stream, events are not queued while your client is disconnected. Reconnect with backoff and respond to pings to stay connected.
What's the difference between Normal and Ultimate?
Ultimate is a lower-latency lane. It is set up manually, contact sales; it is not a self-serve checkout option.
How many accounts can I track?
Up to your plan's account limit. See pricing.
How is it authenticated?
An API key via the X-API-Key header (or Bearer token) per request / WebSocket connection.
How are events delivered?
X plans include a source-specific WebSocket stream and REST account management. Discord, Telegram, and signed-webhook routes depend on account configuration and enabled features.
Is this an X Filtered Stream alternative?
It can be. X currently offers the official API v2 Filtered Stream under pay-per-use pricing. 1322 is a managed, flat-plan option for a selected account list, with its own WebSocket and REST management contract.
Does it work with the Twitter API v2?
1322 is independent of the official Twitter API, you don't need a Twitter developer account, elevated access, or per-request quotas. You authenticate with your 1322 API key.
Can I trial the X (Twitter) feed before subscribing?
Yes, on request. The standard one-day evaluation uses the real dashboard, live feed and production event payloads for a capped tracked list. Request it from the 1322 trial page, which takes you to the 1322 Discord; the team reviews each request before setting a trial up. It requires no card or purchase commitment.