EverySolve CAPTCHA API

Cloudflare challenge page API

EverySolve's Cloudflare challenge page API returns cookie values for your challenge workflow. Send POST /api/v1/captcha with type set to cloudflare_challenge and the inputs listed below.

A Cloudflare challenge page blocks the destination before it loads and is different from an embedded Turnstile widget. The result is cookie data such as a clearance credential. Turnstile returns a form token and uses a site key instead.

Endpoint
POST /api/v1/captcha
Type
cloudflare_challenge
Per 1,000 successful solutions
$1.81 per 1,000 successful solutions

Request parameters

Provide website_url and proxy. Optional parameters are user_agent.

Required parameters

website_urlproxy

Optional parameters

user_agent
cloudflare_challenge.sh
curl -X POST https://api.everyinfra.com/api/v1/captcha \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"type":"cloudflare_challenge","website_url":"<website_url>","proxy":"<proxy>"}'

How to recognize Cloudflare challenge page

A Cloudflare challenge page blocks the destination before it loads and is different from an embedded Turnstile widget.

What makes Cloudflare challenge page different

The result is cookie data such as a clearance credential. Turnstile returns a form token and uses a site key instead.

Where the Cloudflare challenge page parameters come from

Use the blocked URL and the same proxy exit and user agent that will consume the returned clearance cookie.

website_urlRequired
The exact page where this challenge appears, including the relevant path rather than only the site home page.
proxyRequired
The proxy for the solve session; when a result is network-bound, use the same exit for the subsequent target request.
user_agentOptional
The browser user agent for this challenge session; keep it consistent when the returned result is bound to that session.

What the API returns

The Cloudflare challenge page API returns cookie values in cookie. Its solution format is cookie. Attach the returned cookie fields to subsequent requests for the same workflow.

Solution shape
cookie
Solution fields
cookie

How to use the Cloudflare challenge page API

  1. 01Read GET /api/v1/captcha/types and select the cloudflare_challenge entry.
  2. 02Send type: "cloudflare_challenge" and the required parameters to POST /api/v1/captcha.
  3. 03Read cookie values from cookie.
  4. 04Attach the returned cookie fields to subsequent requests for the same workflow.

Billing and availability

EverySolve charges only when a solution is delivered successfully. Unsuccessful attempts are refunded automatically. Read available and the price fields from GET /api/v1/captcha/types at request time rather than treating them as static page content.

Cloudflare challenge page integration questions

How can I identify Cloudflare challenge page before choosing a type?

A Cloudflare challenge page blocks the destination before it loads and is different from an embedded Turnstile widget. Use cloudflare_challenge only after those signals match the target challenge.

Which target-page values belong in a Cloudflare challenge page request?

Use the blocked URL and the same proxy exit and user agent that will consume the returned clearance cookie. Provide website_url and proxy. Optional parameters are user_agent.

What does Cloudflare challenge page return, and what should not be confused with it?

The Cloudflare challenge page API returns cookie values in cookie. Its solution format is cookie. The result is cookie data such as a clearance credential. Turnstile returns a form token and uses a site key instead.

Which external source explains the Cloudflare challenge page integration?

Cloudflare documents challenge passage and the cookies used by its challenge platform. [Open the Cloudflare challenge page reference](https://developers.cloudflare.com/waf/tools/challenge-passage/). EverySolve-specific fields and live availability still come from the type catalog.