Our solution automates solving challenges like sliding captchas and interstitial device checks, allowing seamless access to Datadome-protected websites.
How the Solution Works
To bypass Datadome’s protection, follow these steps:
Load the Challenge Page
Generate the Challenge Payload (using our API)
Post the Payload to retrieve the Datadome cookie.
In order to access any of our endpoint you'll need a valid API Key, either join our discord for a trial or puchase a plan
Build the challenge URL
post
Some websites redirect you to the challenge page directly, while others provide a dd dictionary in the response.
In such cases, you need to build the challenge URL manually.
Our /build endpoint simplifies this by constructing the URL for you.
Authorizations
x-api-keystringRequired
Body
htmlstringOptional
The HTML response content
datadomestringOptional
Your session's datadome cookie value
referrerstringOptional
The requested URL
Responses
200
OK
application/json
400
Bad Request
application/json
401
Unauthorized
application/json
500
Internal Server Error
application/json
post
/build
Solve the challenge
post
After loading the challenge page, our /solve endpoint generates the required payload to post and obtain the Datadome cookie.
After loading a challenge url, you'll just need to pass the response text to our api to get the challenge
solved, no matter the type of it.
The API will return you the needed payload for the cookie generating request.
Authorizations
x-api-keystringRequired
Header parameters
User-AgentstringOptional
The user-agent string of your browser or client. We highly suggest to pass it.
Sec-Ch-UastringOptional
Optional client hints header used by browsers for content negotiation.
Accept-LanguagestringOptional
The Accept-Language header indicating the user's preferred languages. We highly suggest to pass it.
Body
htmlstringOptional
The HTML of the challenge page
Responses
200
OK
application/json
400
Bad Request
application/json
401
Unauthorized
application/json
500
Internal Server Error
application/json
post
/solve
Important Notices
Payload generation is fast, typically 0.5 to 2.5 seconds.
Cookie retrieval: While our API generates the payload, you must handle the post request and interactions with the website.
HTTP/2 & Headers: Ensure you use HTTP/2 and a valid set of headers, matching a real browser for successful navigation and payload posting.