Skip to main content
Your customers connect with the credentials you give them. They don’t need an API key and never call the Reseller API. You build the proxy strings yourself. No endpoint returns a ready-made proxy line for a sub-user.

Residential Sub-Users

Host
HTTP, with sticky sessions.

Username Format

Targeting goes in the proxy username:
Username
The sub-user’s password is sent as is. Only the username gets the targeting added.
You can get the full list of supported countries, states and cities from GET /reseller/targeting. For rotating sessions or custom session lengths, contact support. Those are not part of the format above.

Sessions

The same session ID keeps the same IP. Use a new session ID to get a new IP. Use one session ID for each connection you want to run at the same time.

Full Proxy Line

As host:port:username:password:
Proxy format

Testing a Connection

Python
You should see a residential IP in the country you asked for.

Usage

Traffic counts toward the sub-user’s data limit and shows up on the usage endpoints within moments. When rawUsed reaches rawTotal, the account stops working until you top it up.

Static Proxies

Datacenter and ISP allocations need no formatting. The API returns each IP with everything your customer needs:
Response
Proxy format
There is no targeting, because the region is set when the IP is allocated, and no data limit. The IPs work until you release the allocation.
Last modified on October 15, 2026