Documentation · 14 guides · updated Sep 25, 2026

Everything you need to route your first request.

Two hostnames, six username parameters, standard HTTP and SOCKS5. These pages describe the exact behaviour of the gateway, written for the person who will paste the endpoint into a config file.

Try

Quickstart API reference

2protocolsHTTP(S) on 9000, SOCKS5 on 9001, on every network
6parametersCountry, US state, city, ASN, session id and lifetime
24 hmax stickyHold one exit with -sid-, from one minute to a day
57snippetsCopy-ready code across 14 guides and 84 sections

01 — Start here

Four pages, and you can run anything.

Read them in order the first time. Together they take about the length of a coffee, and every other page assumes them.

01 · 4 min Quickstart Five steps, no SDK to install, any HTTP client. Ten minutes if you already hold some crypto. 02 · 3 min Authentication Both methods work on every network and on both protocols. Pick per server, mix them freely. 03 · 3 min Endpoints & ports Location is never in the hostname. Shared gateways read it from the username; dedicated proxies are fixed at the order. 04 · 4 min Targeting & sessions Country, US state, city, provider, session identity and lifetime. Six parameters, in any order, on both shared gateways.

02 — By network

The same gateway rules, four different behaviours.

Rotation, billing, delivery and the details that differ per network, each on its own page. Prices live on the product pages; the docs explain what you get for them.

Residential res.hodlproxy.com:9000 · 9001 Rotating or sticky, per GB, 199 countries ISP your IP :8000 · 8001 Static residential IPs, unlimited traffic Datacenter your IP :8000 · 8001 100 GB per IP each month, pooled Mobile mob.hodlproxy.com:9000 · 9001 Carrier pool per GB, or a dedicated device

03 — Your first request

One line in any language.

The proxy URL carries everything: credentials, the gateway and the parameters. The target below simply echoes the IP it sees, so you can verify the exit before pointing the same code at real work.

-cc-us asks for a United States household; run it twice, get two addresses
Same syntax on mob.hodlproxy.com for the mobile pool
Dedicated addresses take no parameters: ip:8000 with their own credentials
HTTPS targets tunnel through CONNECT; TLS stays end to end

All code examples

cURL

curl -x http://USER-cc-us:[email protected]:9000 https://api.ipify.org

Python

import requests

proxy = "http://USER-cc-us:[email protected]:9000"
r = requests.get("https://api.ipify.org",
                 proxies={"http": proxy, "https": proxy}, timeout=30)
print(r.text)

Node.js

import { fetch, ProxyAgent } from "undici";

const dispatcher = new ProxyAgent("http://USER-cc-us:[email protected]:9000");
const res = await fetch("https://api.ipify.org", { dispatcher });
console.log(await res.text());

PHP

$ch = curl_init("https://api.ipify.org");
curl_setopt_array($ch, [
    CURLOPT_PROXY          => "http://res.hodlproxy.com:9000",
    CURLOPT_PROXYUSERPWD   => "USER-cc-us:PASS",
    CURLOPT_RETURNTRANSFER => true,
]);
echo curl_exec($ch);

proxyURL, _ := url.Parse("http://USER-cc-us:[email protected]:9000")
client := &http.Client{Transport: &http.Transport{Proxy: http.ProxyURL(proxyURL)}}
resp, err := client.Get("https://api.ipify.org")

04 — Integrate and operate

Protocol details, working code, every error, the API.

For the day you wire HodlProxy into something real: what happens on the wire, what each status means, how the wallet is charged and how to drive it all from code.

Integrate · 2 min Protocols Standard protocols, no custom client. This page is the precise behaviour for people who need to know what happens on the wire. Integrate · 3 min Code examples Every snippet fetches https://api.ipify.org through a United States residential exit and prints the IP. Swap the username parameters and the target, nothing else changes. Integrate · 4 min Errors & troubleshooting Gateway errors come with a short reason in the body. Target errors pass through untouched. Telling the two apart is most of troubleshooting. Account · 3 min Wallet & billing Top up from $20, buy traffic or rent addresses from the balance. Nothing expires, nothing renews without you. Account · 6 min API reference Everything the dashboard does, as JSON over HTTPS. Base URL https://api.hodlproxy.com/v1, Bearer authentication, cursor pagination. Account · 2 min Limits & fair use Short page on purpose. The technical limits fit in one table; the rules of use fit in one list.

05 — Beyond the reference

Guides for the tools you use, a glossary for the words.

The reference says what the gateway does. The guides show it inside Python, Node.js, Playwright, Scrapy, browsers and agents; the glossary defines every term in one paragraph; the payment page explains the crypto wallet.

Guides · 17 Integrations, method, buying Copy-ready setups for requests, undici, cURL, Go, PHP, Playwright, Puppeteer, Selenium, Scrapy, browsers, anti-detect profiles and AI agents; sessions, testing, budgets, troubleshooting. Glossary · 73 terms Every proxy term, defined first Residential, ISP, datacenter and mobile; rotation and sticky sessions; targeting; CONNECT and SOCKS5; detection; billing; errors. One quotable definition per page, then how it applies here. Payments · crypto only How the wallet is funded Accepted coins, confirmation times and fees, how a top-up becomes USD balance, the bonus ladder, what is never asked at sign-up, refunds.

06 — Questions

Before you open the first page.

Where do I find my credentials?

In the dashboard under Credentials, once the account is funded: one username and one password for the residential and mobile gateways. Dedicated ISP, datacenter and mobile-device orders come with their own ip:port:user:pass lines. The same data is returned by GET /v1/credentials and GET /v1/proxies.

Do I need different credentials per network?

No. The shared gateways res.hodlproxy.com and mob.hodlproxy.com take the same username and password; only the hostname changes. Dedicated addresses each have their own pair, printed in your list, and the IP whitelist covers every endpoint at once.

Is there an SDK to install?

No, and none is needed. HodlProxy proxies are standard HTTP(S) and SOCKS5 proxies, so every language, library, browser and tool that can use a proxy already works. The code examples page covers the clients people use most.

Can I use the same username parameters on mobile?

Yes. -cc-, -asn-, -sid- and -ttl- behave identically on mob.hodlproxy.com; -state- and -city- exist for the residential pool. On the mobile pool -asn- is how you choose a carrier.

How is traffic measured on the pool networks?

Every byte that crosses the gateway in both directions counts: request and response, headers and TLS records included. Connections that fail before reaching the target are not billed. ISP proxies and dedicated mobile devices are unmetered; datacenter orders carry a monthly pool.

What does testing cost?

A top-up of $20, which stays on your balance until you spend it. Buy a few GB on residential, or rent a single ISP address or a mobile device for 24 hours, run the recipe from the quickstart against your real target and scale from there.

Ready when you are

Read the quickstart, then run it for real.

Create your account, top up $20 and send the first request against your own target. What you do not use stays on your balance.

Create an account Quickstart

Proxies

Menu