Xanguard API quick start: keys, base URLs and first call
Build on Xanguard's Twitter/X monitoring. Paid plans get ~200 ms median detection, measured and published live. Deliver them to your app, bot, or trading system through the channel that fits your stack.
Xanguard APIs
All Xanguard APIs share one host — https://api.xanguard.tech — speak JSON, and wrap every response from a valid endpoint in the same envelope: {"ok":true,"data":…} on success, {"ok":false,"error":"…"} on failure. Each product lives under its own base path and issues keys with its own prefix:
| API | Base path | Key prefix | Issued by | Purpose |
|---|---|---|---|---|
| Tweet Alerts (consumer) | /v1 |
xg_ |
xanguard.tech/api-keys (paid Tweet Alerts plan); a dt_ key also works |
Track accounts, settings, webhooks, WS alerts |
| B2B Monitoring | /v1/dt |
dt_ |
@B2B_Xanguard_bot (payment confirmation; /apikey reissues) |
Handles, profile/follow data, realtime WS |
| CA Search | /v1/search |
dt_ |
B2B add-on (Extra Features menu) | Tweet search by CA/ticker/keyword |
| Community Watch | /v1/cw |
cw_ |
@F_xanguard_bot | Community events |
| Convergence Tracker | /v1/ct |
ct_ |
@T_xanguard_bot | Community convergence |
| ECA | /v1/eca |
eca_ |
@ECA_Xanguard_bot /apikey |
pump.fun launch watchlist |
| Engagement Tracker | /v1/et |
et_ |
@E_Xanguard_bot | Per-tweet engagement |
| Trending Alerts | /v1/trending |
trend_ |
@Trends_Xanguard_bot | Trending feed |
| PumpFun Livestream | /v1/pf |
pf_ |
@PF_Xanguard_bot | Livestream start/stop |
| Search Alerts | /v1/sa |
sa_ |
@Xanguard_bot | Keyword search alerts |
WebSocket auth
Consumer and product WebSockets authenticate with an ?api_key= query parameter (e.g. wss://api.xanguard.tech/v1/ws?api_key=xg_your_key). The B2B realtime WebSocket is the exception: it authenticates with a LOGIN opcode after connecting — see B2B Realtime WebSocket.
Keys are product-scoped. A dt_ key won't work on /v1/cw, a cw_ key won't work on /v1/et, and so on. One exception: a B2B dt_ key also works on the Tweet Alerts endpoints (/v1/accounts…, /v1/ws). Generate a key from the bot that owns the product you want to use.
Looking for bot setup and user guides instead? See the Telegram guides.
Quick Start
Consumer: Tweet Alerts
Track Twitter/X accounts and receive tweet alerts in your app — four steps:
- Open @Xanguard_bot, send
/start, and choose a paid Tweet Alerts plan. - Create your
xg_key at xanguard.tech/api-keys (Telegram login; a new key revokes the old one). Base URL ishttps://api.xanguard.tech/v1. Building something bigger? New API users are pointed to @B2B_Xanguard_bot, whosedt_key also works here. - Add a handle:
POST /v1/accountswith body{"handles":["elonmusk"]}. - Receive alerts on the WebSocket (
?api_key=auth) or via a signed webhook.
B2B: Handle Monitoring
Xanguard is an API-first, real-time Twitter/X firehose. Get from zero to a live event stream in four steps.
Step one is a key. Open @B2B_Xanguard_bot, pick a plan (from $49/mo for 50 handles) and your key arrives in the payment confirmation. Paid in SOL with automatic activation; payments are final and non-refundable.
Onboard
Open @B2B_Xanguard_bot on Telegram, send /start, and choose a plan (priced by handle count — see B2B Pricing).
Get your API key
Your dt_ key is in the payment confirmation message (shown once; save it). Lost it? /apikey issues a new key and the old one stops working immediately. Base URL is https://api.xanguard.tech/v1/dt. Authenticate every REST call with a Bearer header:
Authorization: Bearer dt_your_api_key_hereAdd a handle
Register an account to monitor. Every response uses the envelope {"ok":true,"data":…} (or {"ok":false,"error":"…"} on failure).
curl -X POST https://api.xanguard.tech/v1/dt/targets \
-H "Authorization: Bearer dt_your_api_key_here" \
-H "Content-Type: application/json" \
-d '{"handle":"elonmusk"}'
# → 201 {"ok":true,"data":{"handle":"elonmusk","twitter_user_id":"44196397"}}Stream events
Connect the WebSocket, send the LOGIN opcode with your dt_ key, and receive real-time events for every monitored handle. See B2B Realtime WebSocket for the full protocol.
wss://api.xanguard.tech/v1/dt/realtime/wsPrefer chat delivery, or looking for the consumer Tweet-Alerts bot? See the Telegram bot guide.