Skip to main content

Util::ReCaptcha2 - recognition of reCaptcha

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::GoogleSE::Google, SE::Google::ImagesSE::Google::Images, SE::Google::ByImageSE::Google::ByImage, as well as custom JavaScript parsers.

The principle of operation of this parser is to send reCaptcha data (usually it is 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 captchas correctly.

Details of the connection and configuration process of this parser are described in the article ReCaptcha Settings

Parser Use Cases​

Example of setting up solving via Xevil​

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

Provider url in Xevil for the Util parser::ReCaptcha2

In the Provider field, select Xevil (AntiGate):

Configuring the Provider url for the Util parser::ReCaptcha2

Capabilities​

  • Supports working with services such as: 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 embedded parsers, where it is optionally or mandatory to solve captchas to obtain results
  • Recognition of captchas in custom JS parsers

Queries​

The parser accepts two types of requests:

  • sitekey url
  • sitekey url proxy user-agent

The parameters are separated by a space and mean:

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

Output Results Options​

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

Captcha 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.

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

note

Common settings for all parsers

ParameterDefault ValueDescription
Client keyClient key for online captcha solving services
Provider urlProvider URL, allows to override 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 automatically uses the necessary one depending on the selected captcha solving service
ProviderAntiCaptchaCaptcha solving service
Wait between get status5Delay between getting status
Max wait time300Maximum waiting time for solving
Threshold % for (Capmonster.cloud)0Confidence threshold (used only in capmonster.cloud)
Last updated