RecaptchaV2TaskProxyless: bypass Google Recaptcha automatically without proxies

This type of task solves Google Recaptcha V2 without proxy. The task is executed using our own proxy servers and/or workers’ IP addresses.

At the moment, Recaptcha does not have protection from situations where a puzzle is solved on one IP address and the form with the g-response is submitted from another. Google’s API does not provide the IP address of the person who solved their Recaptcha. If this changes, you may always use our standard type of task for that – RecaptchaV2Task.

Recaptcha V2 example

Task object

Previous name of task type: NoCaptchaTaskProxyless. It will be supported forever, no need to update your code.
websiteURLStringYesAddress of a target web page. Can be located anywhere on the web site, even in a member area. Our workers don’t navigate there but simulate the visit instead.
Recaptcha website key.
recaptchaDataSValueStringNoValue of ‘data-s’ parameter. Applies only to Recaptchas on Google web sites.
isInvisibleBooleanNoSpecify whether or not Recaptcha is invisible. This will render an appropriate widget for our workers.

Request example

curl -i -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -X POST -d '{

Response example

JSON with no errors

    "errorId": 0,
    "taskId": 7654321

JSON with an error

    "errorId": 1,
    "errorCode": "ERROR_KEY_DOES_NOT_EXIST",
    "errorDescription": "Account authorization key not found in the system"

Retrieve the solution

Use method getTaskResult to request the solution. Give the worker about 5 seconds before making your first request. If the worker is still busy, retry in 3 seconds.

Task solution object

gRecaptchaResponseStringToken string required for interacting with the submit form on the target website.
cookiesArrayOptional array of cookies used for solving Recaptchas. Applies only for domains and subdomains.

Response example