Please enable JS and disable any ad blocker
``` {% endcode %} {% hint style="warning" %} If in the response, `t` is set to `bv`, it means your proxy is hard blocked, solving the challenge will not have any effect. {% endhint %} This is almost the same response you would receive with a Interstitial challenge, however the reference to this URL: `https://ct.captcha-delivery.com/c.js` is unique to slider. ### 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: {% tabs %} {% tab title="Golang" %} {% code overflow="wrap" %} ```go // 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.ParseSliderDeviceCheckLink(reader, datadomeCookie, referer) if err != nil { // Handle the error } // deviceLink will look like: https://geo.captcha-delivery.com/captcha/?... ``` {% endcode %} {% endtab %} {% tab title="Python" %} {% code overflow="wrap" %} ```python from hyper_sdk.datadome import parse_slider_device_check_link device_link = parse_slider_device_check_link(html_content, datadome_cookie, referer) # device_link will look like: https://geo.captcha-delivery.com/captcha/?... ``` {% endcode %} {% endtab %} {% tab title="JS / TS" %} {% code overflow="wrap" %} ```javascript import {parseSliderDeviceCheckUrl, generateSliderPayload} from "hyper-sdk-js/datadome/slider.js"; const result = parseSliderDeviceCheckUrl( "", // Block page body "", // Value of `datadome` cookie "" // Referer, e.g. URL you are trying to access ); if (result.isIpBanned) { // IP address is banned. // Note: result.url is null if this is true. return; } ``` {% endcode %} {% endtab %} {% endtabs %} 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`, `t`, `s`, `e`.\ \ 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: {% code overflow="wrap" %} ``` https://geo.captcha-delivery.com/captcha/?initialCid={cid}&hash={hsh}&cid={datadomeCookie}&t={t}&referer={referer}&s={s}&e={e}&dm=cd ``` {% endcode %} ### Fetching the slider 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: {% code overflow="wrap" %} ```html ``` {% endcode %} 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. {% hint style="info" %} `script` is optional. Integrations that do not send it keep working, sending it is simply the more reliable path. {% endhint %} Our SDKs tell you which of the two cases you are in: {% tabs %} {% tab title="Golang" %} {% code overflow="wrap" %} ```go // 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. } ``` {% endcode %} {% endtab %} {% tab title="Python" %} {% code overflow="wrap" %} ```python from hyper_sdk.datadome import parse_challenge_script_url script = "" script_url = parse_challenge_script_url(html) if script_url is not None: # GET script_url with the same client, read the response body into script ``` {% endcode %} {% endtab %} {% tab title="JS / TS" %} {% code overflow="wrap" %} ```javascript 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 } ``` {% endcode %} {% endtab %} {% endtabs %} ### Fetching the slider puzzle In order for the Hyper Solutions API to solve the slider challenge, it needs access to the images involved. The HTML/JavaScript that we have retrieved in the previous step contains data like this: {% code overflow="wrap" %} ```javascript captchaChallengeSeed: '17af5b20aafd238256f5a5d11cf475da', captchaChallengePath: 'https://dd.prod.captcha-delivery.com/image/2026-01-19/17af5b20aafd238256f5a5d11cf475da.jpg', ``` {% endcode %} #### Parsing the Image URLs You need to extract the `captchaChallengePath` value, which gives you the puzzle image URL directly. To get the piece image URL, simply replace `.jpg` with `.frag.png`. #### Finding the puzzle link (jpg) You can parse `captchaChallengePath` using this regex: ```regexp captchaChallengePath:\s*['"]([^'"]+\.jpg)['"] ``` Or if you already have the path extracted: ```regexp (https:\/\/dd\.prod\.captcha-delivery\.com\/image\/.*?\.jpg) ``` #### Deriving the piece link (frag.png) Once you have the puzzle URL, derive the piece URL by replacing the extension: ```javascript const pieceUrl = puzzleUrl.replace('.jpg', '.frag.png'); ``` For example: * **Puzzle URL:** `https://dd.prod.captcha-delivery.com/image/2026-01-19/17af5b20aafd238256f5a5d11cf475da.jpg` * **Piece URL:** `https://dd.prod.captcha-delivery.com/image/2026-01-19/17af5b20aafd238256f5a5d11cf475da.frag.png` ### Fetching the Images You need to make a GET request to both URLs and store both responses (base64 encoded): * The `.jpg` response should be stored as `puzzle` * The `.frag.png` response should be stored as `piece` ### 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](/api-reference/datadome.md).\ \ Alongside your usual session values (User-Agent, IP, Accept-Language, and the page URL as `parentUrl`), you need up to five challenge-specific values: * deviceLink: The link parsed in the previous sections. * html: The full response body of the GET request you made to the deviceLink URL. * script: The challenge bundle you fetched earlier. Optional, leave it empty when the page inlines the bundle. * puzzle: The base64-encoded bytes of the `.jpg` image. * piece: The base64-encoded bytes of the `.frag.png` image. You can then generate the payload with the SDK as follows: {% tabs %} {% tab title="Golang" %} {% code overflow="wrap" %} ```go checkUrl, headers, err := session.GenerateDataDomeSlider(ctx, &hyper.DataDomeSliderInput{ UserAgent: userAgent, DeviceLink: deviceLink, Html: string(html), Script: script, // empty when the page inlines the bundle Puzzle: base64Puzzle, // base64 of the .jpg Piece: base64Piece, // base64 of the .frag.png ParentUrl: pageUrl, AcceptLanguage: acceptLanguage, IP: ip, }) if err != nil { // Handle the error } // GET the checkUrl; replay the returned headers on subsequent requests ``` {% endcode %} {% endtab %} {% tab title="Python" %} {% code overflow="wrap" %} ```python result = hyper_session.generate_slider_payload(hyper_sdk.DataDomeSliderInput( user_agent=user_agent, device_link=device_link, html=html, script=script, # empty when the page inlines the bundle puzzle=base64_puzzle, piece=base64_piece, parent_url=page_url, accept_language=accept_language, ip=ip, )) # GET result["payload"] (the check URL); replay result["headers"] when applicable ``` {% endcode %} {% endtab %} {% tab title="JS / TS" %} {% code overflow="wrap" %} ```javascript const result = await generateSliderPayload(session, { userAgent: userAgent, deviceLink: deviceLink, html: deviceCheckBody, script: script, // undefined when the page inlines the bundle puzzle: base64Puzzle, // base64 of the .jpg piece: base64Piece, // base64 of the .frag.png parentUrl: pageUrl, acceptLanguage: acceptLanguage, ip: ip, }); // GET result.payload (the check URL); replay result.headers when applicable ``` {% endcode %} {% endtab %} {% endtabs %} ### Posting payload, solving challenge Our API returns a simple URL as the result of solving the slider challenge, all that is required is to make a GET request to this URL which looks as follows: ``` https://geo.captcha-delivery.com/captcha/check?cid=... ``` The response of this GET request will be as follows: {% code overflow="wrap" %} ```json { "cookie": "datadome=cookievalue; Max-Age=31536000; Domain=.example.com; Path=/; Secure; SameSite=Lax" } ``` {% endcode %} You can parse the JSON response, and update your cookieJar with the `"cookie"` you received from DataDome.\ \ You have now successfully solved DataDome's slider challenge, retrying the request that served this block should not give you a challenge anymore.