Skip to Content
AnySolver logo
AnySolver
Cookie

DataDomeInterstitialCookie

Clear the DataDome interstitial device check through your proxy and get the cleared datadome cookie, with no puzzle involved.

DataDomeInterstitialCookie clears the DataDome interstitial through your proxy and returns the cleared datadome cookie. The interstitial is DataDome's device check: a page that runs JavaScript in the browser and, when the check passes, clears itself without showing a puzzle.

Use this task when you capture the challenge page yourself and want the solve to run through your proxy. If you do not send a proxy, use DataDomeInterstitialCookieProxyLess.

Which DataDome task do I need?

The task depends on the challenge DataDome returned.

What you seeTask
An /interstitial/ challenge URL, 'rt':'i' and i.jsDataDomeInterstitialCookie (this task), or DataDomeInterstitialCookieProxyLess without a proxy
A /captcha/ challenge URL, 'rt':'c' and c.jsDataDomeSliderCookie, or DataDomeSliderCookieProxyLess without a proxy
The site loads the DataDome JS Tag (tags.js) and you need its datadome cookieDataDomeTagsCookie

Recognise an interstitial block

Like the slider, the interstitial arrives as a 403 with a dd object in the HTML. Two markers separate it from the slider:

  • dd contains 'rt':'i'
  • the page loads https://ct.captcha-delivery.com/i.js (note the i.js)

JSON and XHR endpoints return the challenge inline as { "url": "https://geo.captcha-delivery.com/interstitial/?..." } instead of the HTML page. An /interstitial/ path means this task; /captcha/ means the slider.

DataDome can answer the device check with a slider instead of a cleared session. If the next challenge URL has a /captcha/ path, use DataDomeSliderCookie for it.

Build captchaUrl

captchaUrl is the full geo.captcha-delivery.com/interstitial/ URL, not the i.js script URL. Use the URL returned by a JSON response or challenge iframe when one is present. Otherwise parse var dd from the blocked HTML and construct it. The current datadome cookie becomes cid, and the full blocked websiteURL becomes referer.

This helper parses the normal DataDome block and builds the URL with proper percent-encoding:

function buildInterstitialUrl(html, datadomeCookie, websiteURL) {
    const source = html.match(/var dd\s*=\s*({[\s\S]*?})\s*;?\s*<\/script>/)?.[1];
    if (!source) throw new Error('DataDome var dd object not found');

    const dd = JSON.parse(source.replaceAll("'", '"'));
    const params = new URLSearchParams({
        initialCid: dd.cid,
        hash: dd.hsh,
        cid: datadomeCookie,
        referer: websiteURL,
        s: dd.s,
        e: dd.e,
        b: dd.b,
        dm: 'cd',
    });
    return `https://geo.captcha-delivery.com/interstitial/?${params}`;
}

GET that exact URL with the same proxy, cookies, User-Agent and browser-like headers used for websiteURL. Base64-encode the raw response bytes without changing the body and send them as challengePage:

const captchaUrl = buildInterstitialUrl(blockedHtml, datadomeCookie, websiteURL);
const challengeResponse = await httpClient.get(captchaUrl);
const challengePage = Buffer.from(challengeResponse.body).toString('base64');

The interstitial URL carries b and has no t, which is the quickest way to tell the two challenge URLs apart once built.

  • task.proxy is required on this task type. Providers that use it solve from that address; some providers solve from the captured session and ignore it.
  • The proxy must keep one IP for the whole solve. See Keep the same IP for the whole solve.
  • Put the blocked response's datadome value in the cid parameter of captchaUrl and in initCookies.datadome. Some providers read it from the URL and others from the cookie jar, so send both.
  • Send the same userAgent for the blocked request, the challengePage fetch, the task and the cookie replay. The datadome cookie is tied to the session behind cid, so a different IP or User-Agent invalidates it. Providers accept different User-Agent lists: if a task is rejected for its User-Agent, check the provider's documentation.
  • Match your TLS fingerprint and header order to a real browser. A valid cookie on a mismatched client can still get a 403.

Set solution.datadome as the datadome cookie on the protected domain and retry the blocked request through the same proxy with the same User-Agent. Some providers return the whole Set-Cookie line (datadome=…; Max-Age=…) instead of the value alone: take the value after datadome=. If the cookie is rejected, check that the proxy kept one IP for the whole solve, then that captchaUrl and websiteURL come from the request that was blocked.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
CapSolver
$2.50
2Captcha
$1.45
CapMonster
$2.20
RiskBypass
$2.00
Salamoonder
$2.76
Solverify
$0.60
VoidCaptcha
$2.00

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

Per-request settings for routing, Auto Retry, Auto Fallback, proxy reuse, response statistics and detailed analytics. Each field overrides the API key's value. See Routing modes.

View settings reference

Task Object Properties

The task field accepts an object with the following properties:

FieldTypeRequiredDescription
type*
Yes
websiteURL*
URLYes

Full URL of the protected page that returned the DataDome block. Use this exact URL as the referer value when constructing captchaUrl.

Example: https://www.pokemoncenter.com/

challengePage*
stringYes

Base64-encoded raw response body from a GET to captchaUrl using the same User-Agent, cookies, proxy and browser-like request identity as the blocked session.

Example: PCFET0NUWVBFIGh0bWw+...

userAgent*
stringYes

User-Agent used to request the protected page and captchaUrl, then replay the solved cookie. Keep it identical across the full flow. Providers accept different User-Agent lists (some accept only desktop Chrome or Firefox), so check the provider docs if a task is rejected for its User-Agent.

Example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36

initCookies*
objectYes

Cookies from the blocked response, as a name → value map. datadome is required.

Example: {"datadome":"noJuZstmvINksqOxaXWQogbPBd01y3VaH3r..."}

proxy*
string | objectYes

Proxy the provider solves through, as a string or an object. See Proxy configuration.

View proxy configuration

Example: http://user:pass@1.2.3.4:8080

captchaUrl*
URLYes

Full geo.captcha-delivery.com/interstitial/ challenge URL. Use the URL returned by a JSON response or challenge iframe when available; otherwise construct it from the blocked page var dd, with the current datadome cookie as cid and websiteURL as referer. It carries b and has no t parameter.

Example: https://geo.captcha-delivery.com/interstitial/?initialCid=AHrlqAAAAAMACAOLE2sBBRMATaDxmw%3D%3D&hash=13C44BAB3C9D728ABD66E2A9F0233C&cid=noJuZstmvINksqOxaXWQogbPBd01y3VaH3r-CZ4eqK4roZuelJMHVhO2rR0IySRieoAivkg74B4UpJ.xj.jVNB6-aLaW.Bwvik7__EncryD6COavwx8RmOqgZ7DK_3v&referer=https%3A%2F%2Fwww.pokemoncenter.com%2F&s=48047&e=3&b=1501854&dm=cd

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "DataDomeInterstitialCookie",
        "websiteURL": "https://www.pokemoncenter.com/",
        "challengePage": "PCFET0NUWVBFIGh0bWw+...",
        "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36",
        "initCookies": {
            "datadome": "noJuZstmvINksqOxaXWQogbPBd01y3VaH3r..."
        },
        "proxy": "http://user:pass@1.2.3.4:8080",
        "captchaUrl": "https://geo.captcha-delivery.com/interstitial/?initialCid=AHrlqAAAAAMACAOLE2sBBRMATaDxmw%3D%3D&hash=13C44BAB3C9D728ABD66E2A9F0233C&cid=noJuZstmvINksqOxaXWQogbPBd01y3VaH3r-CZ4eqK4roZuelJMHVhO2rR0IySRieoAivkg74B4UpJ.xj.jVNB6-aLaW.Bwvik7__EncryD6COavwx8RmOqgZ7DK_3v&referer=https%3A%2F%2Fwww.pokemoncenter.com%2F&s=48047&e=3&b=1501854&dm=cd"
    }
}

Optional fields are not guaranteed across providers

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
datadome*
stringYes

The solved datadome cookie value. Some providers return the whole Set-Cookie line (datadome=…; Max-Age=…) instead: take the value after datadome=. Set it as the datadome cookie on the protected domain and retry the blocked request.

Example: 4ZXwCBlyHx9ktZhSnycMF...

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.

userAgent
stringNo

User-Agent string used during solving.

Example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36