Twitter WebSocket API: real-time X monitoring & alerts
The 1322 Twitter WebSocket API is a real-time monitoring service that streams new tweets, profile changes, and account activity for a custom list of X (formerly Twitter) handles, typically delivering events within 150-250ms of publication. It is a practical alternative to the retired Twitter Streaming API and to expensive enterprise firehose access: posts arrive as structured JSON events containing the tweet text, media, engagement metrics, author profile, and the full reply or quote chain, while a REST API handles tracked-account management. No Twitter developer account is required, and plans start from $250 per month.
What 1322 monitors
- •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 it works
Real-time delivery: WebSocket stream, REST API, Discord bot embeds, Telegram bot/cards, and signed customer webhooks. Base URL https://api.1322.io. Filtered to the accounts on your tracked list; manage that list via REST, Discord, or the dashboard.
Example tweet event (trimmed)
{
"platform": "x",
"eventType": "tweet.full",
"handle": "example",
"content": "gm",
"media": [{ "kind": "image", "url": "https://…" }],
"metrics": { "likes": 12, "retweets": 3, "replies": 1 },
"timestamp": "2026-06-07T12:00:00Z"
}Rendered in your feed
Cybertruck production ramping hard.
X-Ultimate (lower-latency lane) is provisioned manually, contact sales. It is intentionally not a self-serve checkout option.
FAQ
How fast are events?
Typically 150-250ms from when the tweet appears to when you receive it.
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?
WebSocket stream, REST API, Discord bot embeds, Telegram bot/cards, and signed customer webhooks.
Is this a Twitter Streaming API alternative?
Yes. The official Twitter Streaming API was retired and enterprise firehose access is expensive. 1322 gives you a filtered real-time WebSocket for the exact accounts you care about, plus REST management, at a flat plan price.
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. One API key, one WebSocket.