AkamaiCookie
Solve Akamai Bot Manager from a URL, user agent and proxy, and get the cookie jar (_abck, bm_sz, ak_bmsc) to replay on the protected origin.
AkamaiCookie solves Akamai Bot Manager through your proxy and returns the cookie jar (_abck, bm_sz, ak_bmsc) to replay on the protected origin. Akamai scores each session with a sensor script: the browser posts sensor_data to the script endpoint, and Akamai updates the _abck cookie with the verdict. The provider loads the page you give it, finds the sensor script, runs that exchange through your proxy and returns the resulting cookies.
A site uses Akamai Bot Manager when it sets the _abck and bm_sz cookies. Sites with the newer SBSD or sec-cpt layers also set cookies such as bm_s, bm_sc, sbsd_o or sec_cpt. Those layers have their own tasks, listed below.
Which Akamai task do I need?
| What you have or see | Task |
|---|---|
| A page URL, and you want the provider to find the script and run the exchange | AkamaiCookie (this task) |
| The sensor script URL and the site's page fingerprint, and you want the cookie jar | AkamaiAbckToken |
| You want sensor data to post from your own IP | AkamaiWebSensorProxyLess |
A script like /.well-known/sbsd?v=..., and you want the cookies through your proxy | AkamaiSbsdToken |
| The same SBSD script, and you want the payload to post from your own IP | AkamaiSbsdSensorProxyLess |
An HTTP 428 response with "sec-cp-challenge": "true" | AkamaiSecCptToken |
| A native Android or iOS app that posts Akamai sensor data | AkamaiBmpSensorProxyLess |
Proxy
task.proxy is required on this task type, and the provider uses it for the whole exchange, so the cookies belong to that exit IP. Keep one IP for the whole solve: see Keep the same IP for the whole solve. Proxy formats and the schemes each provider accepts are in Proxy configuration.
Choose the URL
Pass a page that loads the Akamai sensor script on the first GET, as websiteURL. This is often the login page rather than the bare homepage. If the page does not load the script, the solve fails because the script tag cannot be found. Send the User-Agent of your client as userAgent.
Use the cookies
Set every cookie from solution.cookies in your client and send the protected request with:
- the
userAgentyou submitted, unchanged; - the same proxy and exit IP you submitted;
- a TLS fingerprint and header order that match a real Chrome.
A valid _abck value contains ~0~. Some sites do not use that marker, so check by sending the protected request.
Replay with the same UA and exit IP
Akamai binds the cookies to the User-Agent and the exit IP used during solving. A mismatch invalidates _abck.
After a protected action, _abck can become invalid. When the origin starts rejecting you again, solve once more for a fresh jar.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
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 | URL of a page that loads the Akamai sensor script. The provider extracts the script path from this page, so use the page that carries it (often the login page). Example: |
userAgent* | string | Yes | Browser User-Agent string. Akamai fingerprints the UA, so you must replay the returned cookies with this exact same value. Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "AkamaiCookie",
"websiteURL": "https://www.example.com/login",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36",
"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 |
|---|---|---|---|
cookies* | Record<string, unknown> | Yes | Session cookies obtained during solving. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent string used during solving. Example: |