Skip to Content
AnySolver logo
AnySolver
Token

AltchaToken

Solve ALTCHA proof-of-work challenges through your own proxy from the challenge JSON and get the payload to submit. With the schema, example and prices.

AltchaToken solves the ALTCHA challenge you send, through your proxy, and returns the payload to submit with the form. ALTCHA is an open-source, proof-of-work CAPTCHA: the altcha-widget web component fetches a challenge from the site's server, solves it in the browser, and submits the result in a hidden form field named altcha by default.

The ALTCHA widget: an "I'm not a robot" checkbox with the "Protected by ALTCHA" label

Use AltchaTokenProxyLess when the site accepts a solution computed 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

The challenge URL is in the challenge attribute of the <altcha-widget> element (challengeurl on older versions), or in the widget's configuration. Open that URL, or watch the Network tab as the widget loads, to see the challenge response.

  • challengeJSON is the response of that request as a string. It carries algorithm, challenge, salt and signature, and maxnumber when the challenge has one. Fetch a new challenge for every task, because challenges expire and the server signs each one. Check that the challenge has challenge, salt and signature fields before you create the task.
  • challengeURL is optional. Providers solve the challengeJSON you send and do not fetch this URL.
  • maxnumber is optional, and only some providers read it. Those use it instead of the maxnumber in challengeJSON.

Challenge format

The task expects a challenge with challenge, salt and signature fields. Newer ALTCHA versions can issue challenges with a different layout, such as the parameters object with PBKDF2/SHA-256. Check the challenge the site returns before you create the task.

Use the token

The solution token is the payload for the form field the widget fills, altcha by default. Most providers return it Base64-encoded, and some return the solved JSON object as a string. Set it as the value of that field, or send it in the request where the page sends the widget's value, before you submit.

If the site rejects the payload, fetch a new challenge and create a new task, and check that the proxy kept one IP for the whole solve.

Check Provider stats for live success rates and solve times before you pick a provider.

Supported Providers

ProviderPrice per 1,000Routing
2Captcha
$2.99
Anti-Captcha
$2.00
CapMonster
$0.80
SolveCaptcha
$1.45

Request Schema

FieldTypeRequiredDescription
clientKey*
stringYes

Your API key. Create one in a workspace of the AnySolver dashboard.

Example: your-api-key-from-dashboard

task*
objectYes

The task body. Required fields depend on the task type. See Tasks for per-task schemas.

View task properties
settings
objectNo

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:

FieldTypeRequiredDescription
type*
Yes
websiteURL*
URLYes

Full URL of the page where the CAPTCHA is displayed.

Example: https://example.com/contact

challengeJSON*
stringYes

Challenge JSON returned by the challenge URL, as a string, with algorithm, challenge, salt and signature (and maxnumber when present). Fetch a new one for every task: challenges expire.

Example: {"algorithm":"SHA-256","challenge":"4f2d...","maxnumber":50000,"salt":"8b9a...","signature":"MEUCIQ..."}

proxy*
string | objectYes

Proxy the provider solves through, as a string or an object. See Proxy configuration.

View proxy configuration

Example: http://user:pass@1.2.3.4:8080

challengeURL
stringNo

URL the widget fetches the challenge from (the challenge or challengeurl attribute of altcha-widget). Optional: providers solve the challengeJSON you send, not this URL.

Example: https://example.com/api/altcha/challenge

maxnumber
numberNo

Maximum puzzle number of the challenge. Only some providers read it: they use it instead of the maxnumber in challengeJSON, and fall back to 1000000 when neither is set.

Example: 50000

{
    "clientKey": "YOUR_API_KEY",
    "task": {
        "type": "AltchaToken",
        "websiteURL": "https://example.com/contact",
        "challengeJSON": "{\"algorithm\":\"SHA-256\",\"challenge\":\"4f2d...\",\"maxnumber\":50000,\"salt\":\"8b9a...\",\"signature\":\"MEUCIQ...\"}",
        "proxy": "http://user:pass@1.2.3.4:8080"
    }
}

Optional fields are not guaranteed across providers

Required fields are guaranteed across every provider that supports this task. Optional fields may be honored by some providers and silently ignored by others. AnySolver does not document per-provider parameter support, so before relying on an optional field, check that provider's own docs for the task you are using.

Response Schema

FieldTypeRequiredDescription
status*
Yes

Task status: "processing", "ready", or "failed".

Example: ready

errorId*
Yes

0 on success; 1 or 2 on an error. Branch on errorCode: Error IDs explains the two error groups.

Example: 0

taskId
stringNo

Unique identifier returned when the task was created.

Example: 01KFNDF328KAN2AJ3BNHCQYE88

errorCode
No

Machine-readable error code.

Example: CAPTCHA_UNSOLVABLE

errorDescription
stringNo

Human-readable error message with resolution hints.

Example: The captcha could not be solved.

cost
numberNo

Actual cost charged for this task in USD.

Example: 0.002

taskType
No

The type of CAPTCHA task to solve.

Example: ReCaptchaV2TokenProxyLess

provider
No

Provider that handled this task. While processing, the provider currently solving it.

Example: Multibot

solution
objectNo

Solution Object Properties

The solution field contains an object with the following properties:

FieldTypeRequiredDescription
token*
stringYes

ALTCHA payload to submit to the target site, usually in the altcha form field. Most providers return it Base64-encoded; some return the solved JSON object serialized as a string.

Example: eyJhbGdvcml0aG0iOiJTSEEtMjU2IiwiY2hhbGxlbmdlIjoiZWFiOTE3NjRkM2Y5ZDBjMGU4ZmR...

raw*
Record<string, unknown>Yes

Raw provider response data for advanced use cases.

userAgent
stringNo

User-Agent string used during solving.