Skip to Content
AnySolver logo
AnySolver
Token

AkamaiAbckToken

Solve Akamai Bot Manager's _abck cookie through your proxy when you supply the sensor script URL and the page fingerprint yourself.

AkamaiAbckToken solves Akamai Bot Manager through your proxy and returns the Akamai cookie jar (_abck and related cookies) for a protected origin. Unlike AkamaiCookie, where the provider discovers the script itself, you provide the sensor script URL and the site's page fingerprint.

Proxy

task.proxy is required on this task type, and the provider solves from that address. Keep one IP for the whole solve and replay the cookies from it: see Keep the same IP for the whole solve.

Collect the inputs

Open the protected page in your browser with DevTools on the Network tab and Preserve log enabled, then reload.

Find the POST request whose body contains sensor_data. Its URL is akamaiJsUrl. The URL can change daily, so read it again for each session.

Set pageFp to the page fingerprint of the site. It is a hex string that is specific to each protected site and is not shown on the page. Providers supply it per site, so check the documentation of the provider you route to.

On high-risk sites, send a GET to websiteURL first and pass the cookies it sets (for example bm_sz) as initCookies.

Use the cookies

Set the cookies from solution.cookies and send the protected request with the returned userAgent and the same proxy exit IP. A valid _abck value contains ~0~, though some sites do not use that marker.

Bind to one IP and UA

Akamai rejects _abck if the IP or the User-Agent changes between solving and replaying.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
RiskBypass
$1.00

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

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:

FieldTypeRequiredDescription
type*
Yes
websiteURL*
URLYes

Full URL of the page where the CAPTCHA is displayed.

Example: https://shop.lululemon.com/

akamaiJsUrl*
stringYes

URL of the Akamai sensor script. In DevTools, find the POST request whose body contains sensor_data: its URL is the sensor script URL. It can change daily, so read it fresh.

Example: https://shop.lululemon.com/WGlx/lc_w/w/vez/w0HNXw/EmubktLXh3Npr6Nab5/TXUGYQ/Lh9aC2xK/H34

pageFp*
stringYes

Akamai page fingerprint of the target site: a hex string that is specific to each protected site. Providers supply it per site.

Example: 424541475255414d424b41585f5e50495c5148

proxy*
string | objectYes

Proxy the provider solves through, as a string or an object. See Proxy configuration.

View proxy configuration

Example: http://user:pass@1.2.3.4:8080

initCookies
Record<string, unknown>No

Optional, for high-risk sites. The cookies set by a GET to websiteURL, as a name → value map (for example bm_sz).

Example: {"bm_sz":"BCD5B7DFC133ED770D17429A247C9724~YAAQ7do..."}

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "AkamaiAbckToken",
        "websiteURL": "https://shop.lululemon.com/",
        "akamaiJsUrl": "https://shop.lululemon.com/WGlx/lc_w/w/vez/w0HNXw/EmubktLXh3Npr6Nab5/TXUGYQ/Lh9aC2xK/H34",
        "pageFp": "424541475255414d424b41585f5e50495c5148",
        "proxy": "http://user:pass@1.2.3.4:8080"
    }
}

Optional fields are not guaranteed across providers

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
cookies*
Record<string, unknown>Yes

Session cookies obtained during solving.

Example: {"_abck":"2706C6DDF2B013C342A7125C1C0F5185~0~YAAQ...","bm_sz":"BCD5B7DFC133ED770D17429A247C9724~YAAQ7do..."}

userAgent*
stringYes

User-Agent string used during solving.

Example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.