Your first solution
Generate a token, header set, or cookie in one request and submit it with the identity it was issued for.
quickstart
base url
https://api.solvethree.com/v1
auth
Authorization: Bearer <key>
Complete Markdown integration reference.
Generate a token
POST /v1/tasks · 201
curl https://api.solvethree.com/v1/tasks \
-H "Authorization: Bearer $SOLVETHREE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"site": "accounts.example.com",
"action": "login",
"proxy": "http://user:[email protected]:8080",
"requestId": "login_20260910_0001"
}'{
"id": "login_20260910_0001",
"status": "ready",
"solution": {
"token": "03AFcWeA5…kQ2b",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) …",
"secChUa": "\"Chromium\";v=\"140\", \"Not=A?Brand\";v=\"24\""
},
"durationMs": 1742
}The create request waits up to 15 seconds and normally returns the finished token. The site must have an active profile in this workspace. A site assigned to your unlimited plan is included; every other site reserves one pay-as-you-go credit.
Optional fields (proxy or proxyCandidates is required)
- recaptchaType
- Use "v3" for regular v3. Omit it for the backward-compatible "enterprise-v3" default.
- requestId
- Your own idempotency key, 1–64 chars. Re-sending it returns the same task.
- proxyCandidates
- Up to six distinct HTTP(S) proxies. solution.egressAttempts is the winning candidate's one-based index. Sessions require a single proxy.
- userAgent, secChUa
- Pin the browser identity you will use with the token.
- timezoneOffsetMinutes
- Match the timezone of the client that submits the token.
- session
- Keep a session across tasks for flows with several steps.
Generate Kasada headers
$1.25 per 1,000 · failed jobs refunded
curl https://api.solvethree.com/v1/tasks \
-H "Authorization: Bearer $SOLVETHREE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "KasadaTask",
"url": "https://www.ticketmaster.com/discovery/v2/events",
"proxy": "http://user:[email protected]:8080"
}'{
"id": "req_92ad…",
"status": "ready",
"solution": {
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) …",
"secChUa": "\"Chromium\";v=\"151\", \"Google Chrome\";v=\"151\"",
"headers": {
"x-kpsdk-ct": "…",
"x-kpsdk-cd": "…",
"x-kpsdk-h": "…",
"x-kpsdk-v": "…"
},
"egressAttempts": 1
}
}Standalone Kasada currently supports HTTPS targets on www.ticketmaster.com. Apply every returned header immediately with the returned browser identity and successful proxy. Header sets are target-, identity-, and egress-bound. Assign Kasada to an unlimited-plan slot to include these tasks in your plan.
Generate Ticketmaster TMPT
$0.99 per 1,000 · failed jobs refunded
curl 'https://api.solvethree.com/v1/tasks?waitMs=75000' \
-H "Authorization: Bearer $SOLVETHREE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"type": "TicketmasterTmptTask",
"url": "https://www.ticketmaster.com/example/event/1A2B3C4D5E6F7A8B",
"action": "Event",
"proxy": "http://user:[email protected]:8080"
}'{
"id": "req_7f4c…",
"status": "ready",
"solution": {
"token": "tmpt-cookie-value…",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) …",
"secChUa": "\"Chromium\";v=\"151\", \"Google Chrome\";v=\"151\"",
"egressAttempts": 1
},
"durationMs": 2310
}The Ticketmaster URL is required; the request ID is not. Use actionEvent with the exact event URL and Login with the sign-in entry URL. TMPT creation is asynchronous by default. Set the URL query parameter waitMs=75000 to wait up to 75 seconds, then inspect the task status and poll if it remains nonterminal. The token is the raw tmpt cookie value. Assign Ticketmaster TMPT to an unlimited-plan slot to include these tasks in your plan.
Async fallback
GET /v1/tasks/:id · 200
curl https://api.solvethree.com/v1/tasks/login_20260910_0001 \
-H "Authorization: Bearer $SOLVETHREE_API_KEY"{
"id": "login_20260910_0001",
"status": "ready",
"solution": {
"token": "03AFcWeA5…kQ2b",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) …",
"secChUa": "\"Chromium\";v=\"140\", \"Not=A?Brand\";v=\"24\""
},
"durationMs": 1742
}Most integrations never need this request. Use it only if the create response remains pending or solving after its synchronous window, or to recover an idempotent task after a connection interruption. Kasada waits up to 75 seconds and reCAPTCHA uses 15 seconds. TMPT creation is asynchronous by default; an explicit TMPT waitMs may be up to 75 seconds.
Handle failures
status · failed
{
"id": "login_20260910_0001",
"status": "failed",
"errorCode": "site-unreachable",
"error": "target page did not respond",
"durationMs": 9210
}Identity included
The token ships with the userAgent and secChUa it was issued for. Send them together.
Failed solves are free
A task that ends in failed is refunded to your balance automatically.
Secret-safe
Tokens, cookies, proxies, and fingerprints stay out of task listings and logs.