> 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/integrations/antidetect-browsers/multilogin.md).

# Multilogin

Multilogin is the most fingerprint-fidelity-focused option among antidetect browsers. Its proxy support covers all ipdunar products.

## Per-profile setup

1. **New profile** → **Proxy** section.
2. **Connection type**: HTTP or SOCKS5.
3. Fill in:

### Residential / Mobile (gateway)

| Field    | Value                                                               |
| -------- | ------------------------------------------------------------------- |
| Host     | `gate.ipdunar.com`                                                  |
| Port     | `7777`                                                              |
| Login    | `ipdunar_s1a2b3c4d5e-type-res-region-us-session-prof01-sesstime-30` |
| Password | sub-user password                                                   |

### ISP

| Field    | Value                 |
| -------- | --------------------- |
| Host     | `198.51.100.42`       |
| Port     | `8000`                |
| Login    | `ipdunar_s1a2b3c4d5e` |
| Password | sub-user password     |

4. Click **Check proxy** — Multilogin probes and shows the exit IP, country, and timezone.
5. Multilogin will offer to **auto-match fingerprint** to the proxy's country. Accept it.

\[screenshot: Multilogin profile creation with ipdunar proxy]

## Bulk via API

Multilogin's Local API can create profiles programmatically — useful for spinning up N profiles, each bound to one ISP IP:

```bash
curl -X POST http://127.0.0.1:35000/api/v1/profile \
  -H "Content-Type: application/json" \
  -d '{
    "name": "isp-us-042",
    "os_type": "windows",
    "proxy": {
      "type": "http",
      "host": "198.51.100.42",
      "port": 8000,
      "username": "ipdunar_s1a2b3c4d5e",
      "password": "PASSWORD"
    }
  }'
```

Loop over your ISP list to provision profiles in seconds.

## Fingerprint match

Multilogin's strength is matching the browser fingerprint to the proxy's locale. Enable **Match fingerprint to proxy country**:

* Language headers align with the country
* Timezone derives from the proxy IP
* WebGL / Canvas fingerprints are randomized within country norms

## Verify

Hit `https://browserleaks.com/ip` + `https://browserleaks.com/javascript` and check IP, timezone, navigator.language all align.

## Common pitfalls

* **`MultiloginProxyError: AUTHENTICATION_FAILED`** — gateway products require the full username (`ipdunar_...-type-res-region-us`), not just `ipdunar_s1a2b3c4d5e`.
* **Profile launched before proxy check** — Multilogin will sometimes hold a stale proxy in memory; restart the profile after editing.


---

# 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/integrations/antidetect-browsers/multilogin.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.
