Skip to content

DataDome overview

Read this before any DataDome guide. Most rejected cookies come from the session, not the payload.

  • We return payloads, not cookies. You submit the payload from your session and DataDome sets the datadome cookie.
  • Synchronous. A solve takes about 50–100 ms.
  • Chrome on Windows only. Your client must match. See Match a real browser.
  • Kept up to date. When DataDome changes, we update the solver. You do not need to do anything.

Base URL: https://dd.antibotapi.com. Only sites approved for your account are accepted; request one from the dashboard.

You see Challenge Guide
A 403 whose page loads ct.captcha-delivery.com/i.js “Verifying your device” Interstitial
A 403 whose page loads ct.captcha-delivery.com/c.js Slider or audio Slider CAPTCHA
No block page, but blocks later in the flow Device signals Tags

Move through the site the way a user would: homepage, then product page, then add to cart. Never send a request the UI could not have made. Each request’s referer is the page before it.

Chrome sends three client hints on every HTTPS request, and your client must too:

  • sec-ch-ua, the brand list, such as "Not/A)Brand";v="8", "Chromium";v="126", "Google Chrome";v="126"
  • sec-ch-ua-mobile: ?0
  • sec-ch-ua-platform: "Windows"

When a response has an Accept-CH header, the site wants more hints on later requests to that origin:

Accept-CH: Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Model

Send every hint it names from then on. Our solve responses include a headers map with these values; send them as given and keep them the same for the whole session. Every hint must agree with your User-Agent: same Chrome version, "Windows" as the platform.

The t value in the block’s dd object is bv both for a banned proxy and for a session that has not solved tags yet. Solve tags before rotating proxies. If t=bv stays after tags, or the CAPTCHA page contains Hard Block, the proxy is banned.

If you keep getting blocked after solving, clear every DataDome cookie, request the page again for a fresh block, and solve from the start. An invalidated cookie keeps you in the loop.