> For the complete documentation index, see [llms.txt](https://docs.ipdunar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ipdunar.com/products/overview-1/authentication.md).

# Authentication

Mobile uses the same two authentication models as residential — pick whichever fits your runtime. The mechanics are identical; only the `type` segment in the username changes.

## Model A — User + password (default)

```bash
curl -x http://ipdunar_s1a2b3c4d5e-type-mob-region-us:PASSWORD@gate.ipdunar.com:7777 \
     https://example.com
```

The password is the mobile sub-user password. Mobile and residential sub-users have independent passwords even if the names look similar.

## Model B — IP whitelist

```bash
curl -x http://ipdunar_s1a2b3c4d5e-type-mob-region-us@gate.ipdunar.com:7777 \
     https://example.com
```

To register IPs: **Dashboard → Mobile → {Sub-user} → Whitelisted IPs**. Up to 50 IPv4 addresses or CIDR ranges per sub-user. Changes take effect within 60 seconds.

> Note: residential and mobile maintain **separate whitelists**. Adding an IP to your residential sub-user does not authorize it for mobile.

## Mobile-specific: risk-based KYC

KYC is **not required by default**. If your account is flagged for a risk review, requests may return the following until verification is completed:

```
HTTP/1.1 403 Forbidden
X-IPdunar-Error-Code: kyc-required
```

This is the exception, not the norm. See [ID verification (KYC)](https://docs.ipdunar.com/account-and-billing/kyc.md).

## Choosing between them

The same trade-offs as residential — see [Residential authentication](https://docs.ipdunar.com/products/overview/authentication.md#choosing-between-them). The mobile-specific consideration: if your client is a mobile device or NAT egress that itself uses cellular/dynamic IPs, IP whitelisting is impractical; default to user+password.

## Rotating credentials

To rotate a mobile sub-user password:

1. **Dashboard → Mobile → {Sub-user} → Reset password**.
2. Old password works for 60 seconds, then begins returning `407`.
3. Update your deployment.

## API

Whitelisted IPs and sub-user credentials are managed via the [Whitelists API](https://docs.ipdunar.com/api-reference/whitelists.md) and [Sub-users API](https://docs.ipdunar.com/api-reference/sub-users.md). Scope the `product` parameter to `mobile`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ipdunar.com/products/overview-1/authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
