DataDomeSliderCookieProxyLess
Solve the DataDome slider from a captured challenge page and get the cleared datadome cookie back. Shows the request schema, an example and provider prices.
DataDomeSliderCookieProxyLess solves the DataDome slider from a challenge page you captured and returns the cleared datadome cookie value to set on your session. This is the self-driven variant: you capture the challenge page and hand it over with the User-Agent you fetched it with, and the provider works out the puzzle answer and verifies it. You send no proxy.
To send your proxy with the task, use DataDomeSliderCookie.
Which DataDome task do I need?
The task depends on the challenge DataDome returned.
| What you see | Task |
|---|---|
A /captcha/ challenge URL, 'rt':'c' and c.js | DataDomeSliderCookieProxyLess (this task), or DataDomeSliderCookie with a proxy |
An /interstitial/ challenge URL, 'rt':'i' and i.js | DataDomeInterstitialCookieProxyLess, or DataDomeInterstitialCookie with a proxy |
The site loads the DataDome JS Tag (tags.js) and you need its datadome cookie | DataDomeTagsCookie |
Recognise a slider block
The block arrives as a 403 with a small HTML page containing a dd object where rt is 'c', and it loads https://ct.captcha-delivery.com/c.js. JSON and XHR endpoints skip the HTML and return { "url": "https://geo.captcha-delivery.com/captcha/?…" } inline. A /captcha/ path is the slider; /interstitial/ means the interstitial.
Build the request
Use the JSON url or challenge iframe src when available. Otherwise build captchaUrl from the var dd
object with URLSearchParams, the current datadome cookie as cid, the full websiteURL as referer, and
dm=cd.
GET captchaUrl with the same User-Agent you will pass to the task, and base64-encode the whole response body.
That is challengePage.
websiteURL.solution.datadome as the datadome cookie on the protected domain and retry the blocked request.cid, hsh, t, s and e come from the dd object on the block page; datadomeCookie is the datadome cookie set on the blocked response, and websiteURL is the URL you were blocked on. t must be fe; with t=bv, DataDome has banned the IP, so change the IP and trigger the block again:
const { cid, hsh, t, s, e } = dd;
const params = new URLSearchParams({
initialCid: cid,
hash: hsh,
cid: datadomeCookie,
t,
referer: websiteURL,
s,
e,
dm: 'cd',
});
const captchaUrl = `https://geo.captcha-delivery.com/captcha/?${params}`;t=bv means the IP is banned
The t parameter must be fe. With t=bv, DataDome has banned the IP and solving the challenge does not clear it.
Change the IP and trigger the block again.
Keep one IP and one User-Agent
Fetch the challenge page and replay the cookie from the same IP and the same User-Agent you pass in userAgent. The datadome cookie is tied to the session behind cid, so changing either invalidates it. Providers accept different User-Agent lists: if a task is rejected for its User-Agent, check the provider's documentation, and use the same value for the protected request, the challenge-page fetch, the task and the cookie replay.
Match your TLS fingerprint and header order to a real browser as well. A valid cookie on a mismatched client can still get a 403.
Use the cookie
solution.datadome is the cookie value on its own. solution.raw holds the provider's response; with Salamoonder it includes the full Set-Cookie line, so you can read attributes such as Path, Secure and SameSite there if you need to mirror them.
Related tasks
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
Salamoonder | $2.76 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in a workspace of the AnySolver dashboard. Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See Tasks for per-task schemas. View task properties |
settings | object | No | 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:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
websiteURL* | URL | Yes | Full URL of the protected page that returned the DataDome block. Use this exact URL as the Example: |
challengePage* | string | Yes | Base64-encoded raw response body from a GET to Example: |
userAgent* | string | Yes | User-Agent used to request the protected page and Example: |
captchaUrl* | URL | Yes | Full Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "DataDomeSliderCookieProxyLess",
"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",
"captchaUrl": "https://geo.captcha-delivery.com/captcha/?initialCid=AHrlqAAAAAMAlk-FmAyNOW8AUyTH_g%3D%3D&hash=5B45875B653A484CC79E57036CE9FC&cid=noJuZstmvINksqOxaXWQogbPBd01y3VaH3r-CZ4eqK4roZuelJMHVhO2rR0IySRieoAivkg74B4UpJ.xj.jVNB6-aLaW.Bwvik7__EncryD6COavwx8RmOqgZ7DK_3v&t=fe&referer=https%3A%2F%2Fwww.pokemoncenter.com%2F&s=9817&e=2b1d5a78107ded0dcdc8317aa879979ed5083a2b3a95b734dbe7871679e1403"
}
}Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes |
Example: | |
taskId | string | No | Unique identifier returned when the task was created. Example: |
errorCode | No | Machine-readable error code. Example: | |
errorDescription | string | No | Human-readable error message with resolution hints. Example: |
cost | number | No | Actual cost charged for this task in USD. Example: |
taskType | No | The type of CAPTCHA task to solve. Example: | |
provider | No | Provider that handled this task. While processing, the provider currently solving it. Example: | |
solution | object | No |
Solution Object Properties
The solution field contains an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
datadome* | string | Yes | The solved Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent string used during solving. Example: |