Where the _abck cookie comes from
The first response from an Akamai-protected site sets the _abck cookie together with bm_sz. At that point the cookie exists, but it is not valid yet: it only marks a client that has not proven anything.
The same HTML loads Akamai Bot Manager's script from a long, randomly generated path near the end of the body. In a browser, that script collects sensor data and posts it back to the same path. Every accepted post returns a Set-Cookie header with an updated _abck.
Ordinary page loads do not depend on the cookie. Akamai checks it when the client performs an action the site has marked as protected: typically login, add-to-cart, checkout or a search API. That is why a scraper can read product pages for hours and still fail on the first add-to-cart.
Valid or invalid: what to look for
- Right after the first page load:
_abckis present, but not validated. - After accepted sensor posts: many sites write
~0~into the cookie value once the session is validated. Not every site uses this marker. Where it is missing, the Hyper Solutions flow posts a fixed number of sensors (three) before the protected action. - After a protected action: the cookie is usually invalidated again. The next protected action needs fresh sensor data.
- Never validates: if
_abckstays invalid after three posts, the cause is usually the client rather than the sensor: a handshake that does not match Chrome's TLS fingerprint, a header order no browser sends, or an IP address that changed mid-session.
The Hyper Solutions SDKs include a helper that reads the stop signal in the cookie and compares it with the number of sensors you posted (IsCookieValid in Go, is_cookie_valid in Python). On sites without the marker it stays false, so you stop after three posts yourself.
The cookies around it
Akamai Bot Manager sets more than one cookie, and you will usually see them together in a capture:
bm_szis set on the first response. Its value is an input when sensor data is generated, so it has to come from the same session.ak_bmscandbm_svare further Bot Manager cookies. The sensor flow does not use them as inputs. A few sites also run Akamai's pixel check, which validatesak_bmscwith its own payload. Keep both in your cookie jar and send them back the way the browser does.- Some sites also run SBSD, a separate Akamai check with its own script and its own payload.
Why request-based clients end up with an invalid cookie
A validated _abck belongs to the session that earned it. The same values Akamai saw while the sensors were posted have to stay the same until the protected action:
- the TLS fingerprint and HTTP/2 settings of your client;
- the User-Agent and the client hints that go with it;
- the exact header order of every request;
- the IP address, which is why rotating proxies break the flow halfway.
Copying a valid _abck from your own browser into a script rarely works for long. The protected action invalidates it, and the next one needs a new round of sensor data from a client that matches the session.
When the block is not about _abck
Not every Akamai block comes from this cookie. An "Access Denied" page from a server named AkamaiGHost, with a Reference # ID, is an edge or WAF rule: there is no challenge to solve, and a valid _abck does not change it. Fix the IP and the client first. Some Akamai sites also never post sensor data; their protected API calls carry an Akamai-BM-Telemetry request header instead, and the API answers 403 without a valid one.
Where to go next
The full flow, from parsing the script path to posting sensor data, is in the Akamai getting-started docs and the request-based Akamai guide. The Hyper Solutions Akamai API generates the sensor data, so your client only has to fetch the script, post the payload and keep the session consistent.