PopularCaptchaEnterpriseToken
Solve a visible PopularCaptcha Enterprise widget through your own proxy, including rqdata-bound challenges. With the schema, an example and provider prices.
PopularCaptchaEnterpriseToken solves a visible PopularCaptcha Enterprise widget through your proxy and returns the token the page submits as h-captcha-response. Enterprise widgets look like the standard widget, but the site can bind each challenge to a single-use rqdata value, and can compare the solve with the request that submits it.
Use PopularCaptchaEnterpriseTokenProxyLess when the target does not compare the IP that solved the challenge with the IP that submits it.
The sitekey comes from the widget container as in PopularCaptchaToken. Enterprise test sitekeys such as 20000000-ffff-ffff-ffff-000000000002 never present a challenge. The Steam gid in extended works as in PopularCaptchaToken.
Which PopularCaptcha task do I need?
| Widget | Solved through | Task type |
|---|---|---|
| Visible | Your proxy | PopularCaptchaToken |
| Visible | Provider network | PopularCaptchaTokenProxyLess |
| Invisible | Your proxy | PopularCaptchaInvisibleToken |
| Invisible | Provider network | PopularCaptchaInvisibleTokenProxyLess |
| Enterprise, visible | Your proxy | PopularCaptchaEnterpriseToken (this task) |
| 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.
The rqdata parameter
rqdata is a value the target generates for each challenge. It appears as rqdata in the CAPTCHA network requests, or in the site's own API response. Send it as rqdata, together with the userAgent you use on the target site, and read it fresh for every solve.
Cord returns it in a 400 response when a request needs a CAPTCHA:
{
"captcha_key": ["captcha-required"],
"captcha_sitekey": "a9b5fb07-92ff-493f-86fe-352a2803b3df",
"captcha_service": "xxx",
"captcha_session_id": "eae1f083-0ff6-4e94-a4da-d7aaaa55898b",
"captcha_rqdata": "rX5Jrmm4ylfrnE8lx2COFH83kzM058+EHak3N+1eegOF70r...",
"captcha_rqtoken": "Ikx3bjdxNTBDVUptUzBScWdHYzZRSVRabjUzUUw2U0JOR3ppemd..."
}Send captcha_sitekey as websiteKey and captcha_rqdata as rqdata.

Use the token
Submit solution.token as the h-captcha-response field, as described in Use the token. Send the returned userAgent as the User-Agent of your request when the solution has one. If the site rejects the token, check that the proxy kept one IP for the whole solve, then that websiteKey and rqdata come from the same challenge.
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 | |
RiskBypass | $6.00 | |
VoidSolver | $4.00 | |
OnyxSolver | $10.00 | |
EZCaptcha | $3.00 | |
Razorcap | $10.00 | |
Jett | $4.00–$10.00 | |
Scarnox | $3.00 | |
CaptchaHeaven | $10.00 | |
DraxonSolver | $7.00 | |
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": "PopularCaptchaEnterpriseToken",
"websiteURL": "https://example.com/login",
"websiteKey": "20000000-ffff-ffff-ffff-000000000002",
"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. |