Documentation menu

GeeTestTaskProxyless: solve captcha from without proxy

This type of task solves GeeTest captchas in our workers' browsers. Your app submits the website address, gt key, challenge key and after task completion receives a solution consisting of 3 tokens.

Everything is similar to GeeTestTask, except we don't require proxy and we solve it from our own IP addresses.


Task object

Property Type Required Purpose
type String Yes GeeTestTaskProxyless
websiteURL String Yes Address of a target web page. Can be located anywhere on the web site, even in a member area. Our workers don't navigate there but simulate the visit instead.
gt String Yes The domain public key, rarely updated.
challenge String Yes Changing token key. Make sure you grab a fresh one for each captcha; otherwise, you'll be charged for an error task.
geetestApiServerSubdomain String No Optional API subdomain. May be required for some implementations.
geetestGetLib String No Required for some implementations. Send the JSON encoded into a string. The value can be traced in browser developer tools. Put a breakpoint before calling the "initGeetest" function.

Request example

          curl -i -H "Accept: application/json" \
     -H "Content-Type: application/json" \
     -X POST -d '{

Response example

JSON with no errors
    "errorId": 0,
    "taskId": 7654321
JSON with an error
    "errorId": 1,
    "errorCode": "ERROR_KEY_DOES_NOT_EXIST",
    "errorDescription": "Account authorization key not found in the system"

Retrieve the solution

Use method getTaskResult to request the solution. Give the worker about 5 seconds before making your first request. If the worker is still busy, retry in 3 seconds.

Task solution object

Property Type Purpose
challenge String Hash string required for interacting with the submit form on the target website.
validate String Hash string which is also required.
seccode String Another required hash string; we have no idea why there are 3 of them.

Response example

JSON with no errors

Token usage example