AkamaiCookie
Fully-managed Akamai Bot Manager bypass — send a URL, user agent and proxy, get back the cookie jar (_abck, bm_sz, ak_bmsc) to replay on the protected origin.
Akamai Bot Manager fingerprints the client and gates the origin behind a sensor-data challenge. AkamaiCookie runs the full handshake for you — it fetches the target, extracts the sensor script, runs the sensor rounds, and returns the resulting cookie jar. The cookie that matters is _abck, which marks the session as trusted.
You only supply a URL, a user agent and a proxy. Everything else is handled solver-side.
Replay with the same UA and exit IP
Akamai binds the cookies to the User-Agent and the proxy exit IP used during solving. Replay the returned cookies
with the exact same user agent and the same proxy/exit IP you submitted. A mismatch invalidates _abck.
Choosing the URL
Use the URL that actually serves the Akamai sensor on the first GET — this is often the login page, not the bare homepage. If the page you pick doesn't load the sensor, the solve fails with a "script tag not found" style error.
Proxy
A proxy is required and is used for the entire handshake, so the cookies are bound to that exit IP. Supported schemes are http, https, and socks5 — socks4 is rejected. Prefer residential or mobile IPs; datacenter ranges are scored harshly by Akamai.
Cookies expire
_abck is consumed over a handful of requests, and Akamai can invalidate it early. When the origin starts rejecting
you again, solve once more for a fresh jar.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
 | $2.00 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in the [AnySolver dashboard](/dashboard/api-keys). Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See [Tasks](/docs/tasks) for per-task schemas. View task properties |
provider | No | Specific provider to use. If omitted, automatic routing selects the best provider. Example: | |
selectionMode | No | Routing strategy for this request. Overrides the API key default. See [Routing Strategies](/docs/getting-started/routing-strategies). Example: | |
keyPoolMode | No | Which provider key pool to use: `all` (default, uses AnySolver-managed keys and your own) or `platformOnly` (AnySolver-managed keys only). See [Key Pool Mode](/docs/getting-started/routing-strategies#key-pool-mode). Example: |
Task Object Properties
The task field accepts an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
websiteURL* | URL | Yes | The Akamai-protected origin — the page that loads the sensor script (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 |
Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes | 0 = success, 1 = external error, 2 = internal error. 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 | Specific provider to use. If omitted, automatic routing selects the best provider. 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 (if applicable). |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent string used during solving (if applicable). |