SBSD challenge
- The page carries a challenge script at
?v=<uuid>. Answering it setsbm_s,bm_scandbm_so. You send the script, we return the payload, in about a second. - Akamai SBSD solver
Akamai Bot Manager puts more than one gate in front of a page. notabot solves them over plain HTTPS, with no browser to run, and charges only for solves that work.
They look alike from the outside and need different answers. Pick by what the site sends back.
?v=<uuid>. Answering it sets bm_s, bm_sc and bm_so. You send the script, we return the payload, in about a second._abck cookie from sensor posts, on web and in mobile apps.soonRequest the page once with a Chrome client and read what comes back.
| What you get back | Gate | Use |
|---|---|---|
| “Unusual Traffic Detected”, no script tag | Edge fingerprint screen | akamai.edge |
HTML with a script at ?v=<uuid>, or bm_s / bm_so cookies | SBSD challenge | akamai.sbsd.payload |
The page loads, then _abck is checked on later requests | Sensor data | Not live yet |
Send the wrong type and the solver refuses instead of guessing, and you are not charged.
A site can run more than one of these, and they apply in order. The edge screen comes first: it judges the request itself, from its headers and TLS handshake, before Bot Manager serves any script. A request that passes it can then be handed the sbsd challenge, which a browser has to answer. So a session on a strict site may need the edge solver for its first request and the sbsd solver a moment later.
The practical rule is to solve what the site actually sent back and nothing else. Each solver refuses a page that belongs to a different gate, at no charge, so trying the wrong one costs a round trip and tells you which one to use.
Step by step with code: Quickstart. A full sbsd walkthrough: How to solve Akamai SBSD without a browser.
A failed solve is never charged. The response names the reason, and each one has a specific fix.
| Reason | What it means | What to do |
|---|---|---|
NOT_CHALLENGED | The site did not challenge this IP, so there was nothing to solve. Fetch the page directly. | For sbsd, download the script fresh and send values from that same response. For the edge solver, fetch the page directly. |
BLOCKED | The site refused the request before any challenge was shown. Usually the IP. | Change to a clean residential or mobile IP. With reason not_busypage on the edge solver, the page was an sbsd challenge: use the sbsd solver. |
GATE_NOT_CLEARED | The answer was valid but the site still held the session back. Nearly always a flagged IP. Retry on a fresh one. | Retry on a fresh IP. |
UNSUPPORTED_PROFILE | akamai.sbsd.payload only. The userAgent is not one of the supported Chrome versions. The message lists them. | Use one of the Chrome versions the message lists, on every request. |
TRANSPORT_ERROR | The proxy or the site dropped the connection. Retry, ideally on a new IP. | Retry, ideally on a new IP. |
domain_not_allowed | The domain is not approved for your account yet. | Request the site on the Sites page. |
Every code and reason: error reference.
€2.50 per 1,000 successful solves, and less as your lifetime top-ups grow. No subscription, credits never expire, and a solve that fails is not charged.
| Topped up in total | Level | You pay |
|---|---|---|
| Under €100 | List price | €2.50 |
| From €100 | −20% | €2.00 |
| From €250 | −30% | €1.75 |
| From €500 | −40% | €1.50 |
| From €1,000 | −50% | €1.25 |
| From €2,500 | −55% | €1.125 |
| From €5,000 | −60% | €1.00 |
| notabot API | Headless browser | |
|---|---|---|
| What you run | One HTTPS request | A Chrome instance per session, plus the servers under it |
| When the protection updates | We patch the solver. Your code is unchanged | You patch stealth plugins and redeploy |
| What you pay for | Successful solves only | CPU, memory and bandwidth, whether or not the page passes |
| Scaling up | Send more requests | Add more machines |
The sbsd challenge (the bm_s, bm_sc and bm_so cookies) and the edge fingerprint screen (the "Unusual Traffic Detected" page) are live. Sensor data for _abck is next.
Look at the response to a plain page request. A flat "Unusual Traffic Detected" page with no script is the edge screen. HTML with a script tag ending in ?v= and a UUID is the sbsd challenge. A page that loads and then posts sensor_data to validate _abck is the sensor gate.
No. Every solver is plain HTTPS. For sbsd you need an HTTP client with a real Chrome TLS fingerprint to make your own requests to the site.
€2.50 per 1,000 successful solves at list price, down to €1.00 at the top discount level. There is no subscription, credits never expire, and a solve that fails is not charged.
For the edge screen, yes: send the residential or mobile proxy you will make your requests through, because the cookies are bound to that IP. For sbsd, no proxy is sent to us at all. You make the requests yourself.
We update the solvers. Your endpoint, key and request body stay the same, and a solve that fails in the meantime is free.
Page updated . Reference for every solver: documentation.
Login, copy a key, send one request. If the solve fails, it costs you nothing.