CaptchaSolvCaptchaSolv
Captcha Types

DataDome

Bypass DataDome protection and obtain a valid datadome cookie.

DataDome blocks a request with a 403 whose body carries a var dd = {...} configuration. That configuration is the challenge context: pass it to the solver and you get back a valid datadome cookie to send with your own requests.

Type stringWhen to use
DataDomeSliderSlider challenge — block config has "rt":"c"
DataDomeInterstitialInterstitial / device check — block config has "rt":"i"
DataDomeTagsPre-emptive cookie from the site's tags.js, with no block page

Choosing the type

The rt field in the block configuration tells you which challenge was served:

{
  "rt":   "c",
  "cid":  "AHrlqAAAAAMA...",
  "hsh":  "8C7191D8AA1BF5FBB1B84DC7268196",
  "t":    "fe",
  "s":    55733,
  "e":    "5a71185ef370c8f5...",
  "host": "geo.captcha-delivery.com",
  "cookie": "fEO5_X1DSvJ1ARlf..."
}
  • "rt":"c" → DataDomeSlider
  • "rt":"i" → DataDomeInterstitial
  • "t":"bv" → your IP is banned. No challenge can be solved from it; rotate the proxy. The solver rejects these tasks rather than consuming a solve.

Data fields

FieldRequiredDescription
configYesThe whole var dd = {...} object from the block response, as JSON. Harvest it immediately before submitting — it is per-session and single-use.
captcha_urlNoA pre-extracted geo.captcha-delivery.com challenge URL, when your flow obtains one directly instead of from a block page.
api_pathNoUsed with captcha_url: the endpoint path your flow calls to receive the challenge URL. Defaults to /api.
tags_urlNo(DataDomeTags only) The site's tags.js URL. DataDome serves it first-party per customer, e.g. https://dd.example.com/tags.js. Defaults to https://js.datadome.co/tags.js.

For DataDomeTags, pass the site's DataDome key as site_key.

Solution fields

FieldDescription
solution.tokenThe datadome cookie value. Send it as Cookie: datadome=<value>.
solution.userAgentThe user-agent used during solving. You must reuse it — see below.

Example

Request
{
  "api_key":  "YOUR_API_KEY",
  "type":     "DataDomeSlider",
  "site_url": "https://example.com/",
  "proxy":    "user:pass@host:port",
  "data": {
    "config": "{\"rt\":\"c\",\"cid\":\"AHrlqAAAAAMA...\",\"hsh\":\"8C7191D8...\",\"t\":\"fe\",\"s\":55733,\"e\":\"5a71185e...\",\"host\":\"geo.captcha-delivery.com\",\"cookie\":\"fEO5_X1D...\"}"
  }
}
Response
{
  "errorId":  0,
  "status":   "ready",
  "solvtime": 6.3,
  "data": {
    "useragent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 ...",
    "language":  "en-US,en;q=0.9",
    "solution": {
      "token": "0lgJ5AtwCr2XGYxA3aKHSJtjGkuEwnKTlu9QJWRksqsXq1JETRjRH7GL7CVo..."
    }
  }
}

Set the returned value as the datadome cookie on your subsequent requests:

Cookie: datadome=<solution.token>

The cookie is bound to the user-agent it was minted under. Sending it with a different user-agent gets the request challenged again, even though the cookie is valid. Always replay with the userAgent from the solution.

Your HTTP client also has to present a realistic TLS fingerprint. DataDome scores the cookie together with the transport, so a default requests / urllib client is challenged regardless of the cookie. Use a client that can match a real client's TLS signature, for example curl_cffi.

How to identify DataDome

  • A datadome cookie on the response, or an x-datadome / x-dd-b response header.
  • A 403 whose body contains var dd = {...} and a script from captcha-delivery.com.
  • Requests to geo.captcha-delivery.com or ct.captcha-delivery.com.
  • A first-party tags.js on the site, e.g. dd.example.com/tags.js.

Tips

  • Harvest the config last. It is single-use and short-lived: build the rest of your request first, then fetch the block response and submit immediately.
  • Match the proxy. Mint and replay through the same exit IP — DataDome weighs IP reputation heavily.
  • Reuse the returned userAgent. The cookie is bound to it.
  • Check for t":"bv" before solving. That value means the IP is banned, and no solve will help until you rotate it.

On this page