Skip to main content

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​

  • ✅ reCAPTCHA v2 ("I'm not a robot")
  • ❌ reCAPTCHA v3 (not supported with proxies due to significantly reduced success rate)

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).

ParameterTypeRequiredDescription
proxystringNoProxy 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)
proxytypestringNoOne of: HTTP, HTTPS, SOCKS4, SOCKS5

You can pair proxy parameters with the usual fields for the captcha type you are solving (e.g., method=userrecaptcha, googlekey, pageurl for reCAPTCHA v2).

Examples​

Example A — reCAPTCHA v2 with IP‑authenticated HTTP proxy​

Request params (GET)
{
  "key": "YOUR_API_KEY",
  "method": "userrecaptcha",
  "googlekey": "YOUR_SITE_KEY",
  "pageurl": "https://example.com/login",
  "proxy": "123.123.123.123:3128",
  "proxytype": "HTTP"
}

Example B — reCAPTCHA v2 with login:password SOCKS5 proxy​

Request params (GET)
{
  "key": "YOUR_API_KEY",
  "method": "userrecaptcha",
  "googlekey": "YOUR_SITE_KEY",
  "pageurl": "https://example.com/login",
  "proxy": "user123:pass456@198.51.100.20:1080",
  "proxytype": "SOCKS5"
}

Example C — Turnstile with proxy (same params)​

Request params (GET)
{
  "key": "YOUR_API_KEY",
  "method": "turnstile",
  "sitekey": "SITE_KEY_FROM_PAGE",
  "pageurl": "https://example.com",
  "proxy": "user:pass@203.0.113.7:3128",
  "proxytype": "HTTPS"
}

After submission, poll res.php as usual to retrieve the solution. For some integrations (e.g., Turnstile), you may need json=1 when retrieving to obtain structured fields.

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; results will likely degrade and are not supported.
  • Proxy quality: Prefer stable, low‑latency residential or datacenter proxies with consistent uptime. Avoid public/open proxies.
  • 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.