- You do not need to get new data from the bot.
- The password stays the same.
- Earlier strings keep working with their own settings. One package can hold strings for different countries, and they share its traffic.
This works for Residential and Mobile. ISP and Datacenter have a fixed IP, so their username carries no settings.
How the string is built
The bot gives you the username and password in the proxy panel: Rotating → category → Get data. Your plain username is everything before the first
_. In the examples on this page, replace LOGIN and PASSWORD with your own.
HTTP and SOCKS5 work on the same port, and the gateway detects the protocol by itself.
Parameters
Each parameter is written as_key_value and appended to the username.
Skip the parameters you do not need. Write the rest in the same order the bot uses:
- in a city or postal code. Keep the whole username within 128 characters.
Strings the bot issued earlier may contain
_isp_ with a number. It is also a provider, just by an internal code. Those strings keep working, and the bot now builds new ones with _asn_.How the IP changes
Two parameters control IP changes:_s_ and _ttl_.
Session. You make up the
_s_ value yourself: any Latin letters and digits, for example _s_job1. The same value gives the same IP, and a new value gives a new IP. So you can change the IP at any moment by changing the _s_ value.
Time. _ttl_ takes a number and a unit: s for seconds, m for minutes, h for hours. For example, _ttl_30s, _ttl_10m, _ttl_1h. In the bot, rotation goes from 1 minute to 24 hours, which is _ttl_1m to _ttl_24h.
A session with no traffic for 60 minutes is closed. The next request with the same
_s_ gets a new IP._s_, every new connection gets a new IP. A connection to an HTTPS site that your software keeps open uses one IP until it closes.
New geo, new session
Geo step by step
Country
_c_ plus a two-letter country code: _c_US, _c_DE, _c_FR. The United Kingdom is GB, not UK. Without _c_, the IP can be from any country.
Region or state
_sd_ plus a numeric code: _sd_2928 is Texas. A name like _sd_Texas or an abbreviation like _sd_TX is rejected with 407.
US state codes are listed below. For other countries, pick the region in the bot (Geolocation → Region), tap Get data, and copy the number after _sd_.
US state codes
US state codes
The codes are the same for Residential and Mobile, but Mobile covers fewer states. If a state is not listed in the bot, a string with its code returns
503.City
_city_ plus the English name, with spaces replaced by -: _city_Dallas, _city_New-York, _city_Los-Angeles. Add the country as well, since the same city name exists in different countries.
The easiest way to get the exact spelling is the bot: pick the city in Geolocation, tap Get data, and look at the username.
Provider or carrier
_asn_ plus the provider’s autonomous system (AS) number. Digits only, without the AS letters: the gateway rejects _asn_AS7922.
The bot shows available providers under Geolocation → Provider. For Mobile, the button is called Operator. You can look up any other provider’s number by name in public ASN directories. If no IP is available for that number right now, the string returns
503.
ZIP
_zip_ plus a postal code. It works only together with a country: _c_US_zip_10001. Without _c_, the username fails authentication with 407.
Write letters in upper case and replace a space with -: _c_US_zip_75201, _c_DE_zip_10115, _c_CA_zip_M5V.
The gateway picks the nearest available IP, so the exit’s postal code can differ from the one you set. If there is no device nearby at all, the string returns 503.
Several filters at once
Every filter narrows the choice of IPs. Country, region, and city together usually work. A city combined with a ZIP or a provider often returns503, for example when the postal code belongs to another city. If a string returns 503, remove filters one at a time, starting with the narrowest.
Parallel threads
- Each port from 10000 to 10999 works as a separate channel. Simultaneous requests through different ports use different IPs, up to 1000 at once.
- When the username has
_s_, the session decides the IP, not the port. The same session on different ports gives one IP. To give each thread its own pinned IP, give each one its own session:_s_job1,_s_job2, and so on. - When the bot issues several strings, it does this for you: each string gets its own port and its own session.
- All strings draw traffic from the same package. Changing parameters costs nothing.
Ready-made examples
Here is the same string in different formats:
- URL
- host:port:user:pass
- user:pass:host:port
How to check
_s_ the IP changes, with _s_ it stays the same.
IP lookup services use different databases. One service may place the same IP in a neighboring city or region.
Errors
During the first 10 minutes after you buy a package, strings may return
503. That is normal while the package connects. With _s_, the first request may also occasionally get 503 if the device has just gone offline. Retry the request and turn on retries in your software.
Extra parameters
The bot does not set these, but the gateway understands them. Use them only if you know why you need them._rotm_ values:
0pick another device right away, this is the default;1wait about 5 seconds until inactive devices drop off the list, requests may get errors meanwhile;2never switch the device.
503.
How this maps to the bot
The bot builds the same username from the panel settings. You can set the proxy up in the bot, get the string, and then edit it by hand.
The password changes only after a reset in the bot: Reset settings → Password. After that, every issued string stops working, and you need to get new data.
Connection and formats
String formats, HTTP and SOCKS5.
If it does not work
Diagnostics by symptom.