DataDomeTagsCookie
Send the DataDome JS Tag telemetry for a session through your proxy and get the datadome cookie it returns. With the schema, an example and provider prices.
DataDomeTagsCookie sends the DataDome JS Tag telemetry for a session through your proxy and returns the datadome cookie DataDome answers with. The JS Tag (tags.js) runs in the visitor's browser and posts browser signals to DataDome; the task produces that request for you. Some providers list this flow as "DataDome invisible".
This task does not solve a challenge
The JS Tag is not part of a block page. If the protected site already returned a 403 with a challenge, use
DataDomeInterstitialCookie for the device check (rt:'i', i.js) or
DataDomeSliderCookie for the puzzle (rt:'c', c.js).
Find the parameters
DataDome's JavaScript Tag documentation shows the snippet a protected page uses:
<script>
window.ddjskey = 'YOUR_DATADOME_JS_KEY';
window.ddoptions = {
ajaxListenerPath: true,
};
</script>
<script src="https://js.datadome.co/tags.js" async></script>Open the protected page with DevTools and read the values from it.
ddjskeyiswindow.ddjskeyin the console. It is the same for every visitor of the site.ddoptionsiswindow.ddoptionsin the console. Pass the object as the page defines it.datadomeJsUrlis thesrcof thetags.jsrequest in the Network tab. It ishttps://js.datadome.co/tags.jsby default and can include a version such as/v5.1.13/tags.js. When the site serves the tag itself, it is a path on the site's own domain.
Send the proxy
task.proxy is required on this task type, and the provider sends the telemetry from that address. The proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve.
Optional parameters
userAgent: the User-Agent to emulate. Providers that support it match the fingerprint to this string and fail the task when they have none for it; others ignore it and pick their own. Use the same value for every request that replays the cookie.cid: thedatadomecookie the session already holds. Send it to continue that session instead of starting a fresh one. Not every provider accepts it.
Use the cookie
Run the task before you request the protected endpoints, then keep the returned solution.datadome in your cookie jar as the datadome cookie on the protected domain. The solution also returns the userAgent the provider used. If a challenge appears later, use the cookie as the cid parameter of the challenge URL so the solve continues the same session.
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 |
|---|---|---|
RiskBypass | $2.00 | |
ShopifaSolver | $1.50 |
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 page where the CAPTCHA is displayed. Example: |
datadomeJsUrl* | string | Yes | URL of the DataDome JS Tag ( Example: |
ddjskey* | string | Yes | The DataDome client-side JS key the page sets as Example: |
ddoptions* | Record<string, unknown> | Yes | The DataDome JS Tag options the page sets as Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
userAgent | string | No | User-Agent to emulate. Providers that support it match the fingerprint to this string and fail the task when they have none for it; others ignore it and pick their own. Example: |
cid | string | No | The Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "DataDomeTagsCookie",
"websiteURL": "https://example.com/",
"datadomeJsUrl": "https://js.datadome.co/tags.js",
"ddjskey": "YOUR_DATADOME_JS_KEY",
"ddoptions": {
"ajaxListenerPath": true
},
"proxy": "http://user:pass@1.2.3.4:8080"
}
}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 Example: |
userAgent* | string | Yes | User-Agent string used during solving. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |