Ticket drops

Exit where the on-sale is.

Regional on-sales care where a buyer connects from. One token picks the exit country, a second narrows it to a city, and the session token holds that IP from the queue to the confirmation page.

country + city targetingsticky up to 24 hourssub-accounts for a team (up to 5)three gateways, one poolusage per domain on the statistics page

The string for an on-sale.

Sticky, New York exit, held for an hour — queue to checkout on one IP. Swap the city for the venue's; the code is exactly what the dashboard's city picker writes.

us-residential2.basilproxies.com:4243:basil_demo-country-us-city-newyork-session-k4mz61pq-lifetime-60:vq20hxw8

Example with placeholder credentials — yours generate in the dashboard. Port 4242 rotates, 4243 holds one IP; targeting rides the username.

Strings

City, then session. In that order.

Country first, city second, session and lifetime last — the order is fixed and the dashboard always emits it. A checker that only needs a fresh look every request drops the session tokens and moves to port 4242.

Read the docs
on-sale.txt
# New York exit, one IP from queue to checkout (port 4243)
us-residential2.basilproxies.com:4243:USER-country-us-city-newyork-session-x9d02mvq-lifetime-60:PASS

# London on-sale through the EU gateway
eu-residential2.basilproxies.com:4243:USER-country-gb-city-london-session-k4mz61pq-lifetime-60:PASS

# Queue checker: a new IP on every request (port 4242)
eu-residential2.basilproxies.com:4242:USER-country-gb:PASS

Which product

One balance, the whole team.

Residential is the product: per-request rotation for the checkers, a sticky IP for each seat in the queue, a city token when the release is regional. Running it with a team? Split one balance across up to five sub-accounts, each with its own credentials — move data both ways, let a sub-account refill itself below 1 GB, and reset one password without touching the others.

See residential

Before you ask.

Be in the queue from the right place.

Get started