[ 01 ]What it looks like
Usually nothing visible: a 403, or a page that reloads forever before any content loads.
Captcha type · Akamai
Akamai Bot Manager handled as a priced, supported type with a real accepted rate, not listed at zero the way services that cannot solve it list it.
Also searched as_abck cookiesensor_databm_szAkamai BMPx-acf-sensor-data
[ 01 ]What it looks like
Usually nothing visible: a 403, or a page that reloads forever before any content loads.
[ 02 ]Why it is hard
The gate is a valid _abck cookie, earned by POSTing a sensor_data payload built from heavily obfuscated per-site JavaScript that mixes device telemetry, WebGL and TLS fingerprints, and input timing. Akamai re-obfuscates the script frequently, so a static reimplementation decays within weeks. The mobile BMP variant signs each request with an X-acf-sensor-data header from a different SDK, which means web and app need separate implementations.
[ 03 ]How we solve it
A dedicated Akamai pool tracks the per-site script and regenerates sensor_data against the version currently served, so a re-obfuscation on their side does not stop your crawl. Payloads are produced behind your proxy and userAgent because _abck is scored against both, and we keep the TLS fingerprint consistent with the user agent you send. Sites that escalate to an Akamai-hosted challenge page are picked up by the same task and still return one usable cookie set.
[ 02 ]Solve it in five lines
Post the task, get the token. Our SDKs collapse creation, polling and retries into one call.
curl -s https://api.nexcaptcha.net/createTask \
-H "Content-Type: application/json" \
-d '{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "AkamaiTask",
"websiteURL": "...",
"userAgent": "...",
"proxy": "..."
}
}'Required parameters
[ 03 ]Where this one shows up
[ 05 ]Questions about this one
Because they do not sell it. A $0 row on a rate card means the type is listed for completeness, not solved: 2Captcha publishes Akamai at zero and offers custom arrangements instead. We price it at $4.49 per 1,000 because we actually run it, at a 96.8% accepted rate.
A valid _abck cookie plus the supporting bm_sz and ak_bmsc values, matched to the proxy and user agent you sent. Put all of them on your next request with the same headers and TLS client, and the request reaches the origin.
Mobile BMP is a separate path: it signs requests with an X-acf-sensor-data header generated by Akamai’s app SDK rather than browser JavaScript. Tell us which one you need when you open the account, because the two use different worker pools.
It is re-scored on every request rather than expiring on a fixed clock, and it degrades if your request rate, header order or TLS fingerprint drifts from the session that earned it. In practice, reuse one cookie across a session and re-solve when you see a 403 return.
Create a key, paste it into the sample above, and watch a real token come back. No card, no sales call.