Tasks
Updated 8/6/2026
Alix5sec Solver API
Solve Alibaba x5sec NoCaptcha interstitial challenges with the Solverify x5sec Solver API. The browser-based task handles the slide-to-verify page shown after Alibaba reports unusual network traffic, then returns the x5sec value and all captured session cookies.
Use this task type for authorized Alibaba or AliExpress workflows protected by the x5sec NoCaptcha challenge.
Alibaba x5sec Solver Endpoint
POST https://solver.solverify.net/createTask
The x5sec integration follows the standard Solverify task workflow:
- Create an
alix5sectask with the protected page URL. - Supply a replayable proxy for production use.
- Store the returned
taskId. - Poll
POST /getTaskResultuntil processing completes. - Read the
x5secvalue, complete cookie set, and user-agent fromsolution. - Replay all cookies with the same proxy and user-agent.
Request Parameters
| Field | Type | Required | Description |
|---|---|---|---|
clientKey | string | Yes | Your private Solverify API key. |
task.type | string | Yes | Must be alix5sec. |
task.websiteURL | string | Yes | Full URL of the x5sec-protected page. Maximum 2,048 characters. |
task.useragent | string | No | Chrome-family user-agent. Maximum 512 characters. |
task.proxyType | string | No | Proxy type. Only http is accepted. Defaults to http when address and port are supplied. |
task.proxyAddress | string | No | Proxy IP address or hostname. Maximum 256 characters. |
task.proxyPort | string | No | Proxy port as a numeric string containing 1 to 5 digits. |
task.proxyLogin | string | No | Username for an authenticated proxy. |
task.proxyPassword | string | No | Password for an authenticated proxy. |
The backend permits proxyless tasks, but x5sec is IP-bound. For a cookie that your application can replay, provide proxyAddress and proxyPort, then use the same proxy for the follow-up request. Proxy credentials are required only when your proxy requires authentication.
If useragent is supplied, use desktop Chrome/Chromium or Android Chrome. Android Chrome is accepted when the worker can generate a compatible device fingerprint. Firefox, Edge, Opera, iOS, and non-Chrome Android user-agents are rejected.
Create x5sec Task Request
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "alix5sec",
"websiteURL": "https://login.aliexpress.com/user/buyer/login/loginByPwd",
"useragent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36",
"proxyType": "http",
"proxyAddress": "1.1.1.1",
"proxyPort": "8080",
"proxyLogin": "username",
"proxyPassword": "password"
}
}
Omit proxy credentials when authentication is not required. Omit useragent to use the solver browser's user-agent, which is returned in solution.useragent.
Alibaba x5sec Code Examples
These examples create an x5sec task and print the returned task ID.
curl --request POST \
--url https://solver.solverify.net/createTask \
--header "Content-Type: application/json" \
--data '{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "alix5sec",
"websiteURL": "https://login.aliexpress.com/user/buyer/login/loginByPwd",
"proxyType": "http",
"proxyAddress": "1.1.1.1",
"proxyPort": "8080"
}
}'
Create Task Response
{
"errorId": 0,
"taskId": "UUID"
}
Completed x5sec Result
{
"errorId": 0,
"status": "completed",
"solution": {
"value": "7b22617365727665722d696e746c3b33223a22307c434a767775...",
"cookies": {
"cna": "H2bVImLv4gUCAbnRxKC80C9X",
"xman_t": "3ZMT4QP+ScFwl43ld5PM...",
"xman_f": "Uqbga6J5MfoxXsJnpPIXA7FR...",
"x5sec": "7b22617365727665722d696e746c3b33223a22307c434a767775...",
"tfstk": "gqgISaVpiS2wN7URNkAw53Qu..."
},
"useragent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/146.0.0.0 Safari/537.36"
},
"errorCode": null,
"errorDescription": null
}
Solution Fields
| Field | Description |
|---|---|
value | The x5sec cookie value. |
cookies | Complete cookie set captured from the browser session, including x5sec. |
useragent | User-agent used by the solver and required for consistent replay. |
Replay the full cookie set rather than only x5sec. Some Alibaba endpoints also require session cookies such as xman_t, xman_f, cna, or tfstk.
Alibaba x5sec Timeout
Alibaba x5sec tasks can run for up to approximately 90 seconds before timing out internally. Configure an overall polling deadline and stop when the API returns an error.
Alibaba x5sec API Errors
| Error code | Description |
|---|---|
ERROR_INVALID_REQUEST | The top-level request is missing or contains invalid JSON. |
ERROR_INVALID_TASK | The target URL or supplied proxy settings are invalid. |
ERROR_INSUFFICIENT_BALANCE | The account balance is too low to create the task. |
ERROR_NO_CAPACITY | x5sec solver capacity is temporarily unavailable. |
ERROR_TASK_FAILED | The x5sec challenge could not be completed or no usable cookie was captured. |
ERROR_TIMEOUT | Solving exceeded the allowed processing time. |
For recovery guidance and every supported response, see Solverify API Error Codes.
Next Steps
After creating an Alibaba x5sec task, poll the Get Task Result API every 2 to 3 seconds with the returned taskId. Stop polling after completion or failure.
Frequently Asked Questions
What does the Alibaba x5sec Solver API return?
It returns the x5sec value in solution.value, all captured browser cookies in solution.cookies, and the solver user-agent in solution.useragent.
Is a proxy required?
The API allows proxyless tasks, but x5sec is IP-bound. Use a proxy for production and replay the cookies from the same proxy IP.
Are proxy credentials required?
Only when your proxy requires authentication. Unauthenticated proxies need proxyAddress and proxyPort but not login credentials.
Should I replay only the x5sec cookie?
No. Replay the complete solution.cookies set because the target may require accompanying Alibaba session cookies.