Skip to content

netdash documentation

netdash is a standard HTTP proxy with one credential pair and one username syntax. Start with the quickstart, then use the reference pages.

Updated
Reading time
4 min

The netdash documentation covers everything between buying a plan and a working integration: which gateway each plan uses, how the username sets the exit country and the session, what to do when a request fails, and how billing works. Your username and password are the same on every residential and mobile plan, and each plan keeps its own GB balance.

Every request goes to a regional gateway with a username built like this one:

Proxy username

USERNAME-cc-US-session-a1b2c3d4-ttl-30

USERNAMEYour username
From the dashboard
-cc-USExit country
ISO code, GB for the UK
-session-a1b2c3d4Session ID
Sticky only; letters and digits
-ttl-30Lifetime
Minutes to keep the exit IP
Leave out -session-…-ttl-… for rotating sessions. The password is the proxy password from the dashboard, not your sign-in password.

That is the whole interface. There is no SDK to install: any client that supports an HTTP proxy works. HTTPS websites go through a CONNECT tunnel, so the proxy URL starts with http:// for every website:

A first request
curl --max-time 30 -x "http://USERNAME-cc-US:PASSWORD@scale-us.netdash.io:2000" \
  "https://api.ipify.org?format=json"
Checked against a local test proxy

Start here

  1. 01

    Create an account

    Sign up with an email address and password and enter the one-time code we email you, or sign in with Google or Discord.

    Create account →
  2. 02

    Buy a plan

    Choose a residential plan or Mobile and buy GB for it, from 1 GB per order. You pay once, by card.

    See pricing →
  3. 03

    Copy your credentials

    In the dashboard, open Residential (or Mobile) and use Generate. It shows your username, password and the gateway for your plan.

    Proxy format reference →
  4. 04

    Send a first request

    Run one request through the gateway with curl, Python or Node.js and check the exit IP it prints.

    Read the quickstart →

Reference

  • Quickstart

    From a new account to a first proxied request with curl, Python or Node.js.

  • Proxy format reference

    Gateway hosts and ports per plan, the username syntax and the three output formats.

  • Sessions

    Rotating and sticky sessions, session IDs, and lifetime presets from 15 minutes to 7 days.

  • Country targeting

    Pick the exit country with an ISO code, use GB for the UK and choose the gateway.

  • Troubleshooting

    407 errors, HTTPS requests that skip the proxy, timeouts and the wrong exit country.

  • Billing

    One GB balance per plan, graduated pricing per order and ISP and datacenter renewals.

Integration guides

The proxy integration guides show the exact setup for each HTTP client, browser automation tool and coding agent, with code you can copy. Five of them:

  • Python

    requests and httpx, with both proxy keys set and timeouts on.

  • Node.js

    undici ProxyAgent with fetch, and axios with https-proxy-agent.

  • Playwright

    Proxies per browser or per context, with sticky sessions for multi-step flows.

  • Scrapy

    Proxies through request meta or a small downloader middleware.

  • Claude Code

    Credentials in .env and a proxy on each client, not on the coding agent.

What netdash doesn't do

netdash forwards your traffic and leaves the rest to your code. These limits apply to every plan:

  • No CAPTCHA solving, JavaScript rendering, retries or unblocking

    netdash forwards your traffic unchanged, so a challenge reaches your client exactly as the website sent it.

  • Targeting below country level

    You choose the exit country; you can't select a city, region, ZIP code, ASN or carrier.

  • Authentication by IP address

    Every request uses your username and password.

  • A public account API or SDK

    None is needed: it's a standard HTTP proxy, and usage lives in the dashboard.

  • Published uptime figures or an SLA

    We don't publish uptime figures or offer an SLA.

netdash documentation for AI agents

If a coding agent or an AI assistant sets up netdash for you, give it the plain-text versions of these pages instead of the rendered HTML:

  • llms.txt lists every docs page and integration guide with a one-line description, plus the connection facts.
  • llms-full.txt contains the full text of the docs and guides in one file.
  • Add .md to the URL of any docs page or guide for a Markdown copy, for example /docs/proxy-format.md. The Markdown copy of this page is /docs/index.md.

The quickstart also has a setup prompt for coding agents that you can paste into your agent. It asks the agent to read credentials from environment variables and to configure the proxy on the HTTP client or browser, not on the whole process.

Get help

  • Troubleshooting

    The common errors, their causes and the fix for each.

  • FAQ

    Short answers about plans, billing, sessions and setup.

  • Contact

    Email sales or support, live chat on this site, or Discord.

  • Service status

    What to check first when requests fail. We don't currently publish a live status page.

You can also email support directly or ask in the netdash Discord.

Spotted something out of date? Tell us.

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

Privacy choices

Choose what netdash.io may use. You can change this at any time under “Privacy choices” in the footer.

Necessary (always on)

Keeps the site working and secure, and remembers your privacy choices (nd_consent, 12 months).

In the EEA, the UK and Switzerland it stays off until you switch it on; elsewhere it is on unless you switch it off here. Google Analytics 4 measures page views, clicks on links and buttons, use of the price calculator, connection builder and code examples, scroll depth, file downloads, and page-performance metrics. It sets the cookies _ga and _ga_96MPNM6GHH, which last up to 12 months. Google processes this data, which may involve transfer to the United States. We do not send your name, email address or account details to Google Analytics. With this switched on we also remember a referral code or campaign you arrived with (nd_attr, 30 days), so a partner can be credited if you sign up.

Support chat (loads only when you open it)

Our live chat is provided by LiveChat. It loads only when you open the chat window. LiveChat then sets its own cookies and processes the messages you send and technical data about your browser.