Introduction
What wproxy is, what it is not, and how the documentation is organised.
wproxy is a proxy network. You send us HTTP, HTTPS or SOCKS5 traffic; we forward it from an address in the country, city or carrier you asked for. There is one gateway host per product, and everything else — geography, session behaviour, rotation — is expressed as flags in the username you authenticate with.
That design decision shapes the whole API. You never have to provision an endpoint, wait for an allocation, or hold a list of IPs in your application. You change a string and the next request leaves from somewhere else.
The five products
| Product | Gateway | Billing | Best for |
|---|---|---|---|
| Residential | res.wproxy.io | per GB | Anti-bot-protected targets, ad verification, retail |
| Datacenter | dc.wproxy.io | per GB or per IP | Bulk fetching where the target does not profile networks |
| Mobile | mob.wproxy.io | per GB | App APIs, social platforms, carrier-gated content |
| ISP | isp.wproxy.io | per IP / month | Long sessions on residential-looking addresses |
| Dedicated | ded.wproxy.io | per IP / month | Fixed addresses you can whitelist with a partner |
How to read these docs
Quick start
Working credentials and a successful request in about three minutes.
Authentication
Username and password, IP whitelisting, and how sub-users fit in.
Targeting
Country, state, city and ASN flags, with the exact syntax for each.
Error codes
Every status the gateway can return and what to do about it.
Conventions
Throughout the docs, wp-acc4821 stands in for your account username and s3cr3t-pass for your password. Both appear in the dashboard under Proxy users. Placeholders are always written in that shape so they are easy to find and replace.