Skip to Content
AnySolver logo
AnySolver
Token

KasadaCtBrowserToken

Solve Kasada in a real browser behind your proxy and get the x-kpsdk header set to replay. Shows the request schema, an example and provider prices.

KasadaCtBrowserToken solves Kasada in a real browser through your proxy and returns the x-kpsdk-* headers to replay on the protected endpoint. The provider opens the fingerprint page through the proxy you give it and completes the /tl exchange there.

Use KasadaCtBrowserTokenProxyLess when the target accepts a session solved from the provider network.

Which Kasada task do I need?

What you wantTask
You have the p.js URL and want headers to replay, solved from the provider networkKasadaTokenProxyLess
You want a real-browser solve, from the provider networkKasadaCtBrowserTokenProxyLess
You want a real-browser solve through your own proxyKasadaCtBrowserToken (this task)
You fetched ips.js and post /tl yourself, and want the ct, dt, im and v headersKasadaPayloadProxyLess
You fetched ips.js and post /tl yourself, and want the ct and dt headersKasadaTlPayloadProxyLess
You hold a session and its x-kpsdk-ct, x-kpsdk-st and x-kpsdk-fc, and want x-kpsdk-cdKasadaCdToken
You hold x-kpsdk-st and the User-Agent, and want x-kpsdk-cdKasadaWorkTimeProxyLess

Use your proxy

task.proxy is required on this task type. The provider solves from that address, and the proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve. Use the same proxy for every request that replays the result.

Find the paths

Open DevTools on the protected page and look for the Kasada path, which has the form /149e9513-01fa-4fb0-aad4-566afd725d1b/2d206a39-8ed7-437e-a3be-862e0f06eea3/:

FieldWhere to find it
pJsPathThe path, not the full URL, of the p.js script. Filter the Network tab for p.js.
fpHostThe hostname of the p.js request: the target domain, unless the site serves p.js from another host.
tlHostThe hostname the /tl request goes to. It differs from fpHost when the target is an API subdomain.

On Twitch, the page is passport.twitch.tv and /tl goes to gql.twitch.tv, so fpHost is passport.twitch.tv and tlHost is gql.twitch.tv.

userAgent is optional. If you set it, also set uaVersion to its major Chrome version, and use that same User-Agent for your requests. cdConstant is an optional hex string used as the constant of the x-kpsdk-cd proof-of-work, for sites that require one.

Replay the headers

Send the headers of solution.headers on the protected request, except x-kpsdk-v. x-kpsdk-ct is always present, while x-kpsdk-h and x-kpsdk-cd appear only when the site's Kasada script issues them. Replay the headers you receive instead of expecting a fixed list.

Do not send x-kpsdk-v to the protected endpoint

x-kpsdk-v belongs on the /tl request only. Forwarding it to the protected endpoint is a common reason a valid token is still refused.

When the solution includes user-agent and sec-ch-ua, send them with the request. Send the returned user-agent from a client whose TLS fingerprint matches the same Chrome version.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
RiskBypass
$1.00
Nslsolver
$1.50
VoidCaptcha
$2.00

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

Per-request settings for routing, Auto Retry, Auto Fallback, proxy reuse, response statistics and detailed analytics. Each field overrides the API key's value. See Routing modes.

View settings reference

Task Object Properties

The task field accepts an object with the following properties:

FieldTypeRequiredDescription
type*
Yes
websiteURL*
URLYes

Full URL of the page where the CAPTCHA is displayed.

Example: https://passport.twitch.tv

pJsPath*
stringYes

Path of Kasada's p.js script on the target site, starting with /. In DevTools, filter the Network tab for p.js and copy its path.

Example: /149e9513-01fa-4fb0-aad4-566afd725d1b/2d206a39-8ed7-437e-a3be-862e0f06eea3/p.js

fpHost*
stringYes

Hostname serving the Kasada fingerprint page: the Host of the p.js request. This is usually the target domain.

Example: passport.twitch.tv

tlHost*
stringYes

Hostname of the Kasada /tl token endpoint: the Host of the /tl request. It can differ from fpHost when the protected target is an API subdomain.

Example: gql.twitch.tv

proxy*
string | objectYes

Proxy the provider solves through, as a string or an object. See Proxy configuration.

View proxy configuration

Example: http://user:pass@1.2.3.4:8080

userAgent
stringNo

The User-Agent string to use during solving. It must match the browser used for your subsequent requests to the protected site.

Example: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36

uaVersion
numberNo

Major Chrome version of userAgent, for example 144 for Chrome 144. It must match the User-Agent.

Example: 144

cdConstant
stringNo

Optional hex string used as the constant of the x-kpsdk-cd proof-of-work, for sites that require one.

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "KasadaCtBrowserToken",
        "websiteURL": "https://passport.twitch.tv",
        "pJsPath": "/149e9513-01fa-4fb0-aad4-566afd725d1b/2d206a39-8ed7-437e-a3be-862e0f06eea3/p.js",
        "fpHost": "passport.twitch.tv",
        "tlHost": "gql.twitch.tv",
        "proxy": "http://user:pass@1.2.3.4:8080"
    }
}

Optional fields are not guaranteed across providers

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
headers*
objectYes

Kasada headers returned by the provider. Include these headers in your subsequent requests to the protected site.

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.