When do I use this vs DataDomeSlider?

Use DataDomeInterstitial for the full-page 'device check' / 'Please wait…' screen (the geo.captcha-delivery.com/interstitial/ flow) — there's no puzzle, so we just run DataDome's JS and collect the cookie. Use DataDomeSlider when you get the draggable slider/click puzzle. Both return the datadome cookie.

How do I make it more reliable?

Pass your existing session cookies (the datadome cookie set when you were first blocked) in the cookies array. DataDome scores a returning visitor much higher than a cold session, so continuity raises the pass rate.

Before you submit — these must be correct

If any of these are wrong, your token may be accepted by our solver but rejected or scored poorly by the target site.

The datadome cookie is IP-bound. Reuse the same proxy for the solve and for subsequent requests.
Pass any session cookies you already have from the blocked page (the datadome cookie DataDome set when it first scored you) to skip the warm-up and raise success rate.

DataDome Interstitial

DataDomeInterstitial

proxy required

DataDome Interstitial Solver, solved in 5.0s.

Clear DataDome's full-page 'device check' / 'Please wait…' interstitial (no puzzle). Returns the datadome cookie. Routed for you by default.

Get API Key Try Demo Examples

Avg Speed~5.0s

Success99%+

Cost / 1k$2.00

Throughput12/m

The DataDome interstitial is the full-page device-check that appears instead of a slider — a 'Please wait…' / verification screen served from geo.captcha-delivery.com/interstitial/. There's no puzzle to drag: DataDome runs a proof-of-work and fingerprint check in the page and, if it passes, issues the datadome cookie.

Quick Integration

solve.py

import requests, time

API = "https://api.capzy.ai"
KEY = "capzy_your_key_here"

# Step 1: Create task
task = requests.post(f"{API}/createTask", json={
    "clientKey": KEY,
    "task": {
        "type": "DataDomeInterstitial",
        "websiteURL": "https://example.com/blocked",
        "proxyType": "http",
        "proxyAddress": "123.45.67.89",
        "proxyPort": "8080",
        "proxyLogin": "user",
        "proxyPassword": "pass"
    }
}).json()

task_id = task["taskId"]
print(f"Task created: {task_id}")

# Step 2: Poll for result
while True:
    result = requests.post(f"{API}/getTaskResult", json={
        "clientKey": KEY,
        "taskId": task_id
    }).json()

    if result["status"] == "ready":
        print("Solved!", result["solution"])
        break
    elif result["status"] == "failed":
        print("Failed:", result.get("errorDescription"))
        break

    time.sleep(1)

Using the result

use_result.py

# Step 3: Use the result — drop-in Cookie: header replay
sol = result["solution"]
headers = {
    "Cookie": sol["cookie"],
    "User-Agent": sol.get("userAgent", ""),
}
# IMPORTANT: route through the SAME proxy you supplied at solve time
resp = requests.get("https://target.example.com/", headers=headers, proxies={
    "http":  "http://USER:PASS@PROXY_HOST:PORT",
    "https": "http://USER:PASS@PROXY_HOST:PORT",
})
print(resp.status_code, len(resp.text), "bytes")

1. Send Payload

Dispatch your DataDomeInterstitial to our processing cluster via the secure API endpoint.

2. Solving Engine

We load the interstitial in a real browser, let DataDome's own JavaScript run its device check (no user interaction needed), and collect the datadome cookie it issues — often a silent pass. It's typically faster and cheaper than the slider path. The cookie is IP-bound, so it's routed through a high-reputation IP for you (or supply your own proxy).

3. Get Result

Poll getTaskResult for the validated token, then finalize your automated request.

Task Parameters

API Spec

Proxy fields below are required for this captcha — userAgent must match the one you’ll use when submitting the resulting token.

fieldtyperequireddescription

typetypestringreqyesDataDomeInterstitial

websiteURLtypestringreqnoThe protected page URL, used to warm up DataDome's session scoring before the interstitial

captchaUrltypestringreqnoThe interstitial URL captured from the iframe (geo.captcha-delivery.com/interstitial/...). Provide this OR websiteURL.

cookiestypearrayreqnoOptional session cookies to inject before solving — e.g. the existing datadome cookie from your blocked session. Format: [{name, value, domain?, path?}]. Recommended for continuity.

proxyTypetypestringreqyesProxy protocol: http, https, socks4, or socks5

proxyAddresstypestringreqyesProxy IP address or hostname

proxyPorttypenumberreqyesProxy port number

proxyLogintypestringreqnoProxy username (if auth required)

proxyPasswordtypestringreqnoProxy password (if auth required)

userAgenttypestringreqnoUser-Agent string to use. Must match the UA you use when submitting the token

Response Shape

fieldtypedescription

cookietypestringThe datadome cookie value — set it on your domain to pass DataDome on subsequent requests from the same IP

tokentypestringAlias of cookie (same value)

Example response

{
  "errorId": 0,
  "status": "ready",
  "solution": {
    "cookie": "datadome=<long opaque datadome cookie value, IP-bound>",
    "token": "datadome=<same value>"
  }
}

Error response

{
  "errorId": 1,
  "errorCode": "ERROR_CAPTCHA_UNSOLVABLE",
  "errorDescription": "Solver gave up."
}

Features

Clears the device-check interstitial with no puzzle solving

Often a silent pass — faster and cheaper than the slider

Returns the datadome cookie for replay

Routed for you by default; bring your own proxy if you prefer

Pricing & Stats

Per 1,000 solves$2.00

Avg solve time~5.0s

Success rate99%+