GeeTestV3Token
Solve GeeTest V3 through your proxy from the gt and challenge values and get the challenge, validate and seccode fields.
GeeTestV3Token solves GeeTest V3 through your proxy and returns the three values the site submits with the form: challenge, validate and seccode. GeeTest V3 is a behavioral CAPTCHA, such as a slider or click puzzle, that the page starts with initGeetest. The task takes the page URL, the static gt value and a fresh challenge.
Use this task when the site checks that the solve came from the same IP as your own requests. Otherwise use GeeTestV3TokenProxyLess, which takes the same parameters without a proxy. For the newer captcha_id based version, use GeeTestV4Token.
Find the parameters
Open DevTools, go to the Network tab and reload the page. The site registers the CAPTCHA before it renders the widget, and the response of that request carries the values:
gtis a static value that stays the same on every load. It is also in theinitGeetestcall.challengeis new on every load. It becomes invalid as soon as the widget has loaded with it, so you need your own request to the site's registration endpoint to get a fresh one for each task.
Request a new challenge for every task
A challenge can be used once. Reusing the value from a page you already loaded, or from an earlier task, makes the
solve fail.
Send the 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.
Optional parameters
geetestApiServerSubdomain: send it when the page loads the GeeTest scripts from a host other thanapi.geetest.com, for exampleapi-na.geetest.com. TheinitGeetestcall can also set it asapi_server.offlineandnewCaptcha: mirror theofflineandnew_captchaoptions in theinitGeetestconfiguration. Send them only when the page sets them totrue. Some providers ignore them.
Use the result
Submit the challenge, validate and seccode values from the solution exactly as returned. They are the geetest_challenge, geetest_validate and geetest_seccode fields that GeeTest's own widget posts to the site: either hidden inputs in the geetest_form element or the object from captchaObj.getValidate(). The challenge in the solution can differ from the one you sent, so use the returned value. The seccode is the validate value followed by |jordan.
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 | $1.80 | |
CapMonster | $1.20 | |
SolveCaptcha | $0.80 | |
VoidCaptcha | $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: |
gt* | string | Yes | Static GeeTest V3 Example: |
challenge* | string | Yes | Dynamic GeeTest V3 Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
geetestApiServerSubdomain | string | No | Optional GeeTest API server hostname, such as Example: |
offline | boolean | No | Set to Example: |
newCaptcha | boolean | No | Set to Example: |
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": "GeeTestV3Token",
"websiteURL": "https://2captcha.com/demo/geetest",
"gt": "81388ea1fc187e0c335c0a8907ff2625",
"challenge": "2e2f0f65240058b683cb6ea21c303eea6n",
"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 |
|---|---|---|---|
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
challenge | string | No | GeeTest Example: |
validate | string | No | GeeTest Example: |
seccode | string | No | GeeTest Example: |