Documentation — Mobile Proxy API

Quick Start

Get your first proxy request running in under a minute. You need: an active proxy on your account and an API token from your dashboard.

Sign up at mobileproxy.space.
Order a proxy — pick country & operator on the buy page.
Copy your API token from the API page while logged in.
Make your first request — pick a language below.

curl --request GET \
 --url 'https://mobileproxy.space/api.html?command=get_my_proxy' \
 --header 'Authorization: Bearer YOUR_API_TOKEN'

import requests
r = requests.get(
"https://mobileproxy.space/api.html",
params={"command": "get_my_proxy"},
headers={"Authorization": "Bearer YOUR_API_TOKEN"},
timeout=10,
)
print(r.json())

const res = await fetch(
"https://mobileproxy.space/api.html?command=get_my_proxy",
{ headers: { Authorization: "Bearer YOUR_API_TOKEN" } }
);
console.log(await res.json());

req, _ := http.NewRequest("GET",
"https://mobileproxy.space/api.html?command=get_my_proxy", nil)
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN")
resp, _ := http.DefaultClient.Do(req)
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))

Rate limit: 3 req/sec × N active proxies. Same request cooldown: 3 sec. HTTP 429 on exceed.

Authentication

All API calls authenticate with a personal Bearer token. The token is bound to your account, not to an individual proxy.

Where to get your token

Log into your dashboard and open API. The token field is at the top. You can rotate the token at any time — the old one is revoked immediately.

Sending the token

Authorization: Bearer YOUR_API_TOKEN

IP allowlist (optional)

For extra safety you can restrict API calls to a single IP. Set it under Allowed IP on the API page. Requests from any other IP will be rejected even with a valid token.

Proxy authentication

Proxies themselves use either login/password (default) or IP authorisation. Set this per proxy in the dashboard. With IP auth, no credentials are sent on the proxy connection.

Core Concepts

Mobile carrier IPs

Every proxy in the network is a real 4G/5G modem connected to a real mobile carrier (MTS, Beeline, T-Mobile, Vodafone, etc.). Target sites see traffic as coming from a regular smartphone on a cellular network — not a datacenter.

CGNAT — why mobile IPs are «shared»

Mobile carriers route thousands of subscribers through the same public IP via Carrier-Grade NAT. Bans against a single IP would block real customers, so anti-fraud systems treat mobile IPs more leniently than residential or datacenter IPs. This is the structural reason mobile proxies have higher trust scores.

Rotation

You change the external IP on demand by triggering a modem reconnect:

By link — hit a unique URL (changeip.host/?proxy_key=…) to rotate. Returns the new IP in JSON.
By timer — auto-rotate every N minutes (configurable per proxy).
None (sticky) — keep the same IP until you ask.

Sticky sessions

A «sticky» session is just a proxy with rotation disabled (or a long timer). All requests through that proxy share one IP for the duration. Useful for multi-step flows (login → checkout, parsing across multiple pages of a session).

Session persistence across rotations

Cookies, localStorage and TLS sessions live on the client — not the proxy. After a rotation your existing session in the browser/library survives; only the source IP changes.

Integrations

Drop-in snippets for the most common stacks. Replace PROXY_HOST, PROXY_PORT, LOGIN, PASSWORD with the values from get_my_proxy.

import requests
proxy = "http://LOGIN:PASSWORD@PROXY_HOST:PROXY_PORT"
r = requests.get("https://httpbin.org/ip",
 proxies={"http": proxy, "https": proxy},
 timeout=15)
print(r.json())

import { HttpsProxyAgent } from "https-proxy-agent";
const agent = new HttpsProxyAgent("http://LOGIN:PASSWORD@PROXY_HOST:PROXY_PORT");
const res = await fetch("https://httpbin.org/ip", { agent });
console.log(await res.json());

proxyURL, _ := url.Parse("http://LOGIN:PASSWORD@PROXY_HOST:PROXY_PORT")
client := &http.Client{Transport: &http.Transport{Proxy: http.ProxyURL(proxyURL)}}
resp, _ := client.Get("https://httpbin.org/ip")
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))

curl -x http://LOGIN:PASSWORD@PROXY_HOST:PROXY_PORT https://httpbin.org/ip
# SOCKS5
curl --socks5 LOGIN:PASSWORD@PROXY_HOST:SOCKS_PORT https://httpbin.org/ip

import { chromium } from "playwright";
const browser = await chromium.launch({
proxy: {
server: "http://PROXY_HOST:PROXY_PORT",
username: "LOGIN",
password: "PASSWORD",
},
});
const page = await browser.newPage();
await page.goto("https://httpbin.org/ip");
console.log(await page.content());
await browser.close();

from seleniumwire import webdriver
opts = {"proxy": {
"http": "http://LOGIN:PASSWORD@PROXY_HOST:PROXY_PORT",
"https": "http://LOGIN:PASSWORD@PROXY_HOST:PROXY_PORT",
"no_proxy": "localhost,127.0.0.1",
}}
driver = webdriver.Chrome(seleniumwire_options=opts)
driver.get("https://httpbin.org/ip")
print(driver.page_source)
driver.quit()

Official SDKs and full examples on GitHub: Python · Node · PHP · OpenAPI spec.

Use Cases

What developers actually build with mobile proxies. Each card is a typical pattern.

Web scraping

Rotate IPs per request or per session, combine with browser fingerprinting tools.

Browser automation

Playwright / Selenium with one proxy per worker, sticky sessions for stateful flows.

Verification & QA

Check geo-targeted content, pricing, A/B variants from real carrier networks.

Ad / SERP checking

SERP scraping, ad placement verification, mobile-specific creative checks.

SMM & multi-account

One mobile proxy per account — the carrier-grade IP profile most resembles a real user.

Data pipelines

Background workers behind a rotating pool, retries on rotation, structured error logging.

API Reference

The full REST reference — every endpoint, parameter and response shape — lives on the dedicated API page. It's auto-personalised with your token when you're logged in.

Full REST API documentation

~15 endpoints: proxy management, IP rotation, blacklists, geo/operator lookup, balance.

Open API Reference

Most used endpoints

GET /api.html?command=get_my_proxy
GET CHANGEIP_HOST/?proxy_key=…
GET /api.html?command=proxy_ip&proxy_id=…
GET /api.html?command=change_equipment&…
GET /api.html?command=get_geo_operator_list

Troubleshooting

Top issues developers hit, with the standard fix. Full FAQ is on the FAQ page.

Connection times out / refused

Check the proxy is active in the dashboard, IP allowlist matches your machine's egress IP, and you're using the right port for HTTP vs SOCKS5.

Rotation returns the same IP

The carrier may reassign the same address — normal on small pools. Trigger rotation again, or switch operator with change_equipment.

Target site shows captcha

Captchas correlate with the fingerprint, not just the IP. Pair the mobile IP with a mobile User-Agent, mobile viewport, and consistent TLS profile. See Fingerprint generator.

Session expires unexpectedly

Auto-rotation is firing in the middle of your session. Either disable timer rotation, or capture cookies/tokens before rotating.

Geo mismatch / wrong country

Mobile carriers occasionally route via foreign hops. Verify with proxy_ip and reroute via change_equipment if needed.

HTTP 429 from the API

You've hit the rate limit. Add exponential backoff, cache get_my_proxy responses, batch by sending proxy_id lists where supported.

Best Practices

Retry strategy

Wrap every proxy request in retry-with-jitter (3 attempts, 500ms–3s). On 429, back off exponentially. On connection errors, rotate before retrying.

Session management

One proxy per logical session. Persist cookies/localStorage per worker. Never share an HTTP keep-alive pool across rotations.

Rotation intervals

For scraping — rotate per request or every 30–120 sec. For account work — long sticky sessions (hours), rotate only on explicit logout/error.

Browser consistency

Match User-Agent to the carrier (4G → mobile UA). Set timezone & locale to the proxy's region. Disable WebRTC IP leak.

Ban avoidance

Stay within human-plausible request rates. Randomise request timing. Pair mobile IP with mobile fingerprint — not a desktop one.

Observability

Log proxy_id, current IP, response code and rotation events together. When something breaks, you'll know whether it was the IP, the fingerprint or the target.

Developer Documentation