XCaptchaToken
Solve an xCaptcha widget through your own proxy and get the passcode the target form expects. Shows the request schema, an example and provider prices.
XCaptchaToken solves an xCaptcha widget through your proxy from the page URL and the sitekey, and returns the passcode that the form submits and the site verifies server-side. The challenge is a code-assembly puzzle: a distorted string is drawn across a noisy banner, and the visitor picks the two tiles below that, joined in order, spell it.

Recognize the widget
The markup from xCaptcha's installation guide is distinctive:
<div id="__xCaptchaDiv" data-sitekey="SITE_KEY" style="min-height:75px!important"></div>
<script src="https://static.xcaptcha.com/js/api.js"></script>The tells are the __xCaptchaDiv container, the static.xcaptcha.com/js/api.js script, and the xcaptcha_response input the widget injects into the form.
An invisible integration hides the div with display:none and starts the challenge from JavaScript with window.__xcaptcha.check(callback). This task solves both.
Use your proxy
task.proxy is required on this task type, and the provider solves from that address. The proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve. Submit the form from the same address.
Find the parameters
websiteKeyis the sitekey. It is public, so it is always in the page: read thedata-sitekeyattribute of the#__xCaptchaDivcontainer. For an invisible widget, search the page source forsitekey: the value is in the same attribute or in the script's init call. As a fallback, watch the Network tab while the widget loads: the key appears in the requests toxcaptcha.com.websiteURLis the full URL of the page that renders the widget, not the endpoint you post the form to.
The sitekey is a 32-character hex string, for example 11aa62606fb968f3674742df60598957. Do not send the private key: it belongs to the site's server and is never needed here.
Submit the passcode
Send solution.token as the form's xcaptcha_response field. That is the default input name. A custom integration can rename it, so confirm the name against a manual submission.
Passcodes are single-use and expire, so solve as part of the request that consumes the token instead of building a pool in advance. A stale or reused passcode shows up as a generic CAPTCHA failure message on the form. If the form rejects the passcode, check that the proxy kept one IP for the whole solve, then that websiteKey and websiteURL come from the page that shows the widget.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
CapCracker | $1.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: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "XCaptchaToken",
"websiteURL": "https://example.com/page",
"websiteKey": "11aa62606fb968f3674742df60598957",
"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. |