Util::ReCaptcha3 - Google ReCaptcha v3 recognition
Overview of the scraper
This scraper is designed to be used as a pluggable component in other scrapers where it may be necessary to solve Google ReCaptcha v3.
The principle of this scraper's operation consists of sending ReCaptcha data (this is always the sitekey and the url of the page where the ReCaptcha was obtained) to a solving service and receiving a token consisting of numbers and letters in response. The correctness of the solving depends only on the solving service; as a rule, services almost always solve ReCaptchas correctly.
Features
- Support for working with these services: AntiCaptcha, RuCaptcha, 2captcha, XEvil, CapMonster, CapMonster.cloud, CapSolver, captchas.io, NextCaptcha
- Ability to configure response wait time and status check delay
Use Cases
- Recognition of Google ReCaptcha v3 in built-in scrapers where solving captchas is optionally or mandatory to obtain results
- Recognition of Google ReCaptcha v3 in custom JS scrapers
Queries
The scraper accepts queries in the following format:
sitekeyurl
Parameters are separated by a space and mean:
sitekey- this is the ReCaptcha sitekey, in some services it is called websitekey. As a rule, the sitekey needs to be obtained from the page code and is usually found in the URL of the connected script:
https://www.google.com/recaptcha/api.js?render=SITEKEY
Also, the sitekey in the page code can be specified as a function argument:
grecaptcha.execute(SITEKEY, {action:'verify'}).
url- the page where the ReCaptcha is located
Results output examples
$resp- ReCaptcha response$error- if an error occurred, its description
ReCaptcha token output
Result format:
$resp
Result example:
03AGdBq24qfVWiRMofkMHuxaaW024vkt2Oc4Nnt4WXs3PdV0fJlpDystp444u_rG8HvuJUgN3n-upnHJXeQODxHjn_X9JdRlKEzhDnatYyehxN00WDWN_37LKwdHOgER2TrdB7XBKqrz5rko_CGWea6R1Lfe3eKmkoOeHkTyn8H3ZI90wcSvZR8gSztvq5EZWpGdNgLq15w84F92-PR8S051gUH2Ls82An0N4iiAIcTFrOTQZizqfIjgVzCzqHhSaigIPGy6j8-3nt1sac7q6Xn26fKLsQzd4hZDmrlem5rNoK-IQHEb_AUJ6r4UxQZQ-z4hk9wPpzdeiCi81sxWEX5YI-cn4cWYFsoWutv_DYvZy87Iog7u1VELGWvjT3XwkY3MyDZzpUfauyCGSd5oouLDhV5YnRPfMm-gWQUSRpt28z5xbVbwGSAfmMLEpFboCgKZdUhb-IdAiKHGA4oSXB3RhOA9TQZR-ETVqyUG8A4wJEXdCvEHU7Uhw
Possible settings
The Provider parameter is used to select the service to be used.
For online services (AntiCaptcha, RuCaptcha, 2captcha, CapMonster.cloud, CapSolver, captchas.io), the Client key parameter must be set.
| Parameter | Default value | Description |
|---|---|---|
| Client key | Client key for online solving services | |
| Provider url | Provider URL, allows overriding the domain. Multiple can be specified separated by commas; the scraper will use each of them in random order. Can be empty; the scraper automatically uses the required one depending on the selected solving service | |
| Provider | AntiCaptcha | Solving service |
| Wait between get status | 5 | Delay between status checks |
| Max wait time | 300 | Maximum wait time for solving |
| minScore | 0.3 | Minimum confidence level for the result. Selected experimentally for each individual site. When contacting the solving service, it defines a filter by which a worker with the required minimum score is selected |
| pageAction | The value of the action parameter passed to Google, which the site owner then sees when checking the token. Usually specified as a function argument: grecaptcha.execute('sitekey', {action:'ACTION VALUE'}) | |
| isEnterprise | ☐ | Tells the solving service to solve this ReCaptcha as Recaptcha Enterprise V3. Does not work in all solving services |