Cloudflare solver API

Get a cf_clearance cookie without running a browser. notabot solves Cloudflare JavaScript Detections over plain HTTPS and charges only for solves that work.

Price
from €1.00 per 1,000 solves€2.50 before level discounts
Live today
JavaScript Detections (JSD)
Coming next
Turnstile, managed challenge
Failed solves
Free
Commitment
None. Credits never expire

Cloudflare’s bot checks, one by one

They are separate products and a solver for one does not clear the others.

JavaScript Detections

  • A background script on HTML pages. A visitor that passes gets cf_clearance. Send the URL and your proxy, get the cookie back.
  • Cloudflare JSD solver
from €1.00€2.50 before level discounts

Turnstile

  • The widget that replaces a CAPTCHA on forms and returns a token for the site to verify.soon
from €1.00€2.50 before level discounts

Managed challenge

  • The “Just a moment” page a WAF rule puts in front of the content, cleared with cf_clearance.soon
from €1.20€3.00 before level discounts

Which one are you facing?

What you seeProductUse
The page loads, and requests without cf_clearance are blockedJavaScript Detectionscloudflare.jsd
A checkbox-style widget on a formTurnstileNot live yet
A “Just a moment” page before the contentManaged challengeNot live yet

Send the wrong type and the solver refuses instead of guessing, and you are not charged.

How Cloudflare’s JavaScript Detections decide

JavaScript Detections are the quiet check. Cloudflare injects a small script into HTML page views, the browser runs it, and the outcome is stored in a cf_clearance cookie. On its own that changes nothing. The site owner has to write a firewall rule that blocks or challenges requests whose detection did not pass, and they usually apply it to the pages and endpoints worth protecting rather than to the whole site.

Two consequences follow. The block often appears on a later request rather than the first one, because a new visitor has no result yet and owners are told not to enforce the rule on the first page. And the clearance does not last all day: Cloudflare gives the detection a 15-minute lifespan and re-injects the script before it runs out, so a long job should expect to solve again when the site starts challenging.

Source: Cloudflare, JavaScript Detections. More detail on the Cloudflare JSD solver page.

Before your first Cloudflare solve

  1. Create a key. Login with Discord and copy an API key from the dashboard.
  2. Get the site approved. Request the domain on the Sites page. Each domain is reviewed once, usually within a day.
  3. Choose the proxy you will keep using. The clearance is tied to the IP that earned it, so pass a sticky residential or mobile proxy and send your own requests through the same one.
  4. Solve against an HTML page, not an API endpoint. Cloudflare only injects the script into page views.
  5. Send the cookies with the returned user agent from a client with a Chrome TLS fingerprint.

Using the cookies afterwards

The cookies work with the user agent they came with, from the IP that earned them, on a client that looks like that browser.

  1. Send every cookie in the result, and keep whatever the site sets afterwards. Some sites rotate them.
  2. Copy the returned user agent into your user-agent header exactly.
  3. Stay on the same proxy. If the exit IP changes, the cookies stop working. Use a sticky session.
  4. Connect like Chrome. Stock Node, Python and Go clients handshake differently from Chrome, and a site can drop good cookies that arrive that way. Use curl-impersonate, httpcloak, tls-client or a real browser for your own requests.
  5. Reuse the result until it stops working. The site decides how long cookies last. Solve again when challenges come back, not before every request.
LimitValueNote
Solve timeout30 secondsSet your own client timeout to 60 seconds so it outlasts ours
Typical solve time2 to 10 secondsMostly round trips through your proxy. Our own work is well under a second
Requests per second50 per key, 200 per accountOver it you get rate_limited with a retry-after header
Proxy formathttp://user:pass@host:portSOCKS is not supported. Residential or mobile IPs clear far more often than datacenter ones

Worked example in Node: Using the result. All limits: Limits.

When a solve fails

A failed solve is never charged. The response names the reason, and each one has a specific fix.

ReasonWhat it meansWhat to do
CHALLENGE_NOT_FOUNDThe page loaded but the protection script was not on it. The URL may not sit behind this solver's protection.Check the URL is an HTML page behind JavaScript Detections. Turnstile and the managed challenge are different products.
NOT_CHALLENGEDThe site did not challenge this IP, so there was nothing to solve. Fetch the page directly.Fetch the page directly. There was nothing to solve.
GATE_NOT_CLEAREDThe answer was valid but the site still held the session back. Nearly always a flagged IP. Retry on a fresh one.Retry on a fresh residential or mobile IP.
BLOCKEDThe site refused the request before any challenge was shown. Usually the IP.Change IP. Datacenter and already-flagged IPs cause most of these.
domain_not_allowedThe domain is not approved for your account yet.Request the site on the Sites page.

Every code and reason: error reference.

Cloudflare JSD pricing

€2.50 per 1,000 successful solves, and less as your lifetime top-ups grow. No subscription, credits never expire, and a solve that fails is not charged.

Cloudflare JSD, per 1,000 solves
Topped up in totalLevelYou pay
Under €100List price€2.50
From €100−20%€2.00
From €250−30%€1.75
From €500−40%€1.50
From €1,000−50%€1.25
From €2,500−55%€1.125
From €5,000−60%€1.00
  • Top up from €10 by card. The balance works for every solver.
  • A level counts everything you have ever topped up, and it never drops.
  • The price is reserved when you call and released if the solve fails.
  • Each key can carry its own daily, monthly or total spend limit.
Pricing calculator

An API call instead of a headless browser

notabot APIHeadless browser
What you runOne HTTPS requestA Chrome instance per session, plus the servers under it
When the protection updatesWe patch the solver. Your code is unchangedYou patch stealth plugins and redeploy
What you pay forSuccessful solves onlyCPU, memory and bandwidth, whether or not the page passes
Scaling upSend more requestsAdd more machines

Cloudflare solver: questions

Which Cloudflare protections can you solve?

JavaScript Detections (JSD) is live and returns a cf_clearance cookie. Turnstile and the managed challenge are next.

How do I tell which Cloudflare product a site uses?

If the page loads normally and a cf_clearance cookie appears after a background script runs, that is JavaScript Detections. A widget on a form that produces a token is Turnstile. A "Just a moment" page before the content is the managed challenge.

Do I need a browser?

No. The solve is one HTTPS call. For your own requests to the site, use a client with a Chrome TLS fingerprint.

Do I need my own proxies?

Yes. The clearance is tied to the IP that earned it, so pass the residential or mobile proxy you will send your own requests through.

What does it cost?

€2.50 per 1,000 successful solves at list price, down to €1.00 at the top discount level. No subscription, credits never expire, and failed solves are free.

What if the site serves a product you do not solve yet?

The solver refuses instead of guessing and returns solve_failed, which is not charged.

Other solvers

Page updated . Reference for every solver: documentation.

Try it on your own target.

Login, copy a key, send one request. If the solve fails, it costs you nothing.

Cloudflare solver API: cf_clearance, no browser | notabot