Skip to Content
AnySolver logo
AnySolver
Token

HuntCaptchaToken

Solve the Hunt CAPTCHA through your proxy after the target site returns a CAPTCHA error with meta.token. With the schema, an example and provider prices.

HuntCaptchaToken solves the Hunt CAPTCHA through your proxy and returns the solution to submit to the site. It is the second step of the Hunt flow: use it after the site has answered a request with a "Captcha error" (code 113) whose body has a meta.token value, and pass that value as data.

For the first step, which generates the X-HD fingerprint, see HuntXHDToken.

Run the Hunt flow

Create a HuntXHDToken task and read the X-HD value from solution.token.
Call the protected site with that X-HD value, through the same proxy.

If the error response contains meta.token, create a HuntCaptchaToken task with that value as data.

Submit the solution from getTaskResult back to the site.

Find the parameters

  1. Send a real action request to the site, for example a send-code or login request, with the X-HD header.
  2. Open the failed response in DevTools.
  3. Copy meta.token from the response body and send it as data.

apiGetLib is the same api.js URL you used for HuntXHDToken. See Find apiGetLib.

Send the proxy

task.proxy is required on this task type. Use the same proxy for the X-HD task, your requests to the site and this task, and keep one IP for the whole flow: see Keep the same IP for the whole solve. If the proxy changes, generate a new X-HD first.

Use the solution

For HuntCaptchaToken, solution.token is the CAPTCHA solution, not the X-HD fingerprint. Submit it to the site to confirm the blocked action. HuntXHDToken returns the fingerprint you use before the CAPTCHA appears, and HuntCaptchaToken returns the answer you use after it escalates.

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

Supported Providers

ProviderPrice per 1,000Routing
2Captcha
$2.99
CapMonster
$1.00
SCTG
$0.24
VoidCaptcha
$1.50

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://example.com/

apiGetLib*
URLYes

Full URL of the Hunt api.js file. Find it in DevTools by searching the network requests or the page for hd-api or api.js.

Example: https://example.com/hd-api/external/apps/app-id/api.js

data*
stringYes

The meta.token value from the site response that returned the captcha error.

Example: kufyHK/s/j...wIW

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

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.

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

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "HuntCaptchaToken",
        "websiteURL": "https://example.com/",
        "apiGetLib": "https://example.com/hd-api/external/apps/app-id/api.js",
        "data": "kufyHK/s/j...wIW",
        "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
token*
stringYes

HuntXHDToken: the X-HD fingerprint to send with requests to the target site. HuntCaptchaToken: the captcha solution to submit to the target site.

Example: 6IyDCCpDd.../z/kLNSpjewI=

raw
Record<string, unknown>No

Raw provider response data for advanced use cases.

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