👉General Information
Ensure that you have read this guide carefully, as it contains information that will be useful to successfully solve Datadome
🧠 General Overview
Please read this guide thoroughly. It contains essential information for successfully solving Datadome challenges using our API.
💻 Platform Requirements
Our API is designed to emulate Chrome on Windows. Workflows from other browsers such as Firefox, Edge etc) are not supported.
⚙️ API Capabilities
Our API is designed for performance:
No execution of original Datadome JavaScript
Synchronous response — solves occur immediately (typically ~50ms)
Auto-updates to adapt to most Datadome changes
Highly scalable to handle large volumes of requests
Does not return cookies — you must submit the response as instructed in this guide to retrieve a valid cookie
🧩 Datadome-Specific Guidance
📊 Behavior-Based Detection
Datadome analyses user behavior and browsing patterns. To avoid blocks:
Always use TLS for all requests (Datadome and site endpoints)
Ensure all headers match those from a real Chrome browser, pay particular attention to:
refereroriginuser-agentsec-ch-ua(and related client hints)
🔁 Referer Logic
The referer must reflect the correct navigation flow. For example, if accessing Page B, the referer should be Page A — otherwise, you risk being blocked.
🧠 Client Hints and Accept-CH
Accept-CHWhen a response from the target site includes the Accept-CH header, Datadome is requesting additional client hints. You must:
Note the requested headers.
Include them in all subsequent requests to that origin.
Our API will provide the correct headers and values to include. Not including them will likely result in a block.
🔒 Header Order Matters
Header order is critical.
Record a valid session using Charles Proxy.
Replicate the exact header order in your application.
Do not use Proxyman, Fiddler, or similar tools — they do not preserve header order per RFC 7540.
This applies throughout your session — even after solving Datadome, incorrect headers in subsequent requests can lead to detection.
🛍️ Logical Request Flow
Ensure that your requests mirror realistic browser behavior:
Do not send requests that would be impossible via the UI (e.g., sending an Add-to-Cart request without visiting the product page).
Your session should follow natural navigation: homepage → product page → ATC, etc.
Datadome tracks request context and flow - unrealistic behavior leads to blocks.
🏷️ Datadome Tags (tags.js / ch / le)
Some high-security sites require solving Datadome Tags after passing a CAPTCHA or interstitial block.
Example Flow:
Request:
https://www.example.comBlocked with 403 Captcha
Solve CAPTCHA
Retry request → success (200)
Solve tags (
tags.js/ CH / LE)Request product page
Send ATC request
t=bv Explanation
t=bv ExplanationThe t=bv query parameter is often misunderstood. It can indicate a proxy ban, but could also be a false positive if you haven’t solved tags. Always solve tags before rotating proxies.
If the error persists after solving tags, your proxy is likely blocked.
Likewise you can search for the words Hard Block on the Datadome Captcha or Interstitial page to see if you are hard blocked. If you are hard blocked, then your proxy is likely banned.
🧹 Clean Sessions
If you're stuck in a block loop:
Clear all Datadome cookies
Restart your flow by making a new request to the target endpoint
Obtain a new block cookie and begin the solving process again
Reusing invalid cookies will keep you in a detection loop.
🔐 TLS and Header Order
📜 Header Recording & Reproduction
Use Charles Proxy to record real Chrome browsing sessions.
Replicate header order exactly
Pay special attention to
Referer— it must behave as a browser would
Avoid tools that don't honor proper HTTP/2 header ordering.
🌐 TLS Requirements
Datadome requires a high-quality TLS client. We recommend:
tls-client— a trusted open-source client optimized for Datadome scenarios.
Using substandard TLS clients or no TLS clients at all will lead to detection or blocks.
Last updated