AlibabaX5SecCookie
Solve the Alibaba x5sec NoCaptcha slide-to-verify interstitial and get back the x5sec cookie plus the rest of the session jar.
Alibaba and AliExpress answer traffic they distrust with a slide-to-verify interstitial — the "unusual network traffic" page served from _____tmd_____/punish. Clearing it sets an x5sec cookie that unblocks the session. AlibabaX5SecCookie drives that page through your proxy and returns the cookie.
Replay the whole jar, not just x5sec
solution.cookies also carries the Alibaba session cookies minted alongside it — commonly cna, xman_t, xman_f
and tfstk. Many endpoints reject a request that sends x5sec on its own.
Proxy and User-Agent
x5sec is IP-bound. Send the same proxy on the follow-up request, and use the User-Agent returned in
solution.userAgent. Passing your own userAgent in the task is supported, but it must be a desktop
Chrome/Chromium or Android Chrome string — other browser families are rejected.
Use AlibabaX5SecCookieProxyLess only when you are not going to replay the cookie from your own backend: without a proxy the cookie is bound to the solver's exit IP.
Not the same as AlibabaToken
AlibabaToken solves Aliyun Captcha 2.0, the sliding widget embedded in a page. This task is the full-page x5sec interstitial, which returns cookies rather than a verification payload.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
 | $0.40 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in the AnySolver dashboard. Example: |
task* | object | Yes | The task body. Required fields depend on the task type. See Tasks for per-task schemas. View task properties |
settings | object | No | Per-request settings for routing, auto retry, auto fallback, and proxy behavior. See Routing Strategies. View settings reference |
Task Object Properties
The task field accepts an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
type* | Yes | ||
websiteURL* | URL | Yes | Full URL of the page where the CAPTCHA is displayed. Example: |
proxy* | string | object | Yes | |
userAgent | string | No | Browser User-Agent string. Must match the browser used on the target page. Not all providers properly support this parameter. Verify the compatibility with the provider you are using. Example: |
Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes | 0 = success, 1 = external error, 2 = internal error. Example: | |
taskId | string | No | Unique identifier returned when the task was created. Example: |
errorCode | No | Machine-readable error code. Example: | |
errorDescription | string | No | Human-readable error message with resolution hints. Example: |
cost | number | No | Actual cost charged for this task in USD. Example: |
taskType | No | The type of CAPTCHA task to solve. Example: | |
provider | No | Provider that handled this task. While processing, the provider currently solving it. Example: | |
solution | object | No |
Solution Object Properties
The solution field contains an object with the following properties:
| Field | Type | Required | Description |
|---|---|---|---|
x5sec* | string | Yes | The solved Example: |
cookies* | Record<string, unknown> | Yes | Full cookie jar from the solved session. Replay all of it — Alibaba endpoints often need Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
userAgent | string | No | User-Agent string used during solving (if applicable). Example: |