# Using Proxies

> **Availability:** Proxy usage is **disabled by default**. Ask support to enable it for your account before using.


Proxies let CaptchaAI solve certain browser‑based challenges as if the request comes from the same IP that loads the target page. This is often **required when the protection enforces IP matching** (e.g., Cloudflare, Datadome). It is **optional** in many other cases.

## Supported CAPTCHA types

* Cloudflare Turnstile
* reCAPTCHA v2
* reCAPTCHA v3 (not recommended with proxies)


## Supported proxy types & authentication

* Types: `HTTP`, `HTTPS`, `SOCKS4`, `SOCKS5`
* Authentication: by **IP allowlisting** or **login:password** credentials


## How CaptchaAI uses your proxy

* The service checks that the proxy is reachable by attempting to open the target website *through your proxy*.
* If the proxy works, CaptchaAI will **load the challenge through the proxy** for solving.


## Request parameters

These parameters are added to your **`in.php`** submission (or the corresponding method endpoint).

| Parameter | Type | Required | Description |
|  --- | --- | --- | --- |
| `proxy` | string | No | Proxy address. Formats:• IP auth: `ip:port` (e.g., `123.123.123.123:3128`)• Login/password: `login:password@ip:port` (e.g., `user:pass@123.123.123.123:3128`) |
| `proxytype` | string | No | One of: `HTTP`, `HTTPS`, `SOCKS4`, `SOCKS5` |


## Examples

### Example A: reCAPTCHA v2 with IP‑authenticated HTTP proxy


```bash
curl -X POST "https://ocr.captchaai.com/in.php" \
  -H "Content-Type: multipart/form-data" \
  -F "key=YOUR_API_KEY" \
  -F "method=userrecaptcha" \
  -F "googlekey=YOUR_SITE_KEY" \
  -F "pageurl=https://example.com/login" \
  -F "proxy=123.123.123.123:3128" \
  -F "proxytype=HTTP"
```

### Example B: reCAPTCHA v2 with login:password SOCKS5 proxy


```bash
curl -X POST "https://ocr.captchaai.com/in.php" \
  -H "Content-Type: multipart/form-data" \
  -F "key=YOUR_API_KEY" \
  -F "method=userrecaptcha" \
  -F "googlekey=YOUR_SITE_KEY" \
  -F "pageurl=https://example.com/login" \
  -F "proxy=user123:pass456@198.51.100.20:1080" \
  -F "proxytype=SOCKS5"
```

### Example C: Turnstile with proxy (same params)


```bash
curl -X POST "https://ocr.captchaai.com/in.php" \
  -H "Content-Type: multipart/form-data" \
  -F "key=YOUR_API_KEY" \
  -F "method=turnstile" \
  -F "sitekey=SITE_KEY_FROM_PAGE" \
  -F "pageurl=https://example.com/login" \
  -F "proxy=user123:pass456@203.0.113.13:1080" \
  -F "proxytype=SOCKS5"
```

> After submission, poll `res.php` as usual to retrieve the solution with your Task ID.


## Notes & best practices

* **When to use**: Only when required by the target site’s anti‑bot policy (IP match). Otherwise, omit for best success rate and latency.
reCAPTCHA v3: Do not use proxies unless you are experiencing bad scores; results will likely degrade and are not recommended.
* **Troubleshooting**: If you repeatedly get proxy‑related failures, verify reachability from your network and confirm the proxy can access the `pageurl` domain. Replace or remove the proxy if unreachable.