Quick start

Send your first mobile proxy request in 5 minutes. The flow mirrors residential — the main difference is the type segment.

No KYC is required to start. We may request verification later if your account triggers a risk review (see ID verification); if that happens, requests can return 403 with X-Helodata-Error-Code: kyc-required until you complete it.

1. Create a mobile sub-user

1. Open Dashboard → Mobile → Sub-users → Create sub-user.
2. Name it and pick a password.
3. Copy the issued sub-user name (e.g. s1a2b3c4d5e).

Mobile sub-users are billed and rate-limited separately from residential sub-users.

2. Build your username

Simplest case — any US mobile IP:

helo_s1a2b3c4d5e-type-mob-region-us

To pin a specific carrier, append the ASN — strongly recommended on mobile, see ASN targeting:

helo_s1a2b3c4d5e-type-mob-region-us-asn-6167   # Verizon Wireless

3. Send the request

curl

curl -x http://helo_s1a2b3c4d5e-type-mob-region-us:[e-mail]:7777 \
     https://ipv4.icanhazip.com

Python (requests)

import requests

USER = "helo_s1a2b3c4d5e-type-mob-region-us-asn-6167"
PASS = "PASSWORD"
proxy = f"http://{USER}:{PASS}@gate.helodata.io:7777"

r = requests.get(
    "https://ipv4.icanhazip.com",
    proxies={"http": proxy, "https": proxy},
    timeout=60,                                    # mobile is slower — bump the timeout
)
print(r.text.strip())

Node.js (undici)

import { fetch, ProxyAgent } from "undici";

const user = "helo_s1a2b3c4d5e-type-mob-region-us-asn-6167";
const pass = "PASSWORD";
const agent = new ProxyAgent(`http://${user}:${pass}@gate.helodata.io:7777`);

const res = await fetch("https://ipv4.icanhazip.com", { dispatcher: agent });
console.log((await res.text()).trim());

Expect ~1–3 seconds latency on the first hop — mobile networks are slower than wired. Bump your client timeout to at least 30s.

4. Common next steps

Goal	Add to username
Pin a carrier	-asn-2516 (KDDI), -asn-6167 (Verizon Wireless), …
Keep the same IP up to 1 hour	-session-job1-sesstime-60
Switch country	replace -region-us

What's next

• ASN targeting — recommended for every mobile workload
• Sessions & rotation — mobile sticky sessions go up to 60 min
• ID verification — not required to start; risk-based only