Proxy integration guides

netdash is a standard HTTP proxy, so any client that accepts a proxy URL works with it. Each guide shows the exact configuration for one tool, plus sticky sessions, country targeting and the errors you will meet.

Create account Read the quickstart

Proxy URL, exit IP in United States

http://USERNAME-cc-US:PASSWORD@scale-us.netdash.io:2000

scale-us.netdash.io:2000: Host and port pick the plan and the gateway.
USERNAME: Your account username from the dashboard. One pair works on every residential and mobile plan.
-cc-US: The exit country, as a two-letter ISO code. Use GB for the United Kingdom.
-session-a1b2c3d4-ttl-30: Optional. Leave it out and the gateway rotates exit IPs for you.

curl --max-time 30 -x "http://USERNAME-cc-US-session-a1b2c3d4-ttl-10080:PASSWORD@mobile-us.netdash.io:4000" \
  "https://api.ipify.org?format=json"

Example output

{"ip":"203.0.113.10"}

Your output shows a different address in the country you chose.

import requests

proxy = "http://USERNAME-cc-US-session-a1b2c3d4-ttl-10080:PASSWORD@mobile-us.netdash.io:4000"
proxies = {"http": proxy, "https": proxy}  # set both, or HTTPS requests bypass the proxy

response = requests.get("https://api.ipify.org?format=json", proxies=proxies, timeout=30)
response.raise_for_status()
print(response.text)

Example output

{"ip":"203.0.113.10"}

Your output shows a different address in the country you chose.

import { ProxyAgent, fetch } from "undici";

const dispatcher = new ProxyAgent({
  uri: "http://mobile-us.netdash.io:4000",
  token: "Basic " + Buffer.from("USERNAME-cc-US-session-a1b2c3d4-ttl-10080:PASSWORD").toString("base64"),
});

const res = await fetch("https://api.ipify.org?format=json", { dispatcher, signal: AbortSignal.timeout(30_000) });
console.log(await res.text());

Example output

{"ip":"203.0.113.10"}

Your output shows a different address in the country you chose.

curl --max-time 30 -x "http://USERNAME-cc-US:PASSWORD@scale-us.netdash.io:2000" \
  "https://api.ipify.org?format=json"

Example output

{"ip":"203.0.113.10"}

Your output shows a different address in the country you chose.

import requests

proxy = "http://USERNAME-cc-US:PASSWORD@scale-us.netdash.io:2000"
proxies = {"http": proxy, "https": proxy}  # set both, or HTTPS requests bypass the proxy

response = requests.get("https://api.ipify.org?format=json", proxies=proxies, timeout=30)
response.raise_for_status()
print(response.text)

Example output

{"ip":"203.0.113.10"}

Your output shows a different address in the country you chose.

import { ProxyAgent, fetch } from "undici";

const dispatcher = new ProxyAgent({
  uri: "http://scale-us.netdash.io:2000",
  token: "Basic " + Buffer.from("USERNAME-cc-US:PASSWORD").toString("base64"),
});

const res = await fetch("https://api.ipify.org?format=json", { dispatcher, signal: AbortSignal.timeout(30_000) });
console.log(await res.text());

Example output

{"ip":"203.0.113.10"}

Your output shows a different address in the country you chose.

Languages and HTTP clients

Configuration references for the clients that fetch pages in your code. For an end-to-end Python pipeline that fetches, parses and stores, follow the Python web scraping tutorial.

Python
requests, httpx and aiohttp: both proxy keys, sticky sessions, exit countries and common errors.
Node.js
undici ProxyAgent with fetch, or axios with https-proxy-agent, and why built-in fetch ignores HTTPS_PROXY.
Go
A net/http Transport with an authenticated proxy URL, one client per sticky session, timeouts and retries.
Scrapy
Per-request proxy meta or a small downloader middleware, with polite crawl settings.

Browser automation

Browsers take the proxy server and the credentials separately. These guides show where each tool expects them; the workflows themselves are on browser automation.

Playwright
Proxy credentials per browser or per context, for Node.js and Python.
Puppeteer
--proxy-server plus page.authenticate, and per-context proxies.
Selenium
Why credentials stay out of --proxy-server, and a small local forwarder that adds them, tested with Chrome.
Cloud browsers
Browsers on VMs, in containers or with a hosted service, and where the proxy fits.

AI and coding agents

For the architecture and product choice, see proxies for AI agents.

Claude Code
Credentials in .env, a proxy per client instead of HTTPS_PROXY, and Playwright MCP with an authenticated proxy.
Agent frameworks
Browser Use, the OpenAI Agents SDK, LangChain and Playwright MCP: proxy the browser and tools, not the model API calls.

What every proxy integration guide assumes

The guides share one set of facts, names and defaults, so code from one page fits the next.

One credential pair
One username and password work on every residential and mobile plan, and each plan keeps its own GB balance. The guides read them from NETDASH_USERNAME and NETDASH_PASSWORD.
One username syntax
USERNAME-cc-US for a rotating session, USERNAME-cc-US-session-a1b2c3d4-ttl-30 for a sticky one. Country codes are ISO alpha-2: use GB, not UK.
Plan chosen by host and port
Examples use the Scale plan on the Americas gateway, scale-us.netdash.io:2000. Other plans and the -eu gateway change only the host and port; the proxy format reference lists them all.
HTTP proxy, HTTPS via CONNECT
The proxy URL starts with http://, also for HTTPS websites, which go through a CONNECT tunnel. There is no SDK to install and no public account API.

How the code is checked

Every code sample carries a label. Checked against a local test proxy means the code ran against a local stand-in for a netdash gateway that requires a username and password, and the stand-in received the expected username and password, including on the CONNECT request that opens the tunnel to an https:// website. The short snippets for cURL, Python, Node.js and Go are generated from the same username syntax the dashboard uses.

Syntax-checked means the code was parsed but not run against the test proxy: browser automation, Scrapy projects and framework configuration. Where a guide describes how another tool behaves, it links that tool's official documentation in a Sources list with the date we read it.

Credentials from environment variables, never in the code
A timeout on every request
TLS certificate checks left on
Polite defaults: bounded concurrency, stop on 403

Docs for AI agents

llms.txt starts with the connection facts and links every doc and guide; llms-full.txt contains them in one file. Add .md to any guide or docs page URL, for example /developers/python.md, to get the page as Markdown with its code.

To let a coding agent set up netdash in your project, copy the setup prompt from the quickstart or the Claude Code guide. It points the agent at the proxy format reference and tells it to keep credentials in environment variables.

Reference docs

The guides link here for the details. Everything else is in the netdash documentation.

Quickstart
From new account to first proxied request.
Proxy format
Hosts and ports for every plan, the username syntax and the export formats.
Sessions
Rotating vs sticky, session IDs and TTL presets.
Country targeting
Pick the exit country with an ISO code, and the matching gateway.
Troubleshooting
407 errors, timeouts and requests that skip the proxy.

Pick a guide and send your first request

Create an account, buy a residential or mobile plan from 1 GB and copy your username and password from the dashboard. Every guide starts from there.

Create account Read the quickstart

Privacy choices

We use cookies and similar technologies that this site needs to work and to remember your choice. We also use Google Analytics to understand which pages and features people use: in the EEA, the UK and Switzerland only with your consent. Live chat loads only if you open it. You can change your choice at any time under “Privacy choices” in the footer. Privacy Policy