CordNitroRedeemToken
Solve the PopularCaptcha Enterprise challenge Cord serves on the gift-redeem endpoint, and get back both headers needed to replay the redeem.
CordNitroRedeemToken solves the CAPTCHA Cord serves when you redeem a gift or Nitro code and returns the x-captcha-key and x-captcha-rqtoken pair to replay the redeem with. Cord protects redemption with a PopularCaptcha Enterprise challenge bound to an rqdata value. You pass the sitekey and rqdata from Cord's rejection.
The task takes only websiteKey, rqdata and task.proxy, with no websiteURL or userAgent, unlike PopularCaptchaEnterpriseToken. Use this task for the gift and Nitro redeem endpoint, and the enterprise task for other Cord challenges.
Proxy
task.proxy is required on this task type, and the provider solves from that address. Solve and redeem from the same exit IP, and keep one IP for the whole solve: see Keep the same IP for the whole solve. A rotating proxy puts the two requests on different addresses.
Find the parameters
Cord answers a blocked redeem with HTTP 400. The body carries captcha_key set to captcha-required, plus captcha_sitekey, captcha_rqdata and captcha_rqtoken. Send captcha_sitekey as websiteKey and captcha_rqdata as rqdata.
Each captcha_rqdata belongs to one challenge and works once. Take it from a fresh 400 for every attempt instead of reusing an old value.
Replay the redeem
Retry the redeem request with both values from the solution:
X-Captcha-Key: <solution.token>X-Captcha-Rqtoken: <solution.rqToken>
Send both headers on the retry. solution.rqToken is optional in the result, so check solution.raw when it is missing.
Check Provider stats for live success rates and solve times before you pick a provider.
Supported Providers
| Provider | Price per 1,000 | Routing |
|---|---|---|
CaptchaHeaven | $10.00 |
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 | ||
websiteKey* | string | Yes | PopularCaptcha sitekey Cord returns as Example: |
rqdata* | string | Yes | The Example: |
proxy* | string | object | Yes | Proxy the provider solves through, as a string or an object. See Proxy configuration. View proxy configurationExample: |
{
"clientKey": "YOUR_API_KEY",
"task": {
"type": "CordNitroRedeemToken",
"websiteKey": "20000000-ffff-ffff-ffff-000000000002",
"rqdata": "rX5Jrmm4ylfrnE8lx2COFH83kzM058...",
"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 |
|---|---|---|---|
token* | string | Yes | The solved CAPTCHA token to submit with your form. Example: |
raw* | Record<string, unknown> | Yes | Raw provider response data for advanced use cases. |
rqToken | string | No | Value for the |