Skip to content
CaptchaSonic

Bot mitigation solver

DataDome Bypass API

CaptchaSonic bypasses DataDome — the adaptive bot-mitigation layer that ships invisible JS challenges alongside user-facing slide and image-pick puzzles. The solver returns a validated `datadome` cookie that drops directly into the next request, so headless clients pass the gateway in one round trip.

captchasonic
# CaptchaSonic — DataDome bypass via REST
curl -X POST https://api.captchasonic.com/createTask \
  -H "Content-Type: application/json" \
  -d '{
    "clientKey": "YOUR_API_KEY",
    "task": {
      "type": "DataDomeTask",
      "websiteURL": "https://target.example.com/protected",
      "userAgent": "Mozilla/5.0 (...) Chrome/120",
      "proxy": {
        "type": "http",
        "host": "residential.proxy.io",
        "port": 8080,
        "login": "user",
        "password": "pass"
      }
    }
  }'

# Poll getTaskResult — returns { solution: { cookie: "datadome=..." } }
# Drop the cookie into your next request and the DataDome gate passes.
99.9%
成功率
99.9%
稼働率

Sonicを使う理由: Bot mitigation solver?

速度、信頼性、簡単な連携のために設計されています。

6-10s median solve

End-to-end solve time for both invisible JS and visible slide tiers — fast enough for high-throughput scrapers.

Validated cookie return

Returns the real `datadome` cookie ready to set on subsequent requests. Cache for ~1 hour per fingerprint.

Proxy-bound fingerprint

Solve from inside your residential egress IP so the cookie matches the address DataDome sees on the next hop.

Async polling pattern

createTask returns a taskId; poll getTaskResult every 2-3s until the cookie resolves — standard 2captcha-compatible flow.

構築に使う

SDK

AIエージェント

Defeat DataDome bot mitigation from any AI agent via MCP.

MCPのドキュメント

拡張機能

SDKの例
Python
from captchasonic import CaptchaSonic
client = CaptchaSonic(api_key="YOUR_API_KEY")

# 1. submit the task
task = client.create_task({
    "type": "DataDomeTask",
    "websiteURL": "https://example.com",
    "captchaUrl": "https://geo.captcha-delivery.com/captcha/..."
})

# 2. poll until the solution resolves
result = client.get_task_result(task.task_id)
print(result.solution)
Node
import { CaptchaSonic } from 'captchasonic'
const client = new CaptchaSonic({ apiKey: 'YOUR_API_KEY' })

// 1. submit the task
const task = await client.createTask({
  type: 'DataDomeTask',
  websiteURL: 'https://example.com',
  captchaUrl: 'https://geo.captcha-delivery.com/captcha/...'
})

// 2. poll until the solution resolves
const result = await client.getTaskResult(task.taskId)
console.log(result.solution)
他社との比較

Compare

他社との比較

Feature-by-feature against the four most-mentioned alternatives, compiled from each provider’s public pricing pages. Competitor figures may change — verify current rates with each provider.

FeatureCaptchaSonic2CaptchaCapSolverAnti-CaptchaCapMonster Cloud
AI / ML solver (no human relay)
AWS WAF
Success rate (trailing 30d)99.9%~95%~98%~95%~97%
Proxy + proxyless modes
Free trial credits
SDK languages (Py, Node, Go, C#, Java, PHP)66454
Selenium / Puppeteer / Playwright examples
Browser extension
Webhook callbacks
99.9% uptime SLA

よくある質問

DataDome fingerprints each session with around 30 client-side signals — canvas, WebGL, navigator props, mouse entropy, header order — and serves either an invisible JS challenge or an interactive image-slide puzzle when the score drops. Validated sessions receive a `datadome` cookie. CaptchaSonic replays the full flow server-side and returns that cookie.

Typical TTL is around 1 hour per origin and device fingerprint. Cache the cookie across requests inside that window — re-solving on every call wastes spend and degrades the fingerprint. Rotate the cookie at the same cadence you rotate proxies.

Yes — pass `proxy.host`, `proxy.port`, and credentials in the createTask payload. CaptchaSonic solves from inside the same egress IP so the issued cookie fingerprints to the address DataDome will see on subsequent requests. Mismatched IPs are the #1 cause of DataDome re-prompts.

CaptchaSonic returns a real DataDome-issued cookie, not a forged one — the gateway validates it identically to a human-solved cookie. Detection comes from session-level signals (proxy reputation, header consistency, request cadence). The token itself is indistinguishable from a real-user solve.