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
HuntXHDToken task and read the X-HD value from solution.token.If the error response contains meta.token, create a HuntCaptchaToken task with that value as data.
getTaskResult back to the site.Find the parameters
- Send a real action request to the site, for example a send-code or login request, with the X-HD header.
- Open the failed response in DevTools.
- Copy
meta.tokenfrom the response body and send it asdata.
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
| Provider | Price per 1,000 | Routing |
|---|---|---|
2Captcha | $2.99 | |
CapMonster | $1.00 | |
SCTG | $0.24 | |
VoidCaptcha | $1.50 |
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: |
apiGetLib* | URL | Yes | Full URL of the Hunt Example: |
data* | string | Yes | The 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. Example: |
{
"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
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 |
Example: |
raw | Record<string, unknown> | No | Raw provider response data for advanced use cases. |
{
"status": "ready",
"errorId": 0,
"solution": {
"token": "6IyDCCpDd.../z/kLNSpjewI="
}
}