Cloudflare Clearance (cf_clearance) solver API

Solve request#

Solving Cloudflare Clearance 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 16s. 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#

• Restoring a crawl that has hit a managed challenge
• Availability monitoring behind an interstitial
• Archiving public pages that gate on a browser check

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.

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.

{
  "clientKey": "void_a1b2c3d4e5f60718293a4b5c6d7e8f90",
  "task": {
    "type": "CFClearance",
    "url": "https://example.com/",
    "proxy": "proxy.example.com:9090:user:pass"
  }
}

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.cf_clearance(
    url="https://example.com/",
    proxy="proxy.example.com:9090:user:pass",
)

print(result.value)

Example response#

A successful solve returns errorId: 0 and a solution object. The result is in solution.cf_clearance; 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.

This type also returns solution.user_agent. The exact User-Agent the cookie was earned with. Send this verbatim on every request carrying the cookie; the response also repeats it as userAgent.

This type also returns solution.sec_ch_ua. The sec-ch-ua client hint that went with the solve. Cloudflare checks the hints against the User-Agent, so sending one without the others is worse than sending neither.

This type also returns solution.sec_ch_ua_platform. The sec-ch-ua-platform hint for the same identity. The solve is a Windows profile end to end.

This type also returns solution.cf_bm. The __cf_bm Bot Management cookie the site set during the solve. Some sites check it as well as, or instead of, cf_clearance; send it with the other cookies.

This type also returns solution.cookies. Every cookie the site set during the solve, name to value, cf_clearance and __cf_bm included. The simplest thing to replay is all of them.

{
  "errorId": 0,
  "status": "ready",
  "solution": {
    "cf_clearance": "9pQzR2.LmXv1…",
    "user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/154.0.0.0 Safari/537.36",
    "sec_ch_ua": ""Chromium";v="154", "Not=A?Brand";v="24", "Google Chrome";v="154"",
    "sec_ch_ua_platform": ""Windows"",
    "cf_bm": "…",
    "cookies": { "cf_clearance": "…", "__cf_bm": "…" },
    "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 Clearance can return, on top of the shared authentication and billing set. Branch on errorCode, not on the HTTP status.

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": "CFClearance",
        "url": "https://example.com/",
        "proxy": "proxy.example.com:9090:user:pass"
    },
}

# 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["cf_clearance"])
print(solution["userAgent"])

Questions#