XFlux Documentation
XFlux gives you programmatic access to public X (Twitter) data through a REST API, plus optional account monitors that watch @handles and surface new tweets — with signed webhooks on paid plans.
Try before you sign up
The homepage has a live API playground — run profile, search, and timeline demos with no API key.
Example API call
After signup you get a Bearer token. One request returns normalized JSON — no HTML parsing, no unofficial scraping code on your side.
Request
curl -H "Authorization: Bearer xflux_YOUR_KEY" \
https://www.xfluxapi.com/api/v1/users/elonmuskResponse (truncated)
{
"id": "44196397",
"username": "elonmusk",
"name": "Elon Musk",
"description": "...",
"followers_count": 220000000,
"verified": true
}What you can build
User profiles
Look up any public @handle — bio, followers, verification.
GET /api/v1/users/:usernameSearch
Keyword, hashtag, or from:username queries.
GET /api/v1/search?q=Timelines
Latest tweets from a public account.
GET /api/v1/users/:username/tweetsMonitors
Background polling — detect new posts automatically.
Dashboard → MonitorsWebhooks
Signed HTTP POST when a monitor finds a new tweet (Starter+).
POST your-endpointAlerts without cron
Skip building scrapers, proxies, and polling jobs yourself.
Free: 1 monitorXFlux API
REST endpoints for users, tweets, and search. Bearer key auth, monthly quota by plan.
XFlux Monitor
Poll @accounts on a schedule, detect new tweets, optional keyword filter + webhooks.
Why XFlux?
- Official X API Basic is $100+/mo with approval — XFlux starts free (1,000 calls/mo)
- Built-in KOL monitoring — no cron jobs or polling code required
- Dashboard for API keys, usage, monitors, and billing
- Webhook delivery with HMAC signatures (Starter plan and above)
How it works
Two products, one platform
Call /api/v1/* with your API key for on-demand data. Monitors watch accounts on a schedule and surface new tweets in your Dashboard. On paid plans, you can also receive signed webhook POSTs when a monitor detects a new tweet.