Util::ReCaptcha3 - Google ReCaptcha v3 recognition
Overview of the scraper
This scraper is intended to be used as a plug-in component in other scrapers where Google ReCaptcha v3 may need to be solved.
The principle of operation of this scraper is to send recaptcha data (which is always the sitekey and the URL of the page where the recaptcha was received) to a solving service and receive a token consisting of numbers and letters in response. The correctness of solving depends only on the solving service; typically, services almost always solve recaptchas correctly.
Capabilities
- Supports working with services such as: AntiCaptcha, RuCaptcha, 2captcha, XEvil, CapMonster, CapMonster.cloud, CapSolver, captchas.io, NextCaptcha
- Ability to configure response timeout and status check delay
Use Cases
- Recognizing Google ReCaptcha v3 in built-in scrapers, where it is optionally or necessarily required to solve captchas to get results
- Recognizing Google ReCaptcha v3 in custom JS scrapers
Queries
The scraper accepts queries in the form:
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 may be specified as a function argument:
grecaptcha.execute(SITEKEY, {action:'verify'}).
url- the page on which the recaptcha is located
Output Results Examples
$resp- recaptcha response$error- if an error occurred, its description
Recaptcha token output
Result format:
$resp
Example result:
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), it is mandatory to set the parameter Client key.
| Parameter | Default value | Description |
|---|---|---|
| Client key | Client key for online solving services | |
| Provider url | Provider URL, allows overriding the domain. Multiple URLs can be specified separated by commas; the scraper will use each of them in random order. Can be empty; the scraper will automatically use the correct one depending on the selected solving service | |
| Provider | AntiCaptcha | Solving service |
| Wait between get status | 5 | Delay between status retrieval |
| Max wait time | 300 | Maximum solving wait time |
| minScore | 0.3 | Minimum trust score for the result. Determined experimentally for each individual site. When contacting the solving service, it defines a filter to select a worker with the required minimum score |
| pageAction | The value of the action parameter that is passed to Google and is then seen by the site owner when checking the token. Usually specified as a function argument: grecaptcha.execute('sitekey', {action:'ACTION_VALUE'}) | |
| isEnterprise | ☐ | Instructs the solving service to solve this recaptcha as Recaptcha Enterprise V3. This does not work for all solving services |