HuntCaptchaToken

Solve Hunt CAPTCHA after the target website returns a captcha error and meta.token.

HuntCaptchaToken is the second step of the Hunt flow. Use it only after the website has already escalated the session and returned a response containing meta.token.

For the initial fingerprint step, see HuntXHDToken.

This task is not for initial setup

If you only need to generate the X-HD fingerprint, use HuntXHDToken and do not send the data field.

When to use HuntCaptchaToken

Use this task only when the target site responds with a captcha error similar to this:

{
    "errors": [{ "code": "113", "title": "Captcha error" }],
    "meta": {
        "token": "SITE_META_TOKEN"
    }
}

The value of meta.token must be passed into task.data.

Full Hunt workflow

Create HuntXHDToken and get the X-HD value from solution.token.

Call the protected website with the same proxy and X-HD value.

Read the error response. If the site returns meta.token, create HuntCaptchaToken.

Submit the final solution from getTaskResult back to the website.

Proxy consistency matters

Use the same proxy across X-HD generation, the protected site request, and Hunt CAPTCHA solving. If the proxy changes, generate a new X-HD first.

How to obtain `meta.token`

The typical pattern looks like this:

Send a real site action request, for example SMS send-code or login.
Include the X-HD value generated from HuntXHDToken.
Inspect the failed response in DevTools.
Copy meta.token from the response payload and pass it as task.data.

The image below shows where to obtain both values during the real site flow:

the request headers contain the X-Hd value generated in the first step
the failed response body contains meta.token, which you must copy into task.data

Where to find Hunt X-HD and meta.token in DevTools

What `solution.token` means here

For HuntCaptchaToken, the returned solution.token is the final Hunt captcha solution, not the X-HD fingerprint. Submit this token back to the target website to confirm the blocked action.

That means:

HuntXHDToken returns the X-HD fingerprint used before escalation
HuntCaptchaToken returns the captcha answer used after escalation

Supported Providers

Provider	Price per 1,000
CapMonster	$1.00

Request Schema

Field	Type	Description
`clientKey`*	string	Your API key from the AnySolver dashboard. Example: `your-api-key-from-dashboard`
`task`*	object	View task properties →
`provider`		Specific provider to use. If omitted, automatic routing selects the best provider. Example: `CapSolver`
`selectionMode`		Read more at the routing strategies docs. Example: `autoCheapest`
`keyPoolMode`		Example: `all`

Task Object Properties

The task field accepts an object with the following properties:

Field	Type	Description
`websiteURL`*	URL	Full URL of the page where the CAPTCHA is displayed. Example: `https://example.com/`
`apiGetLib`*	URL	Full URL to api.js. Find in DevTools via hd-api or api.js. Example: `https://example.com/hd-api/external/apps/a2157wab1045d68672a63557e0n2a77edbfd15ea/api.js`
`userAgent`	string	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.
`data`*	string	meta.token from site response when it returns Captcha error. Example: `kufyHK/s/jTNU...AfwIW`
`proxy`*	string \| object	View proxy configuration →

Response Schema

Field	Type	Description
`status`*		Task status: "processing", "ready", or "failed". Example: `ready`
`taskId`	string	Unique identifier returned when the task was created. Example: `01KFNDF328KAN2AJ3BNHCQYE88`
`errorId`*		0 = success, 1 = external error, 2 = internal error. Example: `0`
`errorCode`		Machine-readable error code (e.g., "CAPTCHA_UNSOLVABLE"). Example: `CAPTCHA_UNSOLVABLE`
`errorDescription`	string	Human-readable error message with resolution hints. Example: `The captcha could not be solved.`
`cost`	number	Actual cost charged for this task in USD. Example: `0.002`
`taskType`		The type of CAPTCHA task to solve. Example: `ReCaptchaV2TokenProxyLess`
`provider`		Specific provider to use. If omitted, automatic routing selects the best provider. Example: `Multibot`
`solution`	object	View solution properties →

Solution Object Properties

The solution field contains an object with the following properties:

Field	Type	Description
`token`*	string	X-HD fingerprint or CAPTCHA solution token to submit to the target site. Example: `6IyDCCpDdSK...YGs1Wug/z/kLNSpjewI=`
`raw`	Record<string, unknown>	Raw provider response data for advanced use cases.

Example Response

{    "status": "ready",    "errorId": 0,    "solution": {        "token": "6IyDCCpDdSK...YGs1Wug/z/kLNSpjewI="    }}

HuntCaptchaToken is the second step of the Hunt flow. Use it only after the website has already escalated the session and returned a response containing meta.token.

For the initial fingerprint step, see HuntXHDToken.

This task is not for initial setup

