Mobile proxies
Real 4G and 5G carrier IPs, the highest trust level a target recognises. Same gateways, ports and username grammar as residential; a different pool selector. Billed per GB, traffic never expires.
Mobile proxies use real carrier IPs. Carriers share one public IP across thousands of subscribers, so a target that blocks it blocks real customers, which is why these IPs pass where others fail.
- Real 4G / 5G carrier IPs, never datacenter
- Rotating by default, sticky sessions up to 24 hours
- Country, region, city, carrier (by ASN) and OS targeting
- HTTP, HTTPS and SOCKS5 over TCP and UDP
- Billed per GB used; traffic never expires
How mobile differs from residential
Everything on the Residential proxies page applies to how you connect, with one change: the username starts with pool-mobile instead of network-residential. Mobile is a separate plan with its own traffic balance and its own price per GB.
| Residential | Mobile | |
|---|---|---|
| Pool selector: | network-residential | pool-mobile |
| Device type: | Desktop by default | Mobile devices on carrier networks |
| Gateways and ports: | gw-eu, gw-us, gw-as · 5555, 7777, 1080 | Same |
| Targeting parameters: | country, region, city, asn, os, session, ttl | Same |
| Plan: | Residential plan, billed per GB at the residential rate | Mobile plan, billed per GB at the mobile rate, bought separately |
Gateways and ports
| Region | Host |
|---|---|
| Europe: | gw-eu.datafuel.ai |
| United States: | gw-us.datafuel.ai |
| Asia: | gw-as.datafuel.ai |
Port 5555 for HTTP, HTTPS and SOCKS5 over TCP and UDP; 7777 for HTTP and HTTPS only; 1080 for SOCKS5 over TCP only.
Rotating versus sticky
Rotating. Omit session and every request gets a new carrier IP.
curl --proxy gw-us.datafuel.ai:5555 \
--proxy-user pool-mobile-country-us:$PASSWORD \
https://ipinfo.io/json
⟧ Sticky. Add session-<id> to keep the same IP across requests, and ttl-<minutes> to say for how long, up to 1440 minutes (24 hours).
curl --proxy gw-us.datafuel.ai:5555 \
--proxy-user pool-mobile-country-us-session-a91f3-ttl-30:$PASSWORD \
https://ipinfo.io/json
⟧ Mobile IPs are shared by many real subscribers and change more often than residential ones; keep sessions as short as the task allows.
Examples
Country and city
curl --proxy gw-eu.datafuel.ai:5555 \
--proxy-user pool-mobile-country-gb-region-england-city-london-session-39yrj3:$PASSWORD \
https://ipinfo.io/json
⟧ Country and region
curl --proxy gw-us.datafuel.ai:5555 \
--proxy-user pool-mobile-country-us-region-texas-session-39yrj3:$PASSWORD \
https://ipinfo.io/json
⟧ Several countries at once. The IP comes from any of them.
curl --proxy gw-eu.datafuel.ai:5555 \
--proxy-user pool-mobile-country-de,gb,fr:$PASSWORD \
https://ipinfo.io/json
⟧ A specific carrier, by ASN. T-Mobile US is AS21928; see the carrier table below.
curl --proxy gw-us.datafuel.ai:5555 \
--proxy-user pool-mobile-country-us-asn-21928-session-a91f3:$PASSWORD \
https://ipinfo.io/json
⟧ Operating system of the device
curl --proxy gw-eu.datafuel.ai:5555 \
--proxy-user pool-mobile-country-de-os-android-session-7288t722:$PASSWORD \
https://ipinfo.io/json
⟧ Carrier and region together. asn cannot be combined with city, but it can with region.
curl --proxy gw-us.datafuel.ai:5555 \
--proxy-user pool-mobile-country-us-region-california-asn-22394-session-c41b:$PASSWORD \
https://ipinfo.io/json
⟧ SOCKS5. Same username, SOCKS5 on port 5555; use socks5h so DNS is resolved through the proxy.
curl --proxy socks5h://gw-us.datafuel.ai:5555 \
--proxy-user pool-mobile-country-us-session-a91f3:$PASSWORD \
https://ipinfo.io/json
⟧ From the Asia gateway, for servers in the region; the exit country is still set by the username.
curl --proxy gw-as.datafuel.ai:5555 \
--proxy-user pool-mobile-country-jp-session-9d1e:$PASSWORD \
https://ipinfo.io/json
⟧ In your code
Python, requests
import requests
proxy = "http://pool-mobile-country-us-session-a91f3:PASSWORD@gw-us.datafuel.ai:5555"
r = requests.get("https://ipinfo.io/json", proxies={"http": proxy, "https": proxy}, timeout=30)
print(r.json())
⟧ Node.js, fetch with undici
import { ProxyAgent, fetch } from "undici";
const dispatcher = new ProxyAgent(
"http://pool-mobile-country-us-session-a91f3:PASSWORD@gw-us.datafuel.ai:5555"
);
const res = await fetch("https://ipinfo.io/json", { dispatcher });
console.log(await res.json());
⟧ Go, net/http
proxyURL, _ := url.Parse("http://pool-mobile-country-us-session-a91f3:PASSWORD@gw-us.datafuel.ai:5555")
client := &http.Client{Transport: &http.Transport{Proxy: http.ProxyURL(proxyURL)}}
res, _ := client.Get("https://ipinfo.io/json")
⟧ Write the username exactly as in the curl examples; URL-encode the password if it contains reserved characters.
Choosing a carrier
Target a carrier with its ASN rather than its name. Some common ones:
| Carrier | Country | ASN |
|---|---|---|
| T-Mobile US: | US | 21928 |
| Verizon Wireless: | US | 22394 |
| AT&T Mobility: | US | 20057 |
| Vodafone UK: | GB | 25135 |
| Deutsche Telekom: | DE | 3320 |
| TIM: | IT | 3269 |
asn and city cannot be combined; use region with asn when you need both a carrier and a place.
Buying and managing
Mobile proxies are a separate plan from residential, with their own traffic balance and their own credentials. In the User API, mobile is a product of the residential service: the same endpoints manage it, and the plan you address is the one created by buying the mobile product. Mobile traffic is billed per GB at the mobile rate on the pricing page, never expires, and is not drawn from a residential balance. A pool-mobile username authenticated with residential credentials, or the other way round, is refused with 407.
Managing the plan with the User API
Everything the dashboard does for a plan is also available at https://api.datafuel.ai with an API key sent as Authorization: Bearer df_live_…. Read operations need the api.residential.read scope; reading credentials or generating proxies needs api.residential.manage. Full reference: Residential proxies · User API.
1. Find the plan id. Plans are listed newest first with the traffic left on each. Residential and mobile are two products in the same API, and you hold one plan per product: pick the plan whose product is mobile traffic.
curl https://api.datafuel.ai/api/v1/residential/plans \
--header "Authorization: Bearer $API_KEY"
⟧ {
"results": [
{
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"name": "Mobile proxies",
"status": "active",
"traffic": { "total_gb": 100, "used_gb": 12.4, "remaining_gb": 87.6 }
}
]
}
⟧ Reference: List your plans.
2. Check what the plan can target. Get a plan returns the plan with a targeting block: which of region, city and asn it accepts, whether sticky sessions and session_minutes are allowed, and the operating systems os can name. A field the plan cannot target is refused with 400.
curl https://api.datafuel.ai/api/v1/residential/plans/$PLAN \
--header "Authorization: Bearer $API_KEY"
⟧ {
"id": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
"name": "Mobile proxies",
"status": "active",
"targeting": {
"region": true,
"city": true,
"asn": true,
"sticky": true,
"session_minutes": true,
"os": ["android", "ios"],
"os_multiple": false
}
}
⟧ Reference: Get a plan.
3. Find region, city and ASN codes. The region and city values in a username are codes, not free text. Ask the plan for the codes in a country, optionally filtered by region or by a search term; the answer carries at most 200 of each.
curl "https://api.datafuel.ai/api/v1/residential/plans/$PLAN/locations?country=US&search=los" \
--header "Authorization: Bearer $API_KEY"
⟧ {
"country": "US",
"regions": [ { "code": "california", "name": "California" } ],
"cities": [ { "code": "losangeles", "name": "Los Angeles" } ]
}
⟧ Use the code values in the username: region-california-city-losangeles. Reference: List regions and cities.
ASNs have their own list. List ASNs searches by name or number and answers with at most 200. The list is global, not per country, so pick one that operates where your proxies exit.
curl "https://api.datafuel.ai/api/v1/residential/plans/$PLAN/asns?search=t-mobile" \
--header "Authorization: Bearer $API_KEY"
⟧ {
"asns": [ { "code": "21928", "name": "T-Mobile USA" } ]
}
⟧ Use the code as asn-21928 in a username. asn cannot be combined with city. Reference: List ASNs.
4. Generate ready-made proxies. Instead of composing usernames yourself, ask the plan for quantity proxies with the targeting you need. Each comes back with the right gateway for its country, a username carrying the targeting and a session, and the plan’s password. Nothing is created or charged by this call. Without country, each proxy exits in a random country of the plan.
curl https://api.datafuel.ai/api/v1/residential/plans/$PLAN/proxies \
--request POST \
--header "Authorization: Bearer $API_KEY" \
--header 'Content-Type: application/json' \
--data '{
"country": "US",
"region": "california",
"city": "losangeles",
"rotation": "sticky",
"session_minutes": 60,
"quantity": 5,
"format": "json"
}'
⟧ {
"proxies": [
{
"host": "gw-us.datafuel.ai",
"port": 5555,
"username": "pool-mobile-country-us-region-california-city-losangeles-session-8f2a91-ttl-60",
"password": "…",
"country": "US"
}
]
}
⟧ rotation is rotating (the default: a new IP between requests) or sticky (each proxy keeps its IP for session_minutes). format: txt returns one host:port:username:password per line, ready to paste into a tool. Reference: Generate proxies.
asn exits through one carrier or ISP, in place of city, and os lists the operating systems the exit device may run, such as ["android"]; it takes more than one only when the plan’s targeting.os_multiple is true.
5. Credentials and usage. The plan’s base username and password come from Get the credentials; Reset the credentials issues a new password and invalidates the old one at once. Requests and traffic over a window, as a daily series, come from Get a plan’s usage. Buying and topping up is Buy traffic, with an Idempotency-Key per order.
Troubleshooting
| Symptom | Check |
|---|---|
407 Proxy Authentication Required: | The password, or a typo in the username. Mobile usernames start with pool-mobile, not network-mobile, and need the credentials of a mobile plan, not of a residential one |
| The IP is not a carrier IP: | Check that the username starts with pool-mobile; os-android on a residential username selects a device type, not a carrier network |
| No IP for a narrow target: | Mobile pools are smaller than residential; widen city to region or drop asn |
| Port or target refused: | See Limits and restrictions |
| Another status from the gateway: | See Status codes |