reCAPTCHA v3 for Ticketmaster

A reCAPTCHA v3 token for Ticketmaster, minted at a 0.9 score.

Scope recaptcha:tmstd

PriceSelf-serve

$3.00per 1,000 successful solves

POSThttps://api.cyxkit.app/v1/recaptcha/tmstd

Your key: Your key goes in the X-API-Key header. Nothing else is read: an Authorization header is ignored.
Key in the body: A top-level clientKey field in the body is refused with 400 bad_request. The header is the only place a key goes.
Method: Every route is a POST with Content-Type: application/json.
Body limit: A request body is at most 1 MiB.
What is charged: A failure is not charged. The price is held when the call starts and charged only when the answer proves a success; anything else is given back in full before the answer reaches you.

Request

Send these as JSON in the body. Required means a first call will not work without it, and a missing one comes back as the solver's own 400 naming the field.

Request fields for POST /v1/recaptcha/tmstd
Field	Needed	What it is
websiteUrl	Required	The Ticketmaster page the token is for, as a browser would load it.
sitekey	Required	The reCAPTCHA site key on that page.
action	Required	The action the page asks reCAPTCHA for.

Example call

curl -X POST 'https://api.cyxkit.app/v1/recaptcha/tmstd' \
  -H "X-API-Key: $CYXKIT_KEY" \
  -H 'Content-Type: application/json' \
  -d '{"websiteUrl": "https://www.ticketmaster.com/", "sitekey": "SITE_KEY", "action": "ACTION"}'

It reads your key from $CYXKIT_KEY, so the line you copy holds no secret. Set it first with export CYXKIT_KEY='PASTE_YOUR_KEY'.

Response

One success and two refusals. Which refusal you get says who turned the call down.

Success

{
  "status": "success",
  "token": "..."
}

This is the only answer that is charged.

Refused by the solver

{
  "status": "error",
  "errorCode": "...",
  "errorDescription": "..."
}

The solver refused the request as sent. Its own 400, 404 or 413 and its own body come back unchanged, and a failure is not charged.

Refused by cyxkit

{
  "error": "<code>",
  "status": <int>
}

cyxkit refused the call. A few codes add one field of their own, and there is no message or attempted field.

On every answer

The headers to read off a response, and what is true of this route only.

Headers on every answer
Header	What it carries
X-Cyxkit-Request-Id	On every answer. Quote it when you ask for help.
X-Charge-Micros	What this call cost, and 0 when it cost nothing. Money is micro-USD: 1 USD is 1,000,000.
X-Balance-Micros	Your available balance after the call, whenever cyxkit has a reading for it.
X-RateLimit-Limit	Your key’s per-minute limit. A key with no per-minute limit gets no `X-RateLimit` header at all.
X-RateLimit-Remaining	What is left of that limit. It comes back with the limit, for a key that has one.

Only on this route

This is reCAPTCHA v3 scoring for Ticketmaster: a 0.9-score token. It carries no cookie and mints no tmpt.
Branch on status, not on errorId: this route’s success and failure carry no errorId at all, so reading a missing one as zero would read a failure as a success.
A missing field is a 400 that names the field, passed back to you as the solver wrote it.

Get a key and top up

Sign in with Discord, add funds with crypto, then call /v1/tmpt or /v1/recaptcha/tmstd. If you need more than 300 requests a minute, ask about Unlimited.

Get started Sign up with Discord Ask about Unlimited (opens in a new tab)