Run your first request in 5 minutes.

Everything you configure rides the username: hyphen-separated tokens, always in the order country → city or ISP → OS → session → lifetime. The password never changes. Both ports speak HTTP, and https:// targets tunnel straight through — point any HTTP-proxy setting at them.

Every credential works on all three hosts. The door only decides where your traffic enters the network — pick the one closest to your machines and shave the round trip. It never limits which countries you can exit from.

• eu-residential2.basilproxies.comEurope
• us-residential2.basilproxies.comAmericas
• ap-residential2.basilproxies.comAsia-Pacific

The dashboard generator picks a default from your account country; the globe in its footer overrides it. A scraper in Frankfurt exiting from US IPs still wants the eu- door.

Your proxy user and password live on the pool's page in the dashboard, right above the generator — every token in this guide rides on top of that username. Access is rolling out account by account; if the page isn't enabled on yours yet, write to us. One thing to know: brand-new credentials can answer 407 for the first minute or two while they propagate. That's not a wrong password — wait briefly and retry.

Open the dashboard→

You choose the session model with the port, not a flag. Sticky sessions then take two extra username tokens to name the session and cap its life.

Four dials, all on the username. Country is the anchor — city and ISP refine it and are mutually exclusive; OS works with anything. Skip every token and you get the worldwide pool.

Order matters, and it's fixed: country → city or ISP → OS → session → lifetime. The dashboard generator always emits tokens in that order — when a hand-built string misbehaves, diff it against a generated one.

The same request in three stacks. Swap USER:PASS for your pair and run it — the -country-us token means every response should report a US exit.

# New IP on every request — targeting rides the username
curl -x "http://USER-country-us:[email protected]:4242" \
  https://ipinfo.io/json

The dashboard keeps a live statistics page for this pool: bandwidth and request charts over 24 hours to 30 days, success rate and latency headlines, and a per-domain table of your top targets. When a job misbehaves, look there before you look at your code — a sinking success rate on one domain tells you more than a stack trace.

Open statistics→

Every account has a read-only API for its own balance, usage, orders and proxy lines — for a script that tops you up before you run dry, or a dashboard of your own. Create a key under Tools → API in the dashboard and send it as a Bearer header.

Create an API key→

Base URL

• GET /me

  Your account id, email, sign-up date and pricing group.

• GET /balance

  Residential MB left (both pools, merged the way the dashboard shows it), mobile MB, and every ISP subscription with its region, IP count, status and renewal date.

• GET /usage?from=&to=&granularity=day|hour

  MB used per day or per hour. ISO dates; defaults to the last 30 days, 90 at most.

• GET /orders?limit=&cursor=

  Your purchases, newest first — amount in minor units in the order's own currency, plus amountEur. Up to 100 per page (default 25); pass nextCursor back for the next one.

• GET /subscriptions

  Every subscription, including ones that are past due.

• GET /proxies?product=residential|isp&country=&session=rotating|sticky&count=&format=

  Ready-to-use proxy lines built from the credentials you already hold — nothing is created and the call spends no data. count up to 1000 (default 10); format host:port:user:pass (default), user:pass@host:port or url.

• GET /res2/subaccounts

  Your main account and each sub-account, with its own balance and credentials.

# Keep the key in an env var, not in the script
curl "https://api.basilproxies.com/api/v1/balance" \
  -H "Authorization: Bearer $BASIL_API_KEY"

GET /balance answers like this:

{
  "residential": {
    "remainingMb": 42350,
    "pool": "res2",
    "classicMb": 0,
    "res2Mb": 42350
  },
  "mobile": {
    "remainingMb": 0
  },
  "isp": [
    {
      "id": "8c1e2f60-4b7a-4d19-9e3a-51f0c2d7a8b4",
      "region": "australia",
      "ipCount": 25,
      "status": "ACTIVE",
      "periodEnd": "2026-10-12T08:31:00.000Z",
      "cancelAtPeriodEnd": false
    }
  ]
}

• 407 Proxy Authentication Required

  Freshly issued credentials need a minute or two to propagate — wait and retry before touching anything. Still 407 after that? Copy the pair from the dashboard again, and remember targeting tokens belong on the username, never the password.

• Everything times out

  Check the port: 4242 rotating, 4243 sticky — nothing else answers. Endpoints saved before August 2026 use retired hosts and ports; regenerate them in the dashboard.

• The exit country isn't what I asked for

  Token order and case are strict: lowercase codes, country before everything else. Generate one string in the dashboard and diff it against yours.

• City or ISP targeting errors out

  City and ISP can't ride one username together — pick one. Both need a country token in front, and the code must match the dashboard picker exactly.

• Connects, but the target blocks you

  That exit is burned for that target. Rotate the session id, narrow the targeting to a cleaner region, or check the statistics page to see if the block is domain-wide.