Queue-it BotDeflector solver API
Some Queue-it waiting rooms gate entry behind BotDeflector. Send the flow token from your own session and get back a ready-to-send request that redeems it. Your session stays yours from start to finish.
- Price
- from €1.20 per 1,000 solves€3.00 before level discounts
- You send
- The flow token from your Queue-it session
- You get
- A signed result and the request that redeems it
- Proxy
- Only when the token is bound to an IP
- Failed solves
- Free
What BotDeflector is
Queue-it normally admits a visitor to its waiting room on a redirect. On protected events it can put BotDeflector first: a challenge the visitor has to pass before taking a place in the queue. The challenge comes with an audio variant and a proof-of-work step, and passing it produces a signed result that Queue-it verifies.
This solver handles exactly that step. It does not join the queue, hold a place or fetch your page. It takes the flow token your own session was given, solves the challenge against Queue-it’s host, and returns the request that hands the result back.
How a solve goes
- Reach the waiting room on your own session. When BotDeflector is shown, read the flow token it issues.
- Send the flow token with the page URL. Add the
x-queueit-challange-hashfrom your softblock page if you captured it, and your proxy if the token is bound to an IP. - Take the redeem request from the response as given: method, URL, headers and body.
- Add your session’s cookies and send it on the session that minted the token. A real pass continues through the waiting room as normal.
{
"type": "queueit.botdeflector",
"url": "https://ticket-onlineshop.com/events/x",
"flowToken": "<the BotDeflector flow token from your own Queue-it session>",
"checksumHash": "<optional: x-queueit-challange-hash from your softblock page>",
"proxy": "http://user:pass@host:port"
}{
"ok": true,
"requestId": "req_Nn8f…",
"result": {
"challengeFlowResult": "…",
"botdeflector": {
"method": "POST",
"url": "https://securedbyqueueit.queue-it.net/spa-api/queue/<customerId>/<eventId>/challenge/botdeflector/verify",
"headers": {
"x-queueit-challange-customerid": "…",
"x-queueit-challange-eventid": "…",
"x-requested-with": "XMLHttpRequest",
"x-queueit-challange-hash": "… (only when you sent checksumHash)"
},
"body": { "challengeType": "botdeflector", "sessionId": "…", "solution": "…", "customerId": "…", "eventId": "…" }
}
},
"cost": 0.003,
"costMicro": 3000,
"solveMs": 740
}Full reference: Queue-it BotDeflector docs.
What makes a solve count
One token, one use
A flow token is spent once it is redeemed. A rejected solve usually means the token was invalid or already used, so mint a fresh one.
The IP that minted it
When the site binds the token to an IP, pass that IP as the proxy. Otherwise Queue-it does not accept the result.
The same session
Redeem on the session that holds the token, with its cookies. The solver never sees or needs that session.
What you send, field by field
| Field | Required | What it is |
|---|---|---|
url | Yes | The protected page, for example the shop URL. Its domain must be approved. It is never fetched. |
flowToken | Yes | The BotDeflector flow token from your own Queue-it session, up to 4,096 characters. |
checksumHash | No | The x-queueit-challange-hash from your softblock page. If you leave it out, add that header yourself when you redeem. |
proxy | If the token is IP-bound | The IP that minted the token, in the same format as every other solver. |
Where BotDeflector sits in Queue-it
Queue-it describes its waiting room as a checkpoint that visitors pass before they reach the site, and lists CAPTCHA and proof-of-work among the challenges it can put at that checkpoint. BotDeflector is that challenge step. It runs before a place in the queue is handed out, which is why solving it does not move you forward in line: it only lets your session take a place.
Queue-it also lists IP binding among its protections. On events where the flow token is tied to the IP that minted it, the token only redeems from that address. That is the one case where this solver needs your proxy.
Source: Queue-it, bot and abuse protection.
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 |
|---|---|---|
TRANSPORT_ERROR | The solving backend was unreachable or full. | Retry the same request with the same flow token. |
Any other reason | The flow token was rejected: invalid, already used, or sent from a different IP than the one it is bound to. | Mint a fresh flow token on your session and solve again. |
domain_not_allowed | The domain of url is not approved for your account yet. | Request the site on the Sites page. |
If the redeem request is refused although the solve succeeded, check that it was sent on the session that minted the token, with its cookies and the x-queueit-challange-hash header. Every code and reason: error reference.
Queue-it BotDeflector pricing
€3.00 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 | €3.00 |
| From €100 | −20% | €2.40 |
| From €250 | −30% | €2.10 |
| From €500 | −40% | €1.80 |
| From €1,000 | −50% | €1.50 |
| From €2,500 | −55% | €1.35 |
| From €5,000 | −60% | €1.20 |
- 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 |
Queue-it BotDeflector solver: questions
What is Queue-it BotDeflector?
BotDeflector is the challenge some Queue-it waiting rooms put in front of entry, instead of admitting visitors on a redirect. It is a captcha-style challenge with an audio option and a proof-of-work step, and a visitor who passes it continues into the queue.
What do I need before calling the solver?
A BotDeflector flow token from your own Queue-it session. You reach the waiting room yourself, and the token is issued to your session when the challenge is presented.
Do you fetch my page or join the queue for me?
No. The challenge is solved against Queue-it’s own host from the flow token you send. The page URL is only checked against your approved sites and is never fetched. You own the Queue-it session throughout.
What do I get back?
A server-signed proof that the challenge was solved, and a complete request to redeem it: method, URL, headers and body. You add your session cookies and send it.
Do I need a proxy?
Only when the site ties the flow token to the IP that minted it. In that case pass that same IP as the proxy, or Queue-it will not accept the solve.
Can I reuse a flow token?
No. A flow token is single use. Once it has been redeemed you need a fresh pass through the waiting room’s own flow to get another.
What does it cost?
€3.00 per 1,000 successful solves at list price and €1.20 at the top discount level. A failed solve is always free.
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.
- Akamai edge solverClear the Akamai “Unusual Traffic Detected” fingerprint screen and get the real page’s cookies.
- 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.
- 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.