Akamai edge solver for “Unusual Traffic Detected”
Some Akamai sites screen the request before any challenge script runs. A request that does not look like a browser gets an “Unusual Traffic” page instead of the content. Send the URL and your proxy, and get back the cookies of the real page.
- Price
- from €1.00 per 1,000 solves€2.50 before level discounts
- Speed
- Typically under a second
- You send
- The page URL and your proxy
- You get
- The real page’s cookies and the user agent to use
- Failed solves
- Free
What the edge screen is
Akamai can turn a request away at the edge, before Bot Manager serves a single script. The decision comes from the shape of the request alone: its headers and its TLS handshake. A plain HTTP library does not match a real browser on either, so it receives a flat “Unusual Traffic Detected” page with nothing in it to solve.
That is why this solver is a request-shape fix and not a sensor solve. Nothing is computed and posted back to the site. The request is made the way the edge expects, through your proxy, and the cookies the real page sets are returned to you.
Edge screen or sbsd challenge?
They look alike at first glance and need different solvers.
| Edge screen | SBSD challenge | |
|---|---|---|
| What comes back | A flat “Unusual Traffic Detected” page | HTML with a script tag at ?v=<uuid> |
| Decided from | Headers and TLS, before anything else | The answer the script posts back |
| Solver | akamai.edge | Akamai SBSD solver |
Send an sbsd page to this solver and it answers solve_failed with reason not_busypage, free.
One request
The response carries the cookies, the user agent they belong to, the final status and how many tries it took. You pay once either way.
curl https://api.notabot.sh/v1/solve \
-H "x-api-key: $NOTABOT_KEY" \
-H "content-type: application/json" \
-d '{
"type": "akamai.edge",
"url": "https://shop.example.com/",
"proxy": "http://user:pass@host:port"
}'Full reference: Akamai edge docs.
What makes it stick
A clean IP
A persistently flagged IP stays denied whatever the request looks like. Residential or mobile proxies work best.
The same proxy afterwards
The cookies belong to the IP that earned them. Send your own requests through the proxy you passed to the solver.
The user agent we return
Use it unchanged, with a client whose TLS fingerprint matches Chrome, or the edge screens you again on the next request.
Using the cookies afterwards
The cookies work with the user agent they came with, from the IP that earned them, on a client that looks like that browser.
- Send every cookie in the result, and keep whatever the site sets afterwards. Some sites rotate them.
- Copy the returned user agent into your
user-agentheader exactly. - Stay on the same proxy. If the exit IP changes, the cookies stop working. Use a sticky session.
- Connect like Chrome. Stock Node, Python and Go clients handshake differently from Chrome, and a site can drop good cookies that arrive that way. Use curl-impersonate, httpcloak, tls-client or a real browser for your own requests.
- Reuse the result until it stops working. The site decides how long cookies last. Solve again when challenges come back, not before every request.
| Limit | Value | Note |
|---|---|---|
| Solve timeout | 30 seconds | Set your own client timeout to 60 seconds so it outlasts ours |
| Typical solve time | 2 to 10 seconds | Mostly round trips through your proxy. Our own work is well under a second |
| Requests per second | 50 per key, 200 per account | Over it you get rate_limited with a retry-after header |
| Proxy format | http://user:pass@host:port | SOCKS is not supported. Residential or mobile IPs clear far more often than datacenter ones |
Worked example in Node: Using the result. All limits: Limits.
When a solve fails
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 |
|---|---|---|
BLOCKED | The site refused the request, or there was no edge screen on the page for this solver to clear. | If the reason is not_busypage, the page was an sbsd challenge or was never screened: use the SBSD solver or fetch it directly. Otherwise change to a clean residential or mobile IP. |
TRANSPORT_ERROR | The proxy or the site dropped the connection. Retry, ideally on a new IP. | Retry, ideally on a new IP. |
BAD_PROXY | The proxy is not a usable http://user:pass@host:port URL, or it refused us. | Send the proxy as http://user:pass@host:port and check it accepts connections. |
RATE_LIMIT | The site rate-limited the proxy IP. Slow down or change IP. | Slow down on that IP or switch to another. |
domain_not_allowed | The domain is not approved for your account yet. | Request the site on the Sites page. |
solver_timeout | The solve ran past 30 seconds. | Retry. Keep your own client timeout at 60 seconds. |
Every code and reason: error reference.
Akamai edge pricing
€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 |
- Top up from €10 by card. The balance works for every solver.
- A level counts everything you have ever topped up, and it never drops.
- The price is reserved when you call and released if the solve fails.
- Each key can carry its own daily, monthly or total spend limit.
An API call instead of a headless browser
| 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 |
Akamai edge solver: questions
What is the Akamai edge fingerprint screen?
A check Akamai runs on the request itself, before any challenge script is served. It looks at the headers and the TLS handshake, and when they do not look like a real browser it answers with a flat "Unusual Traffic Detected" page instead of the content.
How is it different from the sbsd challenge?
The edge screen never shows a challenge script. An sbsd page contains a script tag ending in ?v= and a UUID, and the browser has to answer it. If the page you get back has that script tag, use the SBSD solver. This one refuses an sbsd page instead of guessing, and the refusal is free.
What do I send and what do I get?
You send the page URL and your proxy. You get every cookie the real page set, the user agent the session used, and the final status. Send those cookies on your own requests through the same proxy.
How fast is it?
Typically under a second. Nothing is generated or posted back to the site, so there is no script to run.
Why does it still fail on some IPs?
If the IP itself is flagged it stays denied however the request is shaped. Use a clean residential or mobile proxy with a sticky session.
What does it cost?
€2.50 per 1,000 successful solves at list price and €1.00 at the top discount level. You pay once per solve however many attempts it took, and nothing when it fails.
Can I use it on any site?
Each domain is approved once before it can be solved, usually within a day. Subdomains of an approved domain are covered.
Other solvers
- Akamai solverSolve the Akamai sbsd challenge and the edge fingerprint screen without a browser.
- Akamai SBSD solverSend the sbsd challenge script, get the payload that answers it in about a second.
- Cloudflare solverGet a cf_clearance cookie from Cloudflare JavaScript Detections with one API call.
- Cloudflare JSD solverRun the Cloudflare JavaScript Detections exchange and return cf_clearance, without a browser.
- Queue-it BotDeflector solverSolve the Queue-it BotDeflector challenge from a flow token and get a ready-to-send redeem request.
- Ticketmaster tmpt solverBuild the reCAPTCHA Enterprise reload body that mints the Ticketmaster tmpt cookie.
Page updated . Reference for every solver: documentation.
Try it on your own target.
Login, copy a key, send one request. If the solve fails, it costs you nothing.