Migrate to Xanguard

Leaving twitterapi.io?
Switch in one line.

Xanguard speaks twitterapi.io's API — same routes, same payloads. Point your base URL at us, swap your key, and you're done. You get sub-second delivery, the quote-tweets and retweets their monitor drops, and zero footprint on the accounts you track.

1 line
To switch
<1s
Delivery
QT + RT
Included
0
Footprint

Same API. Three things better.

The drop-in is the easy part — here's what you actually gain.

⚡ ~10× faster

Sub-second delivery. In our testing, twitterapi.io's poll-based monitor took about 10 seconds to surface a tweet — Xanguard delivers in under one.

✅ Full coverage

In our testing, twitterapi.io's monitor silently dropped quote-tweets and retweets — often the actual signal. Xanguard delivers every type: posts, replies, quotes, retweets.

🕸️ Invisible

Xanguard never follows the accounts you monitor or adds them to lists. The accounts you track are never notified that someone's watching.

Change the URL and the key. That's it.

Your routes, request bodies, and tweet parser stay exactly the same.

1Get your Xanguard key from @B2B_Xanguard_bot — it starts with dt_.

2Repoint your REST calls. Same paths, same bodies — only the host changes:

https://api.twitterapi.io/oapi/x_user_stream/add_user_to_monitor_tweet
https://api.xanguard.tech/oapi/x_user_stream/add_user_to_monitor_tweet
The X-API-Key header stays — just use your new dt_ key.

3Repoint the realtime WebSocket. Same header, same payload shape:

wss://ws.twitterapi.io/twitter/tweet/websocket
wss://api.xanguard.tech/twitter/tweet/websocket
Auth via the x-api-key header. Tweets arrive as {"event_type":"tweet","tweets":[…]} — your existing parser works unchanged.

Endpoint map

Actiontwitterapi.ioXanguard
Add a handlePOST /oapi/x_user_stream/add_user_to_monitor_tweetidentical path
Remove a handlePOST /oapi/x_user_stream/remove_user_to_monitor_tweetidentical path
List handlesGET /oapi/x_user_stream/get_user_to_monitor_tweetidentical path
Realtime tweetswss://ws.twitterapi.io/twitter/tweet/websocketwss://api.xanguard.tech/twitter/tweet/websocket
AuthX-API-Key headersame header, dt_ key

Request bodies and tweet event shapes match twitterapi.io's — no code changes beyond the host and the key.

twitterapi.io vs Xanguard

Latency and coverage figures are from our own testing of twitterapi.io's user-monitor stream.

 twitterapi.io monitorXanguard
Tweet delivery latency~10s (poll-based)sub-second
Quote-tweets & retweetsdroppeddelivered
Footprint on tracked accountsmay follow / list themnone — invisible
Migration effortchange base URL + key
Beyond tweetstweets only+ profile changes, new-follower, deleted-tweet

Switch in minutes

Grab a key, change two strings, ship. Pay in SOL.