AkamaiWebSensorProxyLess

Generate Akamai Web v3 sensor data to POST yourself, round by round, until the origin issues a valid _abck.

This is the self-driven variant of the Akamai Web (v3) solve. The solver computes one sensor payload per call; you POST it to the sensor endpoint as sensor_data and repeat across several rounds until the origin returns a valid _abck. Because you drive the HTTP yourself, the cookie is bound to your own IP; no proxy is sent to the solver.

How the rounds work

Load the target page on your side and collect the bm_sz and _abck cookies, a fresh v3Url, and the v3 script body. Call this task with index: 0 and the script set; POST the returned payload to v3Url and keep solution.encodedata.

For each subsequent round, increment index, leave the script empty, and feed the previous solution.encodedata back in as the request's encodeData field (updating the _abck value to the latest cookie). POST each new payload to v3Url.

Stop once the _abck cookie is valid, typically after a few rounds.

v3Url changes per request

On most sites the Akamai v3 script URL rotates on every page load. Fetch a fresh v3Url each time rather than reusing an old one.

Keep the fingerprint consistent

Use the same user agent, language, IP and TLS across every round and on the final request that uses _abck. Validate the cookie each round; some sites accept it before a full set of rounds completes.

Supported Providers

Provider	Price per 1,000	Routing
EZCaptcha	$2.50

Request Schema

Field	Type	Required	Description
`clientKey`*	string	Yes	Your API key. Create one in the AnySolver dashboard. Example: `your-api-key-from-dashboard`
`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, and proxy behavior. See Routing Strategies.
`provider`		No	Specific provider to use. If omitted, automatic routing selects the best provider. Example: `CapSolver`
`selectionMode`		No	Routing strategy for this request. Overrides the API key default. See Routing Strategies. Example: `autoCheapest`
`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. Example: `all`

Task Object Properties

The task field accepts an object with the following properties:

Field	Type	Required	Description
`type`*		Yes
`pageUrl`*	URL	Yes	Full URL of the page where the CAPTCHA is displayed. Example: `https://www.target.com/login`
`v3Url`*	string	Yes	Akamai v3 sensor script URL. It usually rotates on each page load, so fetch a fresh one per request. Example: `https://www.target.com/akam/13/pixel_2a3b4c5d`
`bmsz`*	string	Yes	Current bm_sz cookie value from the page. Example: `AAB12C…`
`abck`*	string	Yes	Current _abck cookie value from the page. Example: `0~AB12…`
`ua`*	string	Yes	User-Agent for the session. Must match every request that uses the resulting cookie. Example: `Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36`
`lang`*	string	Yes	Accept-Language value for the session. Example: `en-US`
`scriptBase64`*	string	Yes	The v3 script body, base64-encoded. Only required on the first packet (index 0). Example: `dmFyIF8wPSc…`
`index`*	number	Yes	Zero-based sequence number of the current sensor packet. Example: `0`
`encodeData`*	string	Yes	Value returned as solution.encodedata by the previous packet. Empty on the first packet. Example:

{    "clientKey": "your-api-key-from-dashboard",    "task": {        "type": "AkamaiWebSensorProxyLess",        "pageUrl": "https://www.target.com/login",        "v3Url": "https://www.target.com/akam/13/pixel_2a3b4c5d",        "bmsz": "AAB12C…",        "abck": "0~AB12…",        "ua": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36",        "lang": "en-US",        "scriptBase64": "dmFyIF8wPSc…",        "index": 0,        "encodeData": ""    }}

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

Field	Type	Required	Description
`status`*		Yes	Task status: "processing", "ready", or "failed". Example: `ready`
`errorId`*		Yes	0 = success, 1 = external error, 2 = internal error. Example: `0`
`taskId`	string	No	Unique identifier returned when the task was created. Example: `01KFNDF328KAN2AJ3BNHCQYE88`
`errorCode`		No	Machine-readable error code. Example: `CAPTCHA_UNSOLVABLE`
`errorDescription`	string	No	Human-readable error message with resolution hints. Example: `The captcha could not be solved.`
`cost`	number	No	Actual cost charged for this task in USD. Example: `0.002`
`taskType`		No	The type of CAPTCHA task to solve. Example: `ReCaptchaV2TokenProxyLess`
`provider`		No	Specific provider to use. If omitted, automatic routing selects the best provider. Example: `Multibot`
`solution`	object	No	View solution properties

Solution Object Properties

The solution field contains an object with the following properties:

Field	Type	Required	Description
`payload`*	string	Yes	Sensor-data payload to POST to v3Url as sensor_data. Example: `7a2c1f…`
`raw`*	Record<string, unknown>	Yes	Raw provider response data for advanced use cases.
`encodedata`	string	No	Opaque value to feed back into the next request as encodeData. Example: `e3b0c4…`

AkamaiWebSensorProxyLess

How the rounds work

Supported Providers

Request Schema

Task Object Properties

Response Schema

Solution Object Properties

On this page

AkamaiWebSensorProxyLess

How the rounds work

Supported Providers

Request Schema

Task Object Properties

Response Schema

Solution Object Properties

On this page