Ticketmaster tmpt solver API
Ticketmaster’s EPS pages gate on a reCAPTCHA Enterprise score. You run the flow on your own session, and we build the one piece you cannot: the reload body that mints the scoring token behind the tmpt cookie.
- Price
- from €4.00 per 1,000 solves€6.00 before level discounts
- You send
- The reCAPTCHA anchor HTML you fetched
- You get
- The reload body, ready to post to Google
- Proxy
- None. We never touch the site
- Failed solves
- Free, and so is the version call
How the tmpt gate works
The EPS pages load reCAPTCHA Enterprise in the background. The browser fetches an anchor page from Google, posts a reload request built from it, and receives a token. The site’s /epsf/gec/v3/pageView endpoint scores that token and, when it is satisfied, sets the tmpt cookie.
Every step except one is an ordinary HTTP request you can make yourself. The exception is the reload body, which a real browser computes. That is the part this solver returns.
The flow, step by step
- Ask for the release id. Post
{ "type": "tmpt", "op": "version" }. It is free, and you need it to build the anchor URL. - Fetch the anchor page from Google’s
/recaptcha/enterprise/anchoron your own session. - Send us the anchor HTML with the user agent you will use. The response carries the reload body, base64 encoded.
- Decode it and post it to
/recaptcha/enterprise/reload?k=<sitekey>asapplication/x-protobuffer. Google answers with the token. - Post the token to the site’s
/epsf/gec/v3/pageView. It setstmpt, and your session carries it from there.
{
"type": "tmpt",
"op": "reload",
"anchorHtml": "<the HTML of the Google reCAPTCHA /enterprise/anchor page you fetched>",
"page_url": "<the URL of the page the reCAPTCHA is on>",
"userAgent": "<optional: the UA you will post the reload with>",
"cookies": ["<optional: your site cookies as name=value>"]
}{
"ok": true,
"requestId": "req_Nn8f…",
"result": { "reload": "<base64 reload body, exactly as the builder returned it>" },
"cost": 0.006,
"costMicro": 6000,
"solveMs": 300
}Full reference: tmpt docs.
What makes it work
A fresh anchor every attempt
Anchors expire. Fetch a new one each time and never reuse one across attempts.
One user agent throughout
Send us the user agent you will post the reload with, and use it for every step of the flow.
Your session, your IP
Nothing is bound to us. The token, the cookie and every request to the site belong to your own session.
What you send, field by field
Fields not listed are dropped.
| Field | Required | What it is |
|---|---|---|
op | No | reload (the default) or version. |
anchorHtml | For reload | The HTML of the Google reCAPTCHA /enterprise/anchor page you fetched, up to 400,000 characters. |
page_url | For reload | The URL of the page the reCAPTCHA is on, for example the event page. |
action | No | pageView (the default) or Event. |
userAgent | No | The user agent you will send when you post the reload. Defaults to a Windows Chrome user agent. |
cookies | No | Your site’s non-HttpOnly cookies, as name=value strings. |
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 |
|---|---|---|
VENDOR_ANOMALY | Nothing usable could be built from that anchor, usually because it expired. | Fetch a fresh anchor and retry. Never reuse an anchor across attempts. |
TRANSPORT_ERROR | The solving backend was unreachable. | Retry the same request. |
bad_params | A field is missing or invalid. | Send anchorHtml as a string under 400,000 characters, and page_url as a full URL. |
If Google accepts the reload but the site does not set tmpt, the token was not accepted for that session: check the user agent is the same on every step and that your cookies were sent. Every code and reason: error reference.
tmpt pricing
€6.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 | €6.00 |
| From €100 | −20% | €4.80 |
| From €250 | −30% | €4.20 |
| €500 and above | −33% | €4.00 |
€4.00 is the lowest price for tmpt. Higher levels keep lowering your other solves.
- 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 |
Ticketmaster tmpt solver: questions
What is the Ticketmaster tmpt cookie?
Ticketmaster’s eticketing (EPS) pages check a reCAPTCHA Enterprise score before they let a session continue. A session that passes is given a cookie named tmpt, and later requests carry it.
What exactly does this solver do?
It builds the one piece of the reCAPTCHA flow you cannot build yourself: the reload request body that mints a scoring token. You fetch the anchor page, send us its HTML, and get the reload body back unchanged.
Do you make requests to Ticketmaster or Google for me?
No. You run every browser-facing step on your own session. We never fetch the site, and no proxy is sent to us.
What are the two operations?
version returns the current reCAPTCHA release id, which you need to build the anchor URL, and it is free. reload takes your anchor HTML and returns the reload body, and it is the one that is charged.
Why did I get VENDOR_ANOMALY?
Nothing usable could be built from that anchor. Anchors expire, so fetch a fresh one for every attempt and retry. The failed call is not charged.
What does it cost?
€6.00 per 1,000 successful reloads at list price and €4.00 at the top discount level. The version call and failed reloads are free.
Does the site need to be approved first?
No. Unlike the other solvers, tmpt is not tied to an approved domain, because we never touch the site.
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.
- Queue-it BotDeflector solverSolve the Queue-it BotDeflector challenge from a flow token and get a ready-to-send redeem request.
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.