How to Bypass GeeTest v3 Captcha

Introduction

If you are automating interactions with websites protected by GeeTest version 3 captcha, this guide will help you set up integration with the 2Captcha service.

GeeTest V3 is a protection system that uses interactive tasks (most often a slider puzzle) combined with behavioral analysis. The key feature of version 3 is the dynamic challenge parameter, which changes for each session and requires obtaining a new value before every API request.

In this article, we will cover both methods of sending tasks: without proxy (GeeTestTaskProxyless) and with proxy (GeeTestTask), and show current JSON request examples.

General Information

What Is GeeTest V3

GeeTest V3 is a popular captcha system that combines a visual task with user behavior analysis. Key features:

• Dynamic challenge parameter that must be extracted for each session
• Static public key gt for each website
• Returns three tokens: geetest_challenge, geetest_validate, geetest_seccode
• Supports both proxyless and proxy modes

Task Types in 2Captcha API

GeeTest V3 Task Parameters

* Required only when using GeeTestTask task type

Environment Setup

Request Requirements

To work with the 2Captcha API, you will need:

• API key from your account dashboard at 2captcha.com
• HTTPS client for sending POST requests (curl, Postman, or a library in your language)
• Valid gt and challenge from the target site
• Full page URL where the captcha is displayed
• Proxy (optional, but recommended for stability)

Getting Your API Key

1. Log in to your 2Captcha account dashboard
2. Go to the account settings section
3. Copy your clientKey (API key)
4. For security, store the key in an environment variable, not in your code

Page Analysis

Finding the gt Parameter

The gt parameter is static and usually contained in the page source code.

Method 1: via DevTools

1. Open the target page in your browser
2. Press F12 to open developer tools
3. Go to the Elements tab
4. Find the initGeetest function call

Example JavaScript:

initGeetest({
    gt: "81388ea1fc187e0c335c0a8907ff2625",
    challenge: "2e2f0f65240058b683cb6ea21c303eea6n",
    // other parameters
});

The value of the gt field is the static site key.

Method 2: via Source Code

Use page search (Ctrl+F) to find the string gt: or data-geetest.

Getting the Dynamic challenge

The challenge parameter is single-use and dynamic. You must obtain a new one before every API request.

Method 1: via Network Tab

1. In DevTools, go to the Network tab
2. Refresh the page with the captcha
3. Filter requests by geetest or get.php
4. Find the request to api.geetest.com/get.php, the challenge parameter will be in the response or request parameters

Method 2: Programmatic Retrieval

Send a request to the endpoint that returns captcha initialization parameters. Usually this is:

GET https://api.geetest.com/get.php?gt=YOUR_GT&callback=geetest_123456

Important: do not cache the challenge value. After use, it becomes invalid.

Checking the websiteURL

Make sure you specify the full page URL, including the protocol:

• Correct: https://example.com/login
• Incorrect: example.com/login or /login

The API does not open the page itself, so it may be accessible only to authorized users, this will not prevent solving.

Implementation

Example Request: GeeTestTaskProxyless (without proxy)

Method: createTask
Endpoint: https://api.2captcha.com/createTask

{
  "clientKey": "YOUR_API_KEY",
  "task": {
    "type": "GeeTestTaskProxyless",
    "websiteURL": "https://example.com/login",
    "gt": "81388ea1fc187e0c335c0a8907ff2625",
    "challenge": "2e2f0f65240058b683cb6ea21c303eea6n"
  }
}

Example Request: GeeTestTask (with proxy)

{
  "clientKey": "YOUR_API_KEY",
  "task": {
    "type": "GeeTestTask",
    "websiteURL": "https://example.com/login",
    "gt": "81388ea1fc187e0c335c0a8907ff2625",
    "challenge": "2e2f0f65240058b683cb6ea21c303eea6n",
    "proxyType": "http",
    "proxyAddress": "1.2.3.4",
    "proxyPort": "8080",
    "proxyLogin": "user23",
    "proxyPassword": "p4$w0rd"
  }
}

Getting the Result

After creating the task, use the getTaskResult method to get the solution.

Endpoint: https://api.2captcha.com/getTaskResult

Request:

{
  "clientKey": "YOUR_API_KEY",
  "taskId": 74455221488
}

Successful Response:

{
  "errorId": 0,
  "status": "ready",
  "solution": {
    "geetest_challenge": "2e2f0f65240058b683cb6ea21c303eea6n",
    "geetest_validate": "a1b2c3d4e5f6g7h8i9j0",
    "geetest_seccode": "k1l2m3n4o5p6q7r8s9t0|jigsaw"
  },
  "cost": "0.00299",
  "ip": "1.2.3.4",
  "createTime": 1692863536,
  "endTime": 1692863556,
  "solveCount": 1
}

Using the Solution on the Target Site

You need to send the received parameters to the target site in the same format that the original form expects. Usually this includes:

• geetest_challenge
• geetest_validate
• geetest_seccode

These values are often passed in the POST request body or in headers. Intercept the original request via DevTools (Network tab) and reproduce it with the received tokens.

Parameter Explanations

Dynamic challenge

The challenge parameter is single-use. After the captcha is loaded on the page, this value becomes invalid.

Rule: obtain a new challenge before every request to the 2Captcha API.

To do this:

1. Analyze the target site network requests when the page loads
2. Find the request that returns a new challenge
3. Reproduce this request before creating a task in the API

Custom API Domain

Some sites use custom domains to load GeeTest scripts. If you see a domain other than api.geetest.com in the source code, specify it in the geetestApiServerSubdomain parameter:

{
  "clientKey": "YOUR_API_KEY",
  "task": {
    "type": "GeeTestTaskProxyless",
    "websiteURL": "https://example.com",
    "gt": "81388ea1fc187e0c335c0a8907ff2625",
    "challenge": "2e2f0f65240058b683cb6ea21c303eea6n",
    "geetestApiServerSubdomain": "api-na.geetest.com"
  }
}

Proxy Settings

If you are using the GeeTestTask task type, make sure that:

• The proxy supports HTTPS and does not require additional CAPTCHA confirmation
• All required fields are specified: proxyType, proxyAddress, proxyPort
• If authentication is required, proxyLogin and proxyPassword are correctly passed
• The proxy is located in the region expected by the target site

Handling API Errors

Common error codes:

Common Mistakes

Additional Resources

• GeeTest API Documentation - Full method specification
• Test Sandbox - Safe testing without deducting funds
• Request Examples on GitHub - Collection of examples in different languages
• Support - Create a ticket if you encounter technical issues

Checklist

• API key obtained and verified from 2Captcha account dashboard
• Static gt parameter extracted from the target site source code
• Dynamic challenge retrieval implemented before every request
• Custom domain specified in geetestApiServerSubdomain if used
• When using proxy, all fields checked: type, address, port, login, password
• Error handling added for errorId and errorCode codes
• Sending the received solution to the target site tested
• Logging of requests and responses configured for debugging

Conclusion

GeeTest V3 requires careful handling of the dynamic challenge parameter, which must be obtained anew before every API request. Unlike version 4, there is no simplified flow with captcha_id, but with proper implementation the integration remains stable.

The 2Captcha service supports two solving methods: GeeTestTaskProxyless for a quick start and GeeTestTask for cases where proxy control is required. Both methods return the same set of tokens: geetest_challenge, geetest_validate, geetest_seccode, which must be passed to the target site for verification.

Integration with 2Captcha allows you to delegate the complex part of bypassing captchas to a specialized service, focusing your efforts on your application logic. By following the parameters in this guide, you will be able to reliably solve GeeTest V3 on any website.