PRODUCT TEST WORKSPACE
Basilisk Captcha
Captcha verification product
BASILISK02 / REQUEST
Request preview
{
"productCode" : "BASILISK",
"adapter" : {
"websiteURL" : "https://example.com/register",
"websiteKey" : "YOUR_WEBSITEKEY"
}
}
03 / RESULT
Response example
—
{
"code" : 0,
"msg" : "Success",
"data" : {
"taskId" : "11111111-1111-4111-8111-111111111111",
"productCode" : "BASILISK",
"state" : "SUCCEEDED",
"solution" : {
"data" : {
"captcha_response" : "EXAMPLE_CAPTCHA_RESPONSE"
},
"headers" : {
"User-Agent" : "EXAMPLE_USER_AGENT"
}
}
}
}
Illustrative response; not a live task result. Replace all request placeholders before submitting.
Read data.solution after state becomes SUCCEEDED. The solution fields depend on the product; other states may return an empty object.
04 / API REFERENCE
Basilisk 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
{
"productCode": "BASILISK", // Product code matching the adapter parameters.
"adapter": { // Product-specific parameter object.
"websiteURL": "https://example.com/register", // Full URL of the page containing the challenge.
"websiteKey": "YOUR_WEBSITEKEY", // Public site key from the target page.
"userAgent": "YOUR_BROWSER_USER_AGENT" // User-Agent of the browser that obtained the challenge.
}
}
Request headers: apiKey: YOUR_API_KEY
Comments explain the fields. Copy produces valid JSON without comments.
Response example
{
"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": "BASILISK", // 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.
"data": { // Product-specific answer field; use it according to the target website verification protocol.
"captcha_response": "EXAMPLE_CAPTCHA_RESPONSE" // Verification token to submit to the target website.
},
"headers": { // HTTP headers used with the verification result.
"User-Agent": "EXAMPLE_USER_AGENT" // Browser User-Agent used to obtain the answer.
}
}
}
}
Creating a task returns its ID and initial state. Query the result or use WebSocket to receive the completed answer shown below.
Request parameters
| Field | Type | Required | Description |
|---|---|---|---|
productCode | string | Yes | Product code matching the adapter parameters. |
adapter | object | Yes | Product-specific parameter object. |
adapter.websiteURL | string | Yes | Full URL of the page containing the challenge. |
adapter.websiteKey | string | Yes | Public site key from the target page. |
adapter.userAgent | string | No | User-Agent of the browser that obtained the challenge. |
Response parameters
| Field | Type | Description |
|---|---|---|
code | integer | Business result code: 0 means success; other values indicate an error. |
msg | string | Result message; may be empty on success. |
data | object | null | Response data; may be null on an error. |
data.taskId | string | Task ID returned by task creation. |
data.productCode | string | Product code matching the adapter parameters. |
data.state | string | Task state: CREATED, SUBMITTING, PROCESSING, SUCCEEDED, FAILED or EXPIRED. |
data.solution | object | Product answer when SUCCEEDED; empty while processing or on failure. |
data.failure | object | omitted | Public diagnosis for FAILED/EXPIRED only; no raw provider messages. Follow the failure handling guide. |
data.failure.code | string | Failure code |
data.failure.nextAction | string | Next action |
data.solution.data | object | Product-specific answer field; use it according to the target website verification protocol. |
data.solution.data.captcha_response | string | Verification token to submit to the target website. |
data.solution.headers | object | HTTP headers used with the verification result. |
data.solution.headers.User-Agent | string | Browser User-Agent used to obtain the answer. |
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.