Twitter search operators you can use in the XFlux API
Advanced search operators still work for public tweet research. Use them in the XFlux /search endpoint (and MCP xflux_search_tweets). Free tier: 1,000 API calls/month. Full operator notes also in /docs/guides/search and /blog/twitter-api-search-operators.
Same operator grammar
from:handle, lang:en, quoted phrases, OR, -exclude — pass as q= on GET /api/v1/search.
Agent-friendly
Claude/Cursor can call search via @xflux/xflux-mcp-server — see /mcp.
When operators are not enough
For always-on @account watches, use monitors instead of polling search — /monitor-twitter-account.
Try operators in three steps
- 1
Get a free API key
Register → Dashboard → API Keys. No credit card on Free.
- 2
Call search with operators
Example: q=from:elonmusk lang:en or q="fed rate" lang:en
- 3
Automate or monitor
Scripts/MCP for on-demand research; monitors for push alerts.
curl example
Replace the key. Operators go in the q parameter.
curl -G "https://www.xfluxapi.com/api/v1/search" \
--data-urlencode 'q=from:elonmusk lang:en' \
-H "Authorization: Bearer xflux_YOUR_KEY"FAQ
- Is this official X advanced search?
- Operators match common public search grammar. XFlux is an independent read API — not the official X developer portal.
- Where is the long operator list?
- Docs: /docs/guides/search. Blog: /blog/twitter-api-search-operators.
- Search vs monitors?
- Search is on-demand. Monitors watch specific accounts continuously.
Related guides
Try account monitors free
Free includes 1 monitor and Dashboard hit history. Live webhook delivery starts on Starter ($19/mo).