TencentCaptchaToken
Solve a Tencent Captcha (TCaptcha) through your own proxy and get the ticket and randstr to submit. Shows the request schema, an example and provider prices.
TencentCaptchaToken solves a Tencent Captcha challenge through your proxy and returns the ticket and randstr that the site's backend verifies with Tencent. Parameters, where to find them and how to use the result are the same as for TencentCaptchaTokenProxyLess, which explains them.
Use the proxyless task when the site does not check the address that submits the values.
Use your proxy
task.proxy is required on this task type, and the provider solves from that address. The proxy must keep one IP for the whole solve: see Keep the same IP for the whole solve. Submit the result from the same address. If the site rejects the result, check that the proxy kept one IP, then that appId comes from the page that shows the CAPTCHA.
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 | $1.60 | |
SolveCaptcha | $1.45 |
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: |
appId* | string | Yes | The CaptchaAppId passed to new TencentCaptcha(appId, callback) in the page source. Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
captchaScript | string | No | URL of the TCaptcha.js script the page loads. Defaults to https://turing.captcha.qcloud.com/TCaptcha.js when omitted. Example: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "TencentCaptchaToken",
"websiteURL": "https://www.example.com/",
"appId": "190014885",
"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 |
|---|---|---|---|
ticket* | string | Yes | The Tencent captcha ticket. Pass it, with randstr, to the TencentCaptcha callback or the site backend. Example: |
randstr* | string | Yes | Random string issued with the ticket; the site verifies both together. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
appId | string | No | The CaptchaAppId the ticket was issued for. Example: |
ret | number | No | Tencent result code; 0 means the captcha was passed. Example: |