Skip to main content

Util::Turnstile - recognition of Cloudflare Turnstile captcha

Util::Turnstile parser overview

This parser is used only as a connectable component in other parsers, where it may be necessary to solve Cloudflare Turnstile captchas, as well as in custom JavaScript parsers.

The principle of operation of this parser is to send Turnstile data (usually it is sitekey and the URL of the page on which the Turnstile captcha 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 Turnstile correctly.

TODO: (next) Describe connection/usage and/or provide a link to an example


  • Supports working with such services: AntiCaptcha, RuCaptcha, 2captcha,, CapSolver,
  • Ability to configure response waiting time and status check delay

Use cases

  • Bypassing Cloudflare Turnstile in parsers where it is optionally or necessarily required to solve this type of captcha to obtain results


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 Turnstile sitekey
  • url - the page on which the Turnstile is located
  • proxy - the proxy through which Cloudflare Turnstile 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 Turnstile was received


As a result, the Cloudflare Turnstile token will be output:


Possible results

  • $resp - Cloudflare Turnstile response (token)
  • $error - if an error occurred, its description

Possible settings

The Provider parameter is used to select the service.

ParameterDefault valueDescription
Client key-Client key for online solving 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 necessary one depending on the selected solving service
ProviderAntiCaptchaSolving service
Wait between get status5Delay between status retrieval
Max wait time300Maximum solving waiting time
Threshold % for Capmonster.Cloud0Confidence threshold (used only in