Engagement Tracker API: per-tweet engagement updates
Programmatic access to Engagement Tracker — per-tweet engagement monitoring. Subscribe and get your et_ key in @E_Xanguard_bot. Plans: $100/mo for 25 tweets, $200/mo for 50, paid in SOL (payments are final and non-refundable); every price is on xanguard.tech/pricing.
Auth: Bearer token with et_ prefix.
Authorization: Bearer et_your_api_key_here| Method | Path | Description |
|---|---|---|
| GET | /v1/et/targets | List watched tweets |
| POST | /v1/et/targets | Add tweets. Body: {"tweet_ids": ["123", "456"]} |
| DELETE | /v1/et/targets/{tweet_id} | Remove watched tweet |
| GET | /v1/et/engagement/{tweet_id} | Current engagement counts |
| GET | /v1/et/webhook | Get webhook URL |
| PUT | /v1/et/webhook | Set webhook URL. ET deliveries are not HMAC-signed; they carry your secret in an X-Webhook-Secret header. Body: {"type": "engagement_update", "tweet_id", "old": {...}, "new": {...}}; single attempt, no retries |
| GET | /v1/et/status | Subscription status |
Engagement Response
{
"ok": true,
"data": {
"tweet_id": "1234567890",
"favorite_count": 42,
"retweet_count": 10,
"reply_count": 5,
"quote_count": 2,
"bookmark_count": 8,
"last_updated": "2026-03-22T11:30:00Z"
}
}WebSocket
wss://api.xanguard.tech/v1/et/ws?api_key=et_your_keyReceives one JSON frame each time the counts change on a watched tweet. Your watched tweets are read when you connect, so reconnect after adding tweets.
{
"type": "engagement_update",
"data": {
"tweet_id": "1234567890",
"old": {"favorite_count": 42, "retweet_count": 10, "reply_count": 5, "quote_count": 2, "bookmark_count": 8},
"new": {"favorite_count": 57, "retweet_count": 12, "reply_count": 6, "quote_count": 2, "bookmark_count": 9}
}
}