Util::ReCaptcha3 - recognition of Google ReCaptcha v3
Parser Overview
This parser is designed for use as a connectable component in other parsers, where it may be necessary to solve Google ReCaptcha v3.
The principle of operation of this parser is to send reCaptcha data (this is always sitekey and the URL of the page where the reCaptcha was received) to the solving service and receive a token in response, consisting of numbers and letters. The correctness of solving depends only on the solving service, usually the services almost always solve reCaptchas correctly.
Capabilities
- Supports working with such services: AntiCaptcha, RuCaptcha, 2captcha, XEvil, CapMonster, CapMonster.cloud, CapSolver, captchas.io
- Ability to adjust response waiting time and status check delay
Use Cases
- Recognition of Google ReCaptcha v3 in built-in parsers, where it is optionally or necessarily required to solve captchas to obtain results
- Recognition of Google ReCaptcha v3 in custom JS parsers
Queries
The parser accepts requests in the following format:
sitekeyurl
The parameters are separated by a space and mean:
sitekey- this is the sitekey of the reCaptcha, in some services it is called websitekey. Usually, the sitekey needs to be obtained from the page code and usually it is located 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 an argument of the function:
grecaptcha.execute(SITEKEY, {action:'verify'}).
url- the page where the reCaptcha is located
Output Results 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), it is necessary to set the Client key parameter.
| 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 parser will use each of them in random order. Can be empty, the parser automatically uses the necessary one depending on the selected solving service | |
| Provider | AntiCaptcha | Solving service |
| Wait between get status | 5 | Delay between getting the status |
| Max wait time | 300 | Maximum solving waiting time |
| minScore | 0.3 | Minimum confidence score for the result. Experimentally selected for each individual site. When accessing the solving service, it determines the filter by which a worker with the required minimum score is selected |
| pageAction | Value of the action parameter passed to Google, which is then seen by the site owner when checking the token. Usually specified as an argument of the function: grecaptcha.execute('sitekey', {action:'ACTION VALUE'}) | |
| isEnterprise | ☐ | Indicates to the solving service that this reCaptcha needs to be solved as Recaptcha Enterprise V3. Does not work in all solving services |