hCaptchaGnizer - template for ZennoPoster

#1
6d9908c4f6[1].png
https://2captcha.com/ru/software/hcaptchagnizer----shablon-dlya-zennoposter

How to test the work through the Browser?
  1. Open the "test_project_Browser.xmlz" template in ProjectMaker.
  2. Enter your API key for the RuCaptcha service in the ZennoPoster settings (if they are already set, then you can skip this step).
  3. Run the template and look at the output (and in the log window to see if there are any errors).

How to test work in GET / POST mode?
  1. Open the "test_project_GETandPOST.xmlz" template in ProjectMaker.
  2. Enter your API key for the RuCaptcha service in the ZennoPoster settings (if they are already set, then you can skip this step).
  3. Run the template and look at the output (and in the log window to see if there are any errors).
  4. PS: The Get / Post mode is activated using the "IN_is_getpost" variable: any value must be passed to it (for example, yes).

How to use it in your templates?
  • Register the API key for RuCaptcha in the ZP / PM settings or add it to the Key_RuCaptcha.txt file next to the hCaptchaGnizer.xmlz template.
  • Add the "Project in project" cube to your template and select hCaptchaGnizer.xmlz in it.
  • Make a submission (sending) of the form where hCaptcha is located yourself: click on the button or execute the necessary js-code for the submission (you will need to figure out how to do this yourself). If you have a solution via GET / POST, then do it by analogy with the test template (see above).
  • Description of variables
  • IN_page_url - URL of the page with huyapcha. You need to fill it in for GET / POST mode, in the browser version it will be filled in by itself.
  • OUT_response - the resulting token from the captcha service will go into this variable.
  • OUT_captcha_id - captcha identifier in the service. It can be useful if you need to send a report about an incorrect decision.
  • OUT_badend - the text of the error, if it occurred inside the template.
  • IN_attempts - the number of attempts to get the result. Default: 250.
  • IN_delay_ms - time to wait between attempts to get the result (in milliseconds). Default: 2000 ms.
  • IN_debug - whether to display the execution log in ZP (always displayed in PM). By default: do not display, i.e. empty value.
  • IN_is_getpost - activation of the work mode via GET / POST.
  • IN_page_content - content of the page with hCaptcha for GET / POST mode (so that the template will parse the sitekey from there). You can pass nothing, then the template itself will try to get the page code from IN_page_url.
  • IN_proxy - a proxy for an employee who will decide on the service (must be available to him, i.e. without binding).
  • IN_proxytype - proxy type (SOCKS4, SOCKS5, HTTPS, HTTP).
  • IN_show_response_field - show token input field.
  • IN_show_timer - show the timer (for how long the captcha was solved in the service). Default: yes, show.
  • IN_sitekey - sitekey from the hkapcha that needs to be solved. If there are several of them on the page, then it is useful to pass the correct one into the variable.