AlibabaToken
Solve Alibaba Cloud CAPTCHA through your own proxy from the sceneId, prefix and requestInfo values. Shows the request schema, an example and provider prices.
AlibabaToken solves Alibaba Cloud CAPTCHA (Aliyun CAPTCHA) through your proxy and returns the verification tokens. It takes the page URL, the scene and prefix values, and optional session values. The server returns a CAPTCHA page after a suspicious action, such as a login attempt.
Use AlibabaTokenProxyLess when the site accepts a token solved from another address.
Proxy
task.proxy is required on this task type, and the provider solves from that address. Send the proxy you use for your own requests to the site, and keep one IP for the whole solve: see Keep the same IP for the whole solve.
Find the parameters
Several of these values are generated dynamically and can differ on every protected page load.
Open the site and perform the action that triggers the CAPTCHA, such as a login attempt. In the Network tab of DevTools, find the response that returns an HTML CAPTCHA page instead of the usual JSON.
Find the var requestInfo object in that page. It holds data, region, sceneId, token, traceid,
type, userId and userUserId.
Map the fields. sceneId, userId, userUserId and region use the field of the same name. verifyType is
the type field, and userCertifyId is the traceid field.
Find prefix, the subdomain of the CAPTCHA initialization request. For
https://dlw3kug.captcha-open.example.aliyuncs.com/, the prefix is dlw3kug.
Find apiGetLib, the URL of the AliyunCaptcha.js script, in a script tag on the CAPTCHA page or in the
Network tab.
Only websiteURL, sceneId and prefix are required. If requestInfo is missing or obfuscated, search the network requests for sceneId, CaptchaSceneId or sId.
Keep the token and traceid values from requestInfo as well. You need them when you resend the original request after the solve.
Use the tokens
The solution tokens is a JSON string with sceneId, certifyId, deviceToken and data. Send it with the request the CAPTCHA page blocked. To find the field that carries it, submit the form once in a browser with the DevTools Network tab open and find the request parameter that carries the tokens.
If the site rejects the tokens, check that the proxy kept one IP for the whole solve, then that the values come from the same page load.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
2Captcha | $2.99 | |
CapMonster | $0.80 | |
Solverify | $0.20 |
Request Schema
| Field | Type | Required | Description |
|---|---|---|---|
clientKey* | string | Yes | Your API key. Create one in a workspace of 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, proxy reuse, response statistics and detailed analytics. Each field overrides the API key's value. See Routing modes. 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: |
sceneId* | string | Yes | Captcha scenario identifier: the Example: |
prefix* | string | Yes | Captcha initialization parameter: the subdomain of the captcha request URL, for example Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
userId | string | No | Unique identifier of the user or session on the website side ( Example: |
userUserId | string | No | Secondary user identifier ( Example: |
verifyType | string | No | Version or type of the captcha verification mechanism ( Example: |
region | string | No | Region of the data center processing the captcha ( Example: |
userCertifyId | string | No | Verification ID linked to the current captcha session ( Example: |
apiGetLib | URL | No | Link to the Example: |
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: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "AlibabaToken",
"websiteURL": "https://www.example.com",
"sceneId": "abc123xyz4",
"prefix": "def456gh",
"proxy": "http://user:pass@1.2.3.4:8080"
}
}Optional fields are not guaranteed across providers
Response Schema
| Field | Type | Required | Description |
|---|---|---|---|
status* | Yes | Task status: "processing", "ready", or "failed". Example: | |
errorId* | Yes |
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 |
|---|---|---|---|
tokens* | string | Yes | JSON string with Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |