Skip to main content
Your customers connect with the credentials you issued them. They don’t need an API key, and they don’t call the Reseller API at all. Proxy strings are built client-side — there’s no endpoint that returns a formatted proxy line for a sub-user. You format the credentials against the gateway yourself.

​
Residential sub-users

HTTP, with sticky sessions.

​
Username format

Targeting is encoded in the proxy username:
The sub-user’s password is sent unmodified — only the username gets the targeting prefix.
Contact support for the full list of supported country names, and for rotating (non-sticky) sessions or custom session durations — those aren’t part of the confirmed format above.

​
Sessions

The same session id keeps the same exit IP. To get a new IP, use a new session id. Generate one session id per concurrent connection you want.

​
Full proxy line

In host:port:username:password form:

​
Testing a connection

You should see a residential IP in the requested country.

​
Metering

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

​
Static proxies

Datacenter and ISP allocations need no formatting. Each IP comes back from the API with everything your customer needs:
There’s no targeting prefix — the region is fixed when the IP is allocated — and no data limit, so nothing meters down. The IPs work until you release the allocation.