PopularCaptchaToken
Solve a visible PopularCaptcha checkbox widget through your own proxy and receive the response token. With the request schema, an example and provider prices.
PopularCaptchaToken solves the visible PopularCaptcha checkbox widget ("I am human") through your proxy and returns the token that the page submits as h-captcha-response.

Use PopularCaptchaTokenProxyLess when the target does not compare the IP that solved the challenge with the IP that submits it.
Which PopularCaptcha task do I need?
| Widget | Solved through | Task type |
|---|---|---|
| Visible | Your proxy | PopularCaptchaToken (this task) |
| Visible | Provider network | PopularCaptchaTokenProxyLess |
| Invisible | Your proxy | PopularCaptchaInvisibleToken |
| Invisible | Provider network | PopularCaptchaInvisibleTokenProxyLess |
| Enterprise, visible | Your proxy | PopularCaptchaEnterpriseToken |
| Enterprise, visible | Provider network | PopularCaptchaEnterpriseTokenProxyLess |
| Enterprise, invisible | Your proxy | PopularCaptchaEnterpriseInvisibleToken |
| Enterprise, invisible | Provider network | PopularCaptchaEnterpriseInvisibleTokenProxyLess |
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 the request that submits the token. Use it as well when the solve has to come from a specific country.
Find the sitekey
The widget container carries the sitekey, a UUID, in data-sitekey:
<div data-sitekey="a5f74b19-9e45-40e0-b45d-47ff91b7a6c2" data-callback="onSuccess"></div>- Open DevTools and go to the Elements tab.
- Search (Ctrl + F) for
data-sitekey. - Copy the UUID. It is your
websiteKey.
![]()
Pages that render the widget from JavaScript pass it as sitekey to the widget's render() call. You can also find it as the sitekey parameter of the widget's network requests, or in the iframe src URL.
Test sitekeys are not real widgets
Test sitekeys such as 10000000-ffff-ffff-ffff-000000000001 exist for integration tests. They never challenge, so
there is nothing to solve.
Optional parameters
userAgent: the User-Agent of the browser you use on the target. Send it together withrqdata.rqdata: a single-use value that enterprise sites bind to the challenge. If the site sends one, seePopularCaptchaEnterpriseToken.extended: a passthrough object for provider-specific fields. See Steam.
If the widget has data-size="invisible" (or size: 'invisible' in the render() call), use PopularCaptchaInvisibleToken.
Steam (extended.gid)
Steam serves the widget on steampowered.com and steamcommunity.com. Pass a gid inside extended:
{ "extended": { "gid": "3399517004423014935" } }- Call
https://store.steampowered.com/join/refreshcaptcha/. - Read the
gidstring from the response. - Pass it as
extended.gid, together with a proxy so the solve IP matches the IP that submits the token.
Provider support
extended is forwarded as-is, and only EZ-Captcha reads it. Other providers ignore it.
Use the token
Submit solution.token as the h-captcha-response field of the form. After a successful challenge, the widget adds that field to the form submission. Send the returned userAgent as the User-Agent of your request when the solution has one.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
2Captcha | $2.99 | |
Anti-Captcha | $2.00 | |
VoidSolver | $4.00 | |
OnyxSolver | $10.00 | |
EZCaptcha | $3.00 | |
Viper | $0.70 | |
Razorcap | $5.00 | |
Jett | $1.00 | |
Scarnox | $0.65 | |
DraxonSolver | $2.00 | |
SCTG | $0.65 | |
SwiftSolve | $7.00 | |
Raze | $12.00 | |
VoidCaptcha | $3.00 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in a workspace of the AnySolver dashboard. Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See Tasks for per-task schemas. View task properties |
settings | object | No | 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:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
websiteURL* | URL | Yes | Full URL of the page where the CAPTCHA is displayed. Example: |
websiteKey* | string | Yes | The sitekey found in the CAPTCHA HTML element on the target page. Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
userAgent | string | No | Browser User-Agent string. Must match the browser used on the target page. Not all providers properly support this parameter. Verify the compatibility with the provider you are using. |
rqdata | string | No | Custom data some PopularCaptcha Enterprise sites bind to the challenge, usually seen as rqdata in the captcha network requests or as captcha_rqdata in the site API response (for example Cord). It is single-use: read it fresh for every solve, and send the same userAgent you use on the target site. Example: |
extended | Record<string, unknown> | No | Provider-specific passthrough object, forwarded to the provider as-is. Only supported by EZ-Captcha; ignored by every other provider. For Steam targets it must include a Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "PopularCaptchaToken",
"websiteURL": "https://example.com/login",
"websiteKey": "a5f74b19-9e45-40e0-b45d-47ff91b7a6c2",
"proxy": "http://user:pass@1.2.3.4:8080"
}
}Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes |
Example: | |
taskId | string | No | Unique identifier returned when the task was created. Example: |
errorCode | No | Machine-readable error code. Example: | |
errorDescription | string | No | Human-readable error message with resolution hints. Example: |
cost | number | No | Actual cost charged for this task in USD. Example: |
taskType | No | The type of CAPTCHA task to solve. Example: | |
provider | No | Provider that handled this task. While processing, the provider currently solving it. Example: | |
solution | object | No |
Solution Object Properties
The solution field contains an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
token* | string | Yes | The solved CAPTCHA token to submit with your form. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent string used during solving. |