Per-call proxy routing
The Twitter (X) API with proxy support
Add an optional proxy field to any call and that request exits through your http/https proxy — per account, per region, per call. No account-level config. No other X API ships this. Same flat $0.001 per call.
curl -X POST "https://api.omnixapi.com/api/v1/twitter/user/info" \
-H "Authorization: Bearer YOUR_OMNIX_KEY" \
-H "Content-Type: application/json" \
-d '{
"auth_token": "YOUR_X_AUTH_TOKEN",
"username": "elonmusk",
"proxy": "http://user:pass@proxy-host:8080"
}'Omit proxy and the call runs normally through OmniX. Include it and only that request routes through your proxy — http/https with optional auth, on every one of the 58 endpoints.
What per-call proxies unlock
Multi-account management
Keep one sticky residential IP per X account. Every call carries that account's proxy, so login sessions never jump countries mid-day.
Geo-specific results
Trends, search and timelines can differ by region. Route a call through a proxy in the target country and read what users there actually see.
Compliance & data residency
Need traffic to exit from a specific jurisdiction? Point the call at your compliant egress, per request, without re-architecting anything.
Your existing proxy fleet
Already pay for residential or mobile proxies? Plug them straight into API calls instead of maintaining your own scraping stack around them.
Why other X APIs don't offer this
Most Twitter data APIs pool your requests through their own scraping infrastructure — you never control the egress IP, and every customer shares the same address space. That's fine for bulk reads, but useless when your product needs a stable IP-per-account, a specific country, or a compliant exit point. OmniX was built the other way around: each call runs as your X account (via its auth_token) and, when you want, through your proxy. You keep control of both identity and network path — per request.
FAQ
How do I use a proxy with the Twitter (X) API?
The official X API has no proxy option — your requests always originate from your server's IP. With OmniX you add an optional proxy field to any API call, and that single request is routed through your http or https proxy. No account-level setup, no separate plans.
Which proxy types does OmniX support?
HTTP and HTTPS proxies, with or without username:password auth (e.g. http://user:pass@host:port). SOCKS proxies are not supported. Residential, datacenter and mobile proxies all work as long as they speak http/https.
Can I use a different proxy for each X account?
Yes — that is the main use case. Because the proxy is set per call, you can keep a sticky residential IP per managed account: every call for account A goes through proxy A, account B through proxy B. Consistent IP-per-account is a common account-hygiene practice for multi-account tools.
Does proxy routing cost extra?
No. Every OmniX endpoint is a flat $0.001 per call, with or without a proxy. You bring your own proxy provider; OmniX just routes the request through it.
Do other Twitter APIs (twitterapi.io, GetXAPI, twexapi) offer proxy support?
As of July 2026, none of them advertise per-request proxy routing — requests exit from their infrastructure's IPs. OmniX is the only X API where the caller controls the egress IP on a per-call basis.
Route your first call in 5 minutes
Free credits to start, flat $0.001 per call — proxy or no proxy.