Skip to main content
This article will introduce a Cloudflare Turnstile Protocol Recognition API integration guide, which allows users to bypass the recognition and clicking of Turnstile CAPTCHA by simply submitting the Website Key for automatic decoding in the background to complete the verification.

​
Application Process

To use the Cloudflare Turnstile Protocol Recognition API, first go to the Ace Data Cloud Console to obtain your API Token for future use. If you are not logged in or registered, you will be automatically redirected to the login page to invite you to register and log in, and after completion, you will be automatically returned to the current page. One API Token can call all services on the platform without needing to apply separately for each service. The first application will grant a free quota for a trial experience; when the quota is insufficient, you can recharge the general balance in the console.
📘 Complete Documentation: Cloudflare Turnstile Protocol Recognition API →

​
Basic Usage

First, understand the basic usage, which is to input the website URL that needs to process the Turnstile CAPTCHA to obtain the processed result. You need to simply pass a website_url field. Our example website is: https://react-turnstile.vercel.app, and we need to obtain the website_key from the website_url page. First, open this webpage, press F12 to enter the console, and perform a global search for cf-turnstile in the Element page to find the container element that carries Turnstile, where the string corresponding to data-sitekey is the value of the website_key. The Request Headers set include:
  • accept: the format of the response result you want to receive, here filled as application/json, which means JSON format.
  • authorization: the key to call the API, which can be directly selected after application.
Additionally, the Request Body is set, including:
  • website_url: the website URL that needs to process the CAPTCHA.
  • website_key: the website key identifier (sitekey) in Cloudflare Turnstile.
  • action: an optional parameter that only needs to be passed when the target website has set a custom action for the Turnstile component.
  • cdata: an optional parameter that only needs to be passed when the target website has set a custom cData for the Turnstile component.
Click the “Try” button to test, and we get the following result:
The returned result contains multiple fields, described as follows:
  • token: the verification result after processing the Cloudflare Turnstile CAPTCHA task.
  • started_at, finished_at: the time when this request started processing and produced results, in Unix timestamp (seconds, float).
  • elapsed: the total time taken for this processing (seconds).
We can see that we obtained the verification result for processing the Turnstile CAPTCHA, which we can then use for POST or simulate submission to the target website, for one-time use, valid for 120 seconds, and it is recommended to use it within 60 seconds. When submitting, the token is usually sent as the cf-turnstile-response parameter to the target website, and the corresponding Python code to call the token verification is as follows:
If you want to generate the corresponding integration code, you can directly copy the generated code, for example, the CURL code is as follows:
The Python integration code is as follows:

​
Asynchronous Mode (async)

By default, the API is synchronous and blocking: a request will wait until the token processing is complete before returning. If you are doing multi-solver rotation and want to “immediately get the task_id after submitting the task, then schedule other solvers and come back later to read the result,” you can pass async: true in the request body. After passing async: true, the interface will immediately return a task_id without blocking:
To actively check the progress, you can use the task_id to query POST /captcha/tasks (recommended every 3-5 seconds). This interface will not trigger or advance task processing; even if you do not query, lose network connection, or exit the client, the server will continue processing:
During processing, it will return status: processing; when processing is complete, it will return status: ready and the token:
Billing Explanation: In asynchronous mode, creating a task and reading the “processing” status are not charged; the client is charged once when it first reads the successful result (consistent with existing behavior and synchronous mode pricing). The server will autonomously advance the task, but will not charge in advance just because the background completes first. If the task is not successful within 120 seconds, it will terminate with HTTP 504 timeout, and no charge will be incurred. /captcha/tasks does not advance the task.
Note: Cloudflare Turnstile does not currently support Bring Your Own Proxy, so this interface does not accept the proxy parameter; if passed, it will return 400 invalid_proxy.

​
Error Handling

When calling the API, if an error occurs, the API will return the corresponding error code and message. For example:
  • 400 token_mismatched：Bad request, possibly due to missing or invalid parameters.
  • 400 invalid_proxy：Bad request, proxy is not supported for this captcha type.
  • 401 invalid_token：Unauthorized, invalid or missing authorization token.
  • 429 too_many_requests：Too many requests, you have exceeded the rate limit.
  • 500 api_error：Internal server error, something went wrong on the server.

​
Error Response Example

​
Conclusion

Through this document, you have learned how to use the Cloudflare Turnstile protocol recognition API to allow users to bypass recognizing and clicking on the Turnstile captcha, achieving automatic decoding in the background simply by submitting the Website Key. We hope this document helps you better integrate and use this API. If you have any questions, please feel free to contact our technical support team.