Util::ReCaptcha2 - captcha recognition

Util::ReCaptcha2 parser overview

This parser is used only as a connectable component in other parsers, where it may be necessary to solve Google ReCaptcha v2, for example: SE::Google, Rank::Ahrefs, as well as custom JavaScript parsers.

The principle of operation of this parser is to send captcha data (usually it is sitekey and the URL of the page where the captcha was received) to the recognition service and receive a token in response, consisting of numbers and letters. The correctness of solving depends only on the recognition service, usually the services almost always solve captchas correctly.

The process of connecting and configuring this parser is described in detail in the article Captcha Configuration

Go to DEMOBuy A-Parser Pro ($299)

Util::ReCaptcha2 use cases

ReCaptcha in JS parsers

Example of a JS parser for working with captchas

Learn more

Capabilities

• Supports working with such services: AntiCaptcha, RuCaptcha, 2captcha, XEvil, CapMonster, CapMonster.cloud, CapSolver, captchas.io
• Ability to configure response waiting time and status check delay

Usage options

• Recognition of captchas in built-in parsers, where it is optional or mandatory to solve captchas to obtain results
• Recognition of captchas in custom JS parsers

Requests

The parser accepts two types of requests:

• sitekey url
• sitekey url proxy user-agent

Parameters are separated by a space and mean:

• sitekey - this is the sitekey of the captcha
• url - the page where the captcha is located
• proxy - the proxy through which the captcha was received. The parameter must be in the format login:pass@ip:port@type for proxies with authorization or ip:port@type for proxies without authorization
  • type can be http, https, socks4, socks5
• user-agent - the user agent with which the captcha was received

Results

As a result, the captcha token will be displayed:

03AGdBq24qfVWiRMofkMHuxaaW024vkt2Oc4Nnt4WXs3PdV0fJlpDystp444u_rG8HvuJUgN3n-upnHJXeQODxHjn_X9JdRlKEzhDnatYyehxN00WDWN_37LKwdHOgER2TrdB7XBKqrz5rko_CGWea6R1Lfe3eKmkoOeHkTyn8H3ZI90wcSvZR8gSztvq5EZWpGdNgLq15w84F92-PR8S051gUH2Ls82An0N4iiAIcTFrOTQZizqfIjgVzCzqHhSaigIPGy6j8-3nt1sac7q6Xn26fKLsQzd4hZDmrlem5rNoK-IQHEb_AUJ6r4UxQZQ-z4hk9wPpzdeiCi81sxWEX5YI-cn4cWYFsoWutv_DYvZy87Iog7u1VELGWvjT3XwkY3MyDZzpUfauyCGSd5oouLDhV5YnRPfMm-gWQUSRpt28z5xbVbwGSAfmMLEpFboCgKZdUhb-IdAiKHGA4oSXB3RhOA9TQZR-ETVqyUG8A4wJEXdCvEHU7Uhw

Possible results

• $resp - captcha response
• $error - if an error occurred, its description

Example of solving configuration through Xevil

In Xevil, it is recommended to choose the API type Antigate (Anti-Captcha). In the settings of Util::ReCaptcha2 in Provider url you need to specify ip:port Xevil:

and select Provider - Xevil:

Possible settings

The Provider parameter is used to select the service.

For online recognition services (AntiCaptcha, RuCaptcha, 2captcha, CapMonster.cloud, CapSolver, captchas.io), the Client key parameter must be set.

info

General settings for all parsers.

Parameter	Default value	Description
Client key	-	Client key for online recognition services
Provider url	-	Provider URL, allows you to override the domain. You can specify several separated by commas, the parser will use each of them in random order. Can be empty, the parser automatically uses the required one depending on the selected recognition service
Provider	AntiCaptcha	Recognition service
Wait between get status	5	Delay between getting status
Max wait time	300	Maximum recognition waiting time
Threshold % for (Capmonster.cloud)	0	Confidence threshold (used only in capmonster.cloud)