Task type
Cloudflare Turnstile solver API
Turnstile is Cloudflare's replacement for a visible captcha, embedded as a widget that returns a token to the host page. It is the one type that needs no proxy from you: the URL and the site key are the whole request, and the solve runs from our own network. You do not send the widget's action or cData either — we open the page and read the widget's own parameters off it, so there is nothing to copy across and nothing to get wrong. Submit the token in the cf-turnstile-response field exactly as it is returned; it is single-use and Cloudflare stops accepting it a few minutes after it is minted, so spend it on the request you were making rather than storing it.
Tip
task.type as Turnstile and the solution arrives in solution.token.A site that will not solve is worth telling us about — coverage is per target as much as per type. The quickest route is Telegram (@VoidCaptchaSupport), where someone usually answers within minutes. You can also open a ticket from your dashboard or email [email protected]. Send the URL and the site key either way.
Solve request#
Solving Cloudflare Turnstile is a single synchronous call. You post one task object and the response carries the finished solution — no task id to store, nothing to poll for.
The connection is held open for the whole solve, which for this type runs a median of 2.1s. Set a client timeout that covers it — the default socket timeout in most HTTP libraries is shorter than the work. If holding a connection that long does not suit your worker fleet, the same task goes to /v1/createTask and you collect it from /v1/checkTask instead.
When to use it#
- Testing a registration form protected by the widget
- Synthetic monitoring of a signup funnel
- Checking the widget renders and verifies across regions
Task object structure#
These fields go inside task. The envelope around it — clientKey and the optional softId — is the same for every type and is described in the API reference.
| Property | Type | Required | Description |
|---|---|---|---|
type | string | Required | Literal "Turnstile". Matching is case-insensitive. |
url | string | Required | The page the widget is embedded on.e.g. https://example.com/register |
site_key | string | Required | The Turnstile site key, normally starting 0x.e.g. 0x4AAAAAAADnPIDROrmt1Wwj |
user_agent | string | Optional | Pin the User-Agent used for the solve. Omit it and a coherent one is chosen for you and returned in the response — match whatever you send downstream.e.g. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 … |
Example payload#
The whole body, assembled from the table above — copy it formatted to read, or on one line to paste straight into a terminal or a REST client. The values are placeholders: swap the key for your own and the URL and site key for the page you are solving.
https://api.voidcaptcha.com/v1/getResult{
"clientKey": "void_a1b2c3d4e5f60718293a4b5c6d7e8f90",
"task": {
"type": "Turnstile",
"url": "https://example.com/register",
"site_key": "0x4AAAAAAADnPIDROrmt1Wwj"
}
}Example request#
The smallest thing that gets a token back, in your language. Python and Node.js use the official client (pip install voidcaptcha, npm install voidcaptcha); every other language makes the HTTP call its standard library already has. The complete version, with the key read from the environment and the error envelope checked, is in Sample code at the bottom of this page.
Language choice is remembered across the whole site, so switching here carries to every other sample in the docs.
# pip install voidcaptcha
from voidcaptcha import VoidCaptcha
client = VoidCaptcha("void_a1b2c3d4e5f60718293a4b5c6d7e8f90")
result = client.turnstile(
url="https://example.com/register",
site_key="0x4AAAAAAADnPIDROrmt1Wwj",
)
print(result.value)Example response#
A successful solve returns errorId: 0 and a solution object. The result is in solution.token; alongside it is the userAgent the solve ran under.
solution carries those and nothing else — the gateway copies the result field, anything extra this type returns, and userAgent across, and drops the rest of whatever the solver sent. Timing arrives at the top level as elapsedMs, present only when the duration is known, beside cost and your remaining balance. The figures below are illustrative: nothing here is a published median.
{
"errorId": 0,
"status": "ready",
"solution": {
"token": "03AGdBq25V6…",
"userAgent": "Mozilla/5.0 …"
},
"cost": "$0.0012",
"balance": "$411.24",
"elapsedMs": 4820
}Send that userAgent on your downstream request as well — for the cookie-based types the result is bound to it and will be rejected under a different one.
Errors for this type#
The codes Cloudflare Turnstile can return, on top of the shared authentication and billing set. Branch on errorCode, not on the HTTP status.
| Code | HTTP | Meaning | Retry |
|---|---|---|---|
ERROR_KEY_MISSING | 401 | No clientKey was supplied. | Do not retry |
ERROR_KEY_INVALID | 401 | The key does not exist or has been revoked. | Do not retry |
ERROR_KEY_SUSPENDED | 403 | The account attached to this key is suspended. | Do not retry |
ERROR_TYPE_NOT_ENABLED | 403 | This account is not enabled for the requested task type. | Do not retry |
ERROR_SITE_UNREACHABLE | 200 | The target host did not respond in time. | Retry with backoff |
ERROR_CAPTCHA_UNSOLVABLE | 200 | The challenge was served but could not be completed. | Retry |
ERROR_TIMEOUT | 200 | The solve exceeded the maximum time for this type. | Retry with backoff |
ERROR_INSUFFICIENT_BALANCE | 402 | Your balance will not cover this solve. | Do not retry |
ERROR_THREAD_LIMIT | 429 | You have more solves in flight than your key permits. | Retry with backoff |
ERROR_RATE_LIMITED | 429 | Too many requests in a short window. | Retry with backoff |
Every code, with the fix for each, is on the error reference. A failed solve is never charged.
Sample code#
A complete file: key from the environment, task built, error envelope checked, result used. It calls the endpoint directly rather than through an SDK, so it works as a starting point in any language.
import os
import sys
import requests
API = "https://api.voidcaptcha.com/v1/getResult"
payload = {
"clientKey": os.environ["VOIDCAPTCHA_KEY"],
"task": {
"type": "Turnstile",
"url": "https://example.com/register",
"site_key": "0x4AAAAAAADnPIDROrmt1Wwj"
},
}
# The endpoint is synchronous: it holds the connection open for the whole
# solve, so the read timeout has to cover it, not just the handshake.
res = requests.post(API, json=payload, timeout=180).json()
if res["errorId"] != 0:
sys.exit(f"{res['errorCode']}: {res['errorDescription']}")
solution = res["solution"]
# Carry the User-Agent downstream — the result was earned under it.
print(solution["token"])
print(solution["userAgent"])Last updated on 2 August 2026