Documentation menu

GeeTestTaskProxyless: solve captcha from without proxy

This type of task solves GeeTest captcha in our workers browsers. Your app submits 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 at the web site, even in a member area. Our workers don't navigate there, but instead simulate the visit.
gt String Yes The domain public key, rarely updated.
challenge String Yes Changing token key. Make sure to grab fresh one for each captcha, otherwise you will be charged for 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 call of 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 a worker some time, like 5 seconds, before making first request. If the worker is still busy, retry in 3 seconds.

Task solution object

Property Type Purpose
challenge String Hash string which is required for interacting with submit form on target website.
validate String Hash string which is required too.
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