notabotDocs

DataDome

DataDome protects a page with a device check and a datadome cookie bound to your IP. datadome fetches url through your proxy, clears the check, and hands back a trusted datadome cookie you ride on your own session.

Type: datadome · Price: €0.0030 per successful solve.

Interstitial or captcha — which do you have?

When DataDome blocks a request it returns one of two challenges. Look at the datadome block on the page (var dd={rt:'…'}) or the url DataDome hands back:

DataDome challenge types
FieldTypeDescription
Interstitialrt:"i"URL contains /interstitial/. An automatic device check, no human interaction. This is what datadome solves.
Slider / puzzle captchart:"c"URL contains /captcha/. An interactive drag-the-piece challenge DataDome shows when the IP or device is already flagged. datadome does not solve this — it comes back solve_failed (BLOCKED) (free). Rotate to a clean residential IP and you get the interstitial instead.

So a BLOCKED result is the signal that your exit was served the slider: the fix is a cleaner IP, not a different call. datadome clears the page interstitial only — it does not mint clearance for /api/ or XHR endpoints that return their own captcha JSON.

Request

POST /v1/solve
{
  "type": "datadome",
  "url": "https://shop.example.com/",
  "proxy": "http://user:pass@residential-host:port",
  "userAgent": "<optional: the UA you will reuse when you ride the cookie>"
}
datadome request fields
FieldTypeDescription
urlrequiredstringThe protected page URL. The site must be approved on your account.
proxystringYour residential proxy as http://user:pass@host:port. The datadome cookie binds to its IP, so reuse the same one afterwards.
userAgentstringThe UA you will reuse with the cookie. Defaults to a Chrome UA.

Fields not listed here are dropped.

Result

datadome result fields
FieldTypeDescription
datadomestringThe trusted datadome cookie value.
cookiesobjectThe session cookies to carry, datadome among them.
userAgentstringThe UA the clearance was issued for. Reuse it exactly.
statusnumberThe verified re-GET status (200 on a real pass).
200 OK
{
  "ok": true,
  "requestId": "req_Dd7a…",
  "result": {
    "datadome": "<the datadome cookie value>",
    "cookies": { "datadome": "…" },
    "userAgent": "Mozilla/5.0 (…) Chrome/156.0.0.0 Safari/537.36",
    "status": 200
  },
  "cost": 0.003,
  "costMicro": 3000,
  "solveMs": 900
}

Using it

  1. Set result.datadome (and the other result.cookies) on your session.
  2. Make your real requests from the same IP and User-Agent — the cookie is bound to both.

Notes

  • solve_failed (BLOCKED): a hard captcha — your IP is flagged. Rotate to a clean residential IP.
  • solve_failed (NOT_CHALLENGED): no DataDome interstitial on the page, or no clearance produced. Nothing to solve.
  • Every solve_failed is free.