DataDome Interstitial

This page explains the flow of solving the interstitial challenge of DataDome.

If you already familiar with solving DataDome challenges, you can either install one of our SDKs for easy integration, or head over to our API Reference if you want to handle the implementation yourself. The DataDome Bypass API overview covers which challenges the endpoints solve and how they are priced.

Interstitial

This challenge is served using a 403 status code and a response body that looks as follows:

<html>
   <head>
      <title>example.com</title>
      <style>#cmsg{animation: A 1.5s;}@keyframes A{0%{opacity:0;}99%{opacity:0;}100%{opacity:1;}}</style>
   </head>
   <body style="margin:0">
      <p id="cmsg">Please enable JS and disable any ad blocker</p>
      <script data-cfasync="false">var dd={'rt':'i','cid':'AHrlqAAAAAMACAOLE2sBBRMATaDxmw==','hsh':'13C44BAB3C9D728ABD66E2A9F0233C','b':1501854,'s':48047,'host':'geo.captcha-delivery.com'}</script><script data-cfasync="false" src="https://ct.captcha-delivery.com/i.js"></script>
   </body>
</html>

This is almost the same response you would receive with a Slider challenge, however the reference to this URL: https://ct.captcha-delivery.com/i.js is unique to interstitial.

Parsing the HTML

Before we explain how you can manually parse the required values from the HTML posted above, first are shown code snippets of how it can be done easily with our SDKs:

Golang

// reader is an `io.Reader` which holds the response body of the HTML.

// datadomeCookie is the cookie value of the cookie with name "datadome",
// this cookie is set by the 403 block page.

// referer is the URL that served the 403 block page.

deviceLink, err := datadome.ParseInterstitialDeviceCheckLink(reader, datadomeCookie, referer)
if err != nil {
// Handle the error
}
// deviceLink will look like: https://geo.captcha-delivery.com/interstitial/?...

Python

from hyper_sdk.datadome import parse_interstitial_device_check_link

device_link = parse_interstitial_device_check_link(html_content, datadome_cookie, referer)
# device_link will look like: https://geo.captcha-delivery.com/interstitial/?...

JS/TS

import parseInterstitialDeviceCheckUrl from "hyper-sdk-js/datadome/interstitial.js";

const deviceCheckUrl = parseInterstitialDeviceCheckUrl(
    "", // Block page body
    "", // Value of `datadome` cookie
    "" // Referer, e.g. URL you are trying to access
);
if (deviceCheckUrl === null) {
    // deviceCheckUrl will be null if parseInterstitialDeviceCheckUrl failed to parse it.
}

If you would rather parse the response yourself, you will need to extract the following fields from the dd object that can be found in the response body: cid, hsh, s, b. You also need to store the URL that received the block, it is used as the referer, and the datadome cookie that is set on this blocked request. You can now build the URL as follows:

https://geo.captcha-delivery.com/interstitial/?initialCid={cid}&hash={hsh}&cid={datadomeCookie}&referer={referer}&s={s}&b={b}&dm=cd

We will call this URL the deviceLink from now on.

Fetching the interstitial script

After having parsed the deviceLink in the previous step, you need to make a GET request to it. Make sure that you are sending the same headers and in the same order as your browser. Read and save the response body of this request as we need it to submit to the Hyper Solutions API.

Fetching the challenge bundle

Most of the time the challenge bundle is inlined in the response body you just saved. Sometimes DataDome leaves it out of the page and loads it from its own file instead, with a tag like this:

<script defer src="https://ct.captcha-delivery.com/interstitial.1.33.0.202609141.js"></script>

DataDome picks between the two per request, so check this on every challenge instead of deciding it once. When the page loads the bundle from its own file, make a GET request to that URL yourself, using the same client, proxy and headers you used for the deviceLink, and save the response body. You submit it to the Hyper Solutions API as script. When the bundle is inlined, you leave script empty.

script is optional. Integrations that do not send it keep working, sending it is simply the more reliable path.

Our SDKs tell you which of the two cases you are in:

Golang

// html is the response body of the GET request to the deviceLink.

var script string
if scriptUrl, ok := datadome.ParseChallengeScriptURL(html); ok {
    // GET scriptUrl with the same client, read the response body into script.
}

Python

from hyper_sdk.datadome import parse_challenge_script_url

script = ""
script_url = parse_challenge_script_url(html_content)
if script_url is not None:
    # GET script_url with the same client, read the response body into script

JS / TS

import {parseChallengeScriptUrl} from "hyper-sdk-js/datadome/script.js";

let script;
const scriptUrl = parseChallengeScriptUrl(deviceCheckBody);
if (scriptUrl !== null) {
    // GET scriptUrl with the same client, read the response body into script
}

Fetching the payload from API

Again we have handy SDK functions to help you with these API calls, if you want to implement the API calls yourself, head over to the API Reference. Alongside your usual session values (User-Agent, IP, Accept-Language), you need up to three challenge-specific values:

• deviceLink: The link parsed in one of the previous sections.

• html: The full response body of the GET request you made to the deviceLink URL.

• script: The challenge bundle you fetched in the previous section. Optional, leave it empty when the page inlines the bundle.

You can then generate the payload with the SDK as follows:

Golang

payload, headers, err := session.GenerateDataDomeInterstitial(ctx, &hyper.DataDomeInterstitialInput{
    UserAgent:      userAgent,
    DeviceLink:     deviceLink,
    Html:           string(html),
    Script:         script,         // empty when the page inlines the bundle
    AcceptLanguage: acceptLanguage,
    IP:             ip,
})
if err != nil {
    // Handle the error
}
// POST the payload; replay the returned headers on subsequent requests

Python

result = hyper_session.generate_interstitial_payload(hyper_sdk.DataDomeInterstitialInput(
    user_agent=user_agent,
    device_link=device_check_link,
    html=html_content,
    script=script,  # empty when the page inlines the bundle
    accept_language=accept_language,
    ip=ip,
))
# POST result["payload"] to https://geo.captcha-delivery.com/interstitial/
# Replay result["headers"] on subsequent requests when required

JS / TS

const result = await generateInterstitialPayload(session, {
    userAgent: userAgent,
    deviceLink: deviceCheckUrl,
    html: deviceCheckBody,
    script: script, // undefined when the page inlines the bundle
    ip: ip,
    acceptLanguage: acceptLanguage,
});
// POST result.payload to https://geo.captcha-delivery.com/interstitial/
// Replay result.headers on subsequent requests when required

Posting payload, solving challenge

The payload returned by the HyperSolutions API in the previous step is an already concatenated Form Data string, you can POST this to the following URL:

https://geo.captcha-delivery.com/interstitial/

And make sure you are matching the headers in the order that your browser used. The response of this POST request will be as follows:

{
	"cookie": "datadome=cookievalue; Max-Age=31536000; Domain=.example.com; Path=/; Secure; SameSite=Lax",
	"view": "redirect",
	"url": "https://www.example.com/path"
}

You can parse the JSON response, and update your cookieJar with the "cookie" you received from DataDome. You have now successfully solved DataDome's interstitial challenge, retrying the request that served this block should not give you a challenge anymore.