Nex Captcha

PRODUCT TEST WORKSPACE

Slider Captcha

Captcha verification product

SLIDER_CAPTCHA

01 / CREATE

Create task

The editor starts with required fields and one conditional branch. Optional fields are listed below and can be loaded into the editor.

02 / REQUEST

Request preview

POST /api/validator/create.cgi
{
  "productCode" : "SLIDER_CAPTCHA",
  "adapter" : {
    "body" : "BASE64_CONTENT"
  }
}

03 / RESULT

Response example

EXAMPLE
Task ID — 
{
  "code" : 0,
  "msg" : "Success",
  "data" : {
    "taskId" : "11111111-1111-4111-8111-111111111111",
    "productCode" : "SLIDER_CAPTCHA",
    "state" : "SUCCEEDED",
    "solution" : {
      "coordinates" : [ {
        "x" : 240,
        "y" : 100
      } ]
    }
  }
}

Illustrative response; not a live task result. Replace all request placeholders before submitting.

Solution fields are not documented yet. This example shows the response envelope only.

Read data.solution after state becomes SUCCEEDED. The solution fields depend on the product; other states may return an empty object.

04 / API REFERENCE

Slider Captcha · API

For task creation and queries, send the API key in the apiKey HTTP header. JSON request bodies contain business parameters only.

Content-Type: application/json
apiKey: YOUR_API_KEY

Request example

POST /api/validator/create.cgi · JSONC
{
  "productCode": "SLIDER_CAPTCHA", // Product code matching the adapter parameters.
  "adapter": { // Product-specific parameter object.
    "body": "BASE64_CONTENT", // Base64 JPEG, PNG or GIF of the current custom slider challenge; a data URI is accepted upstream. Preserve original pixels. Upstream limits: 600 kB decoded, at most 1000 pixels on either side. This is not a GeeTest, DataDome or other vendor token-solving contract.
    "comment": "YOUR_COMMENT" // Optional worker instruction describing the exact point to click, for example the center of the matching target slot. If omitted, the image must contain sufficient instructions. For a custom test, provide explicit English instructions and a known point. Returned coordinates are relative to this image.
  }
}

Request headers: apiKey: YOUR_API_KEY

Comments explain the fields. Copy produces valid JSON without comments.

Response example

POST /api/validator/query.cgi · JSONC
{
  "code": 0, // Business result code: 0 means success; other values indicate an error.
  "msg": "Success", // Result message; may be empty on success.
  "data": { // Response data; may be null on an error.
    "taskId": "11111111-1111-4111-8111-111111111111", // Task ID returned by task creation.
    "productCode": "SLIDER_CAPTCHA", // Product code matching the adapter parameters.
    "state": "SUCCEEDED", // Task state: CREATED, SUBMITTING, PROCESSING, SUCCEEDED, FAILED or EXPIRED.
    "solution": { // Product answer when SUCCEEDED; empty while processing or on failure.
      "coordinates": [ // Click coordinates, with the origin at the top left of the image.
        { // Product-specific answer field; use it according to the target website verification protocol.
          "x": 240, // Horizontal coordinate in pixels.
          "y": 100 // Vertical coordinate in pixels.
        }
      ]
    }
  }
}

Creating a task returns its ID and initial state. Query the result or use WebSocket to receive the completed answer shown below.

Solution fields are not documented yet. This example shows the response envelope only.

Request parameters

FieldTypeRequiredDescription
productCodestringYesProduct code matching the adapter parameters.
adapterobjectYesProduct-specific parameter object.
adapter.bodystringYesBase64 JPEG, PNG or GIF of the current custom slider challenge; a data URI is accepted upstream. Preserve original pixels. Upstream limits: 600 kB decoded, at most 1000 pixels on either side. This is not a GeeTest, DataDome or other vendor token-solving contract.
adapter.commentstringNoOptional worker instruction describing the exact point to click, for example the center of the matching target slot. If omitted, the image must contain sufficient instructions. For a custom test, provide explicit English instructions and a known point. Returned coordinates are relative to this image.

Response parameters

FieldTypeDescription
codeintegerBusiness result code: 0 means success; other values indicate an error.
msgstringResult message; may be empty on success.
dataobject | nullResponse data; may be null on an error.
data.taskIdstringTask ID returned by task creation.
data.productCodestringProduct code matching the adapter parameters.
data.statestringTask state: CREATED, SUBMITTING, PROCESSING, SUCCEEDED, FAILED or EXPIRED.
data.solutionobjectProduct answer when SUCCEEDED; empty while processing or on failure.
data.failureobject | omittedPublic diagnosis for FAILED/EXPIRED only; no raw provider messages. Follow the failure handling guide.
data.failure.codestringFailure code
data.failure.nextActionstringNext action
data.solution.coordinatesarrayClick coordinates, with the origin at the top left of the image.
data.solution.coordinates[]objectProduct-specific answer field; use it according to the target website verification protocol.
data.solution.coordinates[].xintegerHorizontal coordinate in pixels.
data.solution.coordinates[].yintegerVertical coordinate in pixels.

Responses

HTTP business responses contain code, msg and data; code 0 means success. WebSocket uses a separate message structure.

-1317
Invalid API key.
-1100 / -1101
Invalid or missing request parameters.
-1401
Insufficient balance. Add funds before creating a task.
-1400 / -1001
System or task creation error.
API documentation