Proxies and browser identity.
Configure your proxy and carry the successful IP, user agent and client hints into the final request.
Proxies and browser identity
7 guides in Proxies and browser identity
Page 1 of 1
Choose and configure a proxy for CAPTCHA solving
Proxy URL formatting, pinned sessions, and fixes for HTTP 407, unreachable targets, and rejected solutions.
Use the proxy that actually solved the task
Map egressAttempts to the original proxy list, select the winner with an SDK helper, and reuse it with the returned browser identity.
Use the returned user agent and client hints
Set User-Agent and sec-ch-ua from the ready solution, replace stale headers, and submit through the successful proxy.
Submit a CAPTCHA token through a Go HTTP proxy
Configure a separate Go HTTP client for token submission, select the successful proxy and handle target headers, forms, cookies and responses.
The API connection and the CAPTCHA proxy are different
Understand which connection the task proxy controls, keep the target submission on the same exit, and diagnose HTTP_PROXY misrouting.
Size a proxy pool for CAPTCHA solves
A four-flow proxy allocation example, with candidate fallback rules and separate solve and proxy budgets.
Keep application cookies when submitting a solved token
Keep application cookies, the form's CSRF value, and the solver's proxy and browser headers together when submitting a token.
Looking for a field or endpoint?
The API reference lists every request field, task state and response shape.