> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nodemaven.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Getting Started with Mobile proxies

> Connect a NodeMaven Mobile proxy in minutes. Endpoint, ports, code examples, and what differs from Residential.

This guide gets you from zero to a working Mobile proxy connection. Mobile proxies route your traffic through real 4G, 5G, and LTE mobile devices on carrier networks.

Looking for a different product? See [Getting Started with Residential proxies](/quickstart/residential-proxies) or [Getting started with ISP proxies](/quickstart/isp-proxies).

## Your connection details

| Setting | Value |
| - | - |
| Host | gate.nodemaven.com |
| HTTP ports | 8080-9080 and 32000-33000 |
| SOCKS5 ports | 1080-2080 and 42000-43000 |
| Username | Your proxy username, plus any targeting parameters |
| Password | Your proxy password |

Any port within those ranges works. The dashboard gives you 8080 for HTTP and 1080 for SOCKS5 by default, but if a port is blocked on your network, pick another from the range.

## Step 1 - Switch to Mobile

Go to **Rotating Residential Proxy** in the dashboard and set **Connection type** to **Mobile**. Everything else on the page stays the same - Mobile and Residential share one setup screen and one gateway.

Your **Proxy username** and **Proxy password** appear under **Proxy generator**.

![Mobile proxies option](https://downloads.intercomcdn.com/i/o/yvkc0rpk/2578126401/216f200edbfa79503dc04cb98289/Screenshot+2026-07-31+at+10_29_29.png)

## Step 2 - Check your proxy works

Before setting anything up elsewhere, confirm the proxy is healthy. Click **Check proxy** next to your generated proxy in the dashboard.

We run a live check and show you three things:

* **Fraud risk** - for example, "Low fraud risk."
* **Resolved location and IP** - for example, "GB, England, Newcastle upon Tyne, 92.40.200.195"
* **A link to Scamalytics** for that IP, if you want the full report

This takes one click, needs nothing installed, and confirms both that the proxy works and that it is coming out where you expect. Do this first whenever something looks wrong.

![Check proxy in the dashboard](https://downloads.intercomcdn.com/i/o/yvkc0rpk/2578126770/83b1c3196c15d3c64bdc2005a472/Screenshot+2026-07-31+at+10_52_55.png)

![IP health and quality check](https://downloads.intercomcdn.com/i/o/yvkc0rpk/2578126966/330d1fe49d46936572f413e4a577/Screenshot+2026-07-31+at+10_54_45.png)

## Step 3 - Make your first request from your own tools

Once Check proxy looks good, you can wire the proxy into your own code. Replace USERNAME and PASSWORD with your own credentials in one of the examples below.

**cURL**

```bash theme={null}
curl -x "http://USERNAME-country-us:PASSWORD@gate.nodemaven.com:8080" https://ipinfo.io/json
```

**Python**

```python theme={null}
import requests

username = "USERNAME-country-us"
password = "PASSWORD"
proxy = f"http://{username}:{password}@gate.nodemaven.com:8080"

response = requests.get(
    "https://ipinfo.io/json",
    proxies={"http": proxy, "https": proxy},
)
print(response.text)
```

**Node.js**

```javascript theme={null}
const axios = require('axios');
const { HttpsProxyAgent } = require('https-proxy-agent');

const agent = new HttpsProxyAgent(
  'http://USERNAME-country-us:PASSWORD@gate.nodemaven.com:8080'
);

axios.get('https://ipinfo.io/json', { httpsAgent: agent })
  .then(res => console.log(res.data));
```

<Note>
  **Python and Node examples will not work if you paste them straight into a terminal.** They are programs, not shell commands - save them to a file first and run the file. Only the cURL example runs directly in a terminal.
</Note>

If the response shows a US IP rather than your own, your proxy is working.

## Step 4 - Target a location

Add parameters to your username as key-value pairs. Mobile usernames include -type-mobile, which the dashboard adds for you when Connection type is set to Mobile:

```text theme={null}
USERNAME-country-gb-region-england-type-mobile
```

| Parameter | Example | What it does |
| - | - | - |
| -country- | -country-us | Country, two-letter code |
| -region- | -region-california | State or province |
| -city- | -city-los\_angeles | City |
| -zip- | -zip-90039 | ZIP or postal code (replaces region and city) |
| -type-mobile | -type-mobile | Routes through mobile carrier IPs. Added automatically when Connection type is Mobile. |

Mobile inventory is smaller than Residential, so deep targeting narrows your available pool faster. If you are targeting a specific city and connections are slow to establish, try loosening to region or country level.

Easier option: set the location in the dashboard and copy the generated username. Country and Region show a **High** badge where we have strong inventory.

![Specific location selection options](https://downloads.intercomcdn.com/i/o/yvkc0rpk/2578136127/22f7ece09c13374c0a003a8cf1fd/Screenshot+2026-07-31+at+11_02_47.png)

## Step 5 - Session control

Under **Advanced settings**, pick a **Session type**:

* **Sticky** (default) - holds the same IP for up to 24 hours. If that IP goes offline you get a new one from the same location, so your connection keeps working.

* **No rotating** - the IP never changes, even if it goes offline. The session waits for your original IP to return rather than substituting another. To get a new IP, generate a new proxy string with a new SID or just change the SID in your current proxy string.

* **Rotating** - a new IP on every request.

In the username:

```text theme={null}
Sticky        USERNAME-country-gb-type-mobile-sid-abc123
```

```text theme={null}
No rotating   USERNAME-country-gb-type-mobile-sid-abc123-norotate-true
```

```text theme={null}
Rotating      USERNAME-country-gb-type-mobile
```

Sticky also takes a **Custom** duration in seconds, which appears as -ttl- (500 seconds becomes -ttl-8m20s).

![Proxy session type options](https://downloads.intercomcdn.com/i/o/yvkc0rpk/2578142959/25d6ccb502a5dc1d04022769c0bf/Screenshot+2026-07-31+at+11_06_10.png)

## Step 6 - Choose an IP filter mode

Also under **Advanced settings**, **IP filter mode** controls which IPs you route through:

| Mode | Username parameter | Use when |
| - | - | - |
| Quality (default) | -filter-medium | You want the cleanest IPs and best success rate |
| Quality + Speed | -filter-medium-speed-fast | Clean IPs but also low latency |
| Speed | -speed-fast | Latency matters more than filtering |
| Max pool size | (none) | Maximum IP variety |

![Proxy quality filter setting](https://downloads.intercomcdn.com/i/o/yvkc0rpk/2578147586/b3ecaee8d71470fb5273890626fd/Screenshot+2026-07-31+at+11_08_51.png)

## Step 7 - Copy your proxy string

The **Proxy generator** builds your full string as you change settings. Two formats are available: **Host:Port**, which most anti-detect browsers and proxy tools expect, and **Protocol**, for code and command-line tools.

Set **Proxies quantity** to generate several at once, then copy them or **Export** as .csv or .txt.

![Proxy generator with format and quantity options](https://downloads.intercomcdn.com/i/o/yvkc0rpk/2578155094/5d794da9ff8009c1c3356d03788a/Screenshot+2026-07-31+at+11_13_37.png)

## Step 8 - Use it in your tool

Scroll to **Open in Anti-detect browser** to launch straight into a supported tool: Dolphin\{anty}, BitBrowser, AdsPower, MostLogin, GeeLark, DICloak.

For step-by-step setup in these and other tools, see the [Integrations](/integrations/multilogin-x) section of this help center.

## Tracking your usage

Go to **Dashboard** in the left navigation for traffic and request charts, plus a breakdown by domain. Filter by user, product, and time period.

**The product filter separates Proxy from Scraping Browser, not Residential from Mobile.** Residential and Mobile draw on one shared traffic balance and are not reported separately anywhere in the dashboard.

![Dashboard traffic charts filtered by product](https://downloads.intercomcdn.com/i/o/yvkc0rpk/2578158347/fe8a4ee18400bba2048835efe03d/Screenshot+2026-07-31+at+11_15_48.png)

## If something isn't working

* Check your username and password are copied exactly, with no trailing spaces
* Confirm your port is inside the supported ranges - 8080-9080 or 32000-33000 for HTTP, 1080-2080 or 42000-43000 for SOCKS5
* If one port is blocked on your network, try another from the range
* If connections are slow to establish in a narrow location, loosen the targeting or switch IP filter mode to **Max pool size** - Mobile inventory is smaller than Residential
* Use **Check proxy** to confirm the IP itself is healthy

For more, see the [Troubleshooting](/troubleshooting/overview) section of this help center.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.