TMPT vs Kasada: which Ticketmaster task do you need?
Use TicketmasterTmptTask when you need a tmpt cookie. Use KasadaTask when you need Kasada headers. A reCAPTCHA check needs a separate token. These outputs aren't interchangeable: renaming a token field won't turn it into a cookie or a header set.
On this page
Choose by what the target request needs
| Product | Request fields | Output | Supported scope |
|---|---|---|---|
| Ticketmaster TMPT | type: TicketmasterTmptTask, exact target url, action: Event or Login, and a proxy input | Raw tmpt cookie value | Ticketmaster Event and Login tasks |
| Kasada | type: KasadaTask, url, and a proxy input | headers object and browser identity | Standalone Kasada currently supports HTTPS targets on www.ticketmaster.com |
| reCAPTCHA | site hostname, action, and a proxy input; no type or url | reCAPTCHA token | Standard v3 and Enterprise v3 |
All three products require a customer-supplied HTTP(S) proxy.
All three use the same task API: create with POST /v1/tasks and retrieve with GET /v1/tasks/:id. Authenticate with a workspace API key in the Bearer authorization header, and keep that key on your server.
Kasada: request and apply the header set
{
"type": "KasadaTask",
"url": "https://www.ticketmaster.com/discovery/v2/events",
"proxy": "http://user:[email protected]:8080",
"requestId": "example_kasada_001"
}Set url to the intended supported target and replace the example proxy. requestId is optional. Don't add site, action, recaptchaType, session or custom browser identity fields to a Kasada request.
Apply the returned headers together, using the returned browser identity and the successful proxy egress for the intended target. Don't extract one header and treat it as a TMPT cookie or reCAPTCHA token.
Kasada creation waits up to 75 seconds by default, so allow for that wait plus network overhead in your client timeout. See the Kasada headers integration for the complete flow.
One successful solve may not satisfy the next check
A workflow may involve several checks. If a request needs both a TMPT cookie and Kasada headers, solving either task alone doesn't provide the other output. If it also presents a reCAPTCHA check, that requires a separate token. Don't request all three by default; identify what the failing request actually needs.
Before paying for another solve, inspect the outgoing request. Is the TMPT value being sent as the tmpt cookie? Are the Kasada headers applied together? Is a reCAPTCHA token being sent where the target expects it? A ready task means a solution was generated, not that Ticketmaster accepted the request. For a rejected result, continue with diagnosing a Ticketmaster 403.
Sources and API reference
Run your first task.
Start with $5 in workspace credit.