If you only need to generate the X-HD fingerprint, use HuntXHDToken and do not send the data field.

When to use HuntCaptchaToken

Use this task only when the target site responds with a captcha error similar to this:

{
    "errors": [{ "code": "113", "title": "Captcha error" }],
    "meta": {
        "token": "SITE_META_TOKEN"
    }
}

The value of meta.token must be passed into task.data.

Full Hunt workflow

Create HuntXHDToken and get the X-HD value from solution.token.

Call the protected website with the same proxy and X-HD value.

Read the error response. If the site returns meta.token, create HuntCaptchaToken.

Submit the final solution from getTaskResult back to the website.

Proxy consistency matters

Use the same proxy across X-HD generation, the protected site request, and Hunt CAPTCHA solving. If the proxy changes, generate a new X-HD first.

How to obtain `meta.token`

The typical pattern looks like this:

Send a real site action request, for example SMS send-code or login.
Include the X-HD value generated from HuntXHDToken.
Inspect the failed response in DevTools.
Copy meta.token from the response payload and pass it as task.data.

The image below shows where to obtain both values during the real site flow:

the request headers contain the X-Hd value generated in the first step
the failed response body contains meta.token, which you must copy into task.data

Where to find Hunt X-HD and meta.token in DevTools

What `solution.token` means here

For HuntCaptchaToken, the returned solution.token is the final Hunt captcha solution, not the X-HD fingerprint. Submit this token back to the target website to confirm the blocked action.

That means:

HuntXHDToken returns the X-HD fingerprint used before escalation
HuntCaptchaToken returns the captcha answer used after escalation

Supported Providers

Provider	Price per 1,000
CapMonster	$1.00

Request Schema

Field	Type	Description
`clientKey`*	string	Your API key from the AnySolver dashboard. Example: `your-api-key-from-dashboard`
`task`*	object	View task properties →
`provider`		Specific provider to use. If omitted, automatic routing selects the best provider. Example: `CapSolver`
`selectionMode`		Read more at the routing strategies docs. Example: `autoCheapest`
`keyPoolMode`		Example: `all`

Task Object Properties

The task field accepts an object with the following properties:

Field	Type	Description
`websiteURL`*	URL	Full URL of the page where the CAPTCHA is displayed. Example: `https://example.com/`
`apiGetLib`*	URL	Full URL to api.js. Find in DevTools via hd-api or api.js. Example: `https://example.com/hd-api/external/apps/a2157wab1045d68672a63557e0n2a77edbfd15ea/api.js`
`userAgent`	string	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.
`data`*	string	meta.token from site response when it returns Captcha error. Example: `kufyHK/s/jTNU...AfwIW`
`proxy`*	string \| object	View proxy configuration →

Response Schema

Field	Type	Description
`status`*		Task status: "processing", "ready", or "failed". Example: `ready`
`taskId`	string	Unique identifier returned when the task was created. Example: `01KFNDF328KAN2AJ3BNHCQYE88`
`errorId`*		0 = success, 1 = external error, 2 = internal error. Example: `0`
`errorCode`		Machine-readable error code (e.g., "CAPTCHA_UNSOLVABLE"). Example: `CAPTCHA_UNSOLVABLE`
`errorDescription`	string	Human-readable error message with resolution hints. Example: `The captcha could not be solved.`
`cost`	number	Actual cost charged for this task in USD. Example: `0.002`
`taskType`		The type of CAPTCHA task to solve. Example: `ReCaptchaV2TokenProxyLess`
`provider`		Specific provider to use. If omitted, automatic routing selects the best provider. Example: `Multibot`
`solution`	object	View solution properties →

Solution Object Properties

The solution field contains an object with the following properties:

Field	Type	Description
`token`*	string	X-HD fingerprint or CAPTCHA solution token to submit to the target site. Example: `6IyDCCpDdSK...YGs1Wug/z/kLNSpjewI=`
`raw`	Record<string, unknown>	Raw provider response data for advanced use cases.

Example Response

{    "status": "ready",    "errorId": 0,    "solution": {        "token": "6IyDCCpDdSK...YGs1Wug/z/kLNSpjewI="    }}

HuntCaptchaToken

When to use HuntCaptchaToken

Full Hunt workflow

How to obtain `meta.token`

What `solution.token` means here

Supported Providers

Request Schema

Task Object Properties

Response Schema

Solution Object Properties

Example Response

On this page

HuntCaptchaToken

When to use HuntCaptchaToken

Full Hunt workflow

How to obtain `meta.token`

What `solution.token` means here

Supported Providers

Request Schema

Task Object Properties

Response Schema

Solution Object Properties

Example Response

On this page