Task type
Amazon AWS WAF solver API
AWS WAF can answer a request with a CAPTCHA action (a visible puzzle) or a Challenge action (a silent browser check) instead of allowing it through. Both are served by a per-distribution challenge script on awswaf.com, and both end the same way: a token that AWS accepts for the rest of its immunity window. Send it back either as the aws-waf-token cookie or in the x-aws-waf-token header — non-browser clients normally use the header. The token is bound to the domain it was earned on and to the requesting network, so continue the session on the same proxy.
Tip
task.type as awsToken and the solution arrives in solution.aws_token.A site that will not solve is worth telling us about — coverage is per target as much as per type. The quickest route is Telegram (@VoidCaptchaSupport), where someone usually answers within minutes. You can also open a ticket from your dashboard or email [email protected]. Send the URL and the site key either way.
Solve request#
Solving Amazon AWS WAF is a single synchronous call. You post one task object and the response carries the finished solution — no task id to store, nothing to poll for.
The connection is held open for the whole solve. Set a client timeout that covers it — the default socket timeout in most HTTP libraries is shorter than the work. If holding a connection that long does not suit your worker fleet, the same task goes to /v1/createTask and you collect it from /v1/checkTask instead.
When to use it#
- Keeping an API client working against an endpoint that turned on Bot Control
- Synthetic monitoring of a service fronted by AWS WAF
- Verifying your own WAF rules do not challenge legitimate traffic
Task object structure#
These fields go inside task. The envelope around it — clientKey and the optional softId — is the same for every type and is described in the API reference.
| Property | Type | Required | Description |
|---|---|---|---|
type | string | Required | Literal "awsToken". Matching is case-insensitive. |
url | string | Required | The protected URL that returned the challenge.e.g. https://example.com/api/search |
client | string | Optional | Which SDK flow to run: web, android or ios. Defaults to web.e.g. web |
aws_js_url | string | Optional | The full challenge script URL, when you already have it. Required for targets that answer with an empty 202 and no HTML to scrape, and a latency saving everywhere else. Must be an awswaf.com host.e.g. https://d1x2y3z4.edge.sdk.awswaf.com/d1x2y3z4/a1b2c3/challenge.compact.js |
proxy | string | Required | Upstream proxy. Accepts host:port, host:port:user:pass, or a full http:// URL. Use a sticky session — a rotating exit IP mid-solve looks like a hijacked session and will fail.e.g. proxy.example.com:9090:user:pass |
user_agent | string | Optional | Pin the User-Agent used for the solve. Omit it and a coherent one is chosen for you and returned in the response — match whatever you send downstream.e.g. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 … |
Example payload#
The whole body, assembled from the table above — copy it formatted to read, or on one line to paste straight into a terminal or a REST client. The values are placeholders: swap the key for your own and the URL and site key for the page you are solving.
https://api.voidcaptcha.com/v1/getResult{
"clientKey": "void_a1b2c3d4e5f60718293a4b5c6d7e8f90",
"task": {
"type": "awsToken",
"url": "https://example.com/api/search",
"proxy": "proxy.example.com:9090:user:pass"
}
}Example request#
The smallest thing that gets a token back, in your language. Python and Node.js use the official client (pip install voidcaptcha, npm install voidcaptcha); every other language makes the HTTP call its standard library already has. The complete version, with the key read from the environment and the error envelope checked, is in Sample code at the bottom of this page.
Language choice is remembered across the whole site, so switching here carries to every other sample in the docs.
# pip install voidcaptcha
from voidcaptcha import VoidCaptcha
client = VoidCaptcha("void_a1b2c3d4e5f60718293a4b5c6d7e8f90")
result = client.aws_waf(
url="https://example.com/api/search",
proxy="proxy.example.com:9090:user:pass",
)
print(result.value)Example response#
A successful solve returns errorId: 0 and a solution object. The result is in solution.aws_token; alongside it is the userAgent the solve ran under.
solution carries those and nothing else — the gateway copies the result field, anything extra this type returns, and userAgent across, and drops the rest of whatever the solver sent. Timing arrives at the top level as elapsedMs, present only when the duration is known, beside cost and your remaining balance. The figures below are illustrative: nothing here is a published median.
{
"errorId": 0,
"status": "ready",
"solution": {
"aws_token": "eyJ1IjoiaHR0cHM6Ly9leGFtcGxl…",
"userAgent": "Mozilla/5.0 …"
},
"cost": "$0.0014",
"balance": "$411.24",
"elapsedMs": 4820
}Send that userAgent on your downstream request as well — for the cookie-based types the result is bound to it and will be rejected under a different one.
Errors for this type#
The codes Amazon AWS WAF can return, on top of the shared authentication and billing set. Branch on errorCode, not on the HTTP status.
| Code | HTTP | Meaning | Retry |
|---|---|---|---|
ERROR_KEY_MISSING | 401 | No clientKey was supplied. | Do not retry |
ERROR_KEY_INVALID | 401 | The key does not exist or has been revoked. | Do not retry |
ERROR_KEY_SUSPENDED | 403 | The account attached to this key is suspended. | Do not retry |
ERROR_TYPE_NOT_ENABLED | 403 | This account is not enabled for the requested task type. | Do not retry |
ERROR_IP_BLOCKED | 200 | The target rejected the proxy IP outright. | Retry |
ERROR_INSUFFICIENT_BALANCE | 402 | Your balance will not cover this solve. | Do not retry |
ERROR_THREAD_LIMIT | 429 | You have more solves in flight than your key permits. | Retry with backoff |
ERROR_RATE_LIMITED | 429 | Too many requests in a short window. | Retry with backoff |
Every code, with the fix for each, is on the error reference. A failed solve is never charged.
Sample code#
A complete file: key from the environment, task built, error envelope checked, result used. It calls the endpoint directly rather than through an SDK, so it works as a starting point in any language.
import os
import sys
import requests
API = "https://api.voidcaptcha.com/v1/getResult"
payload = {
"clientKey": os.environ["VOIDCAPTCHA_KEY"],
"task": {
"type": "awsToken",
"url": "https://example.com/api/search",
"proxy": "proxy.example.com:9090:user:pass"
},
}
# The endpoint is synchronous: it holds the connection open for the whole
# solve, so the read timeout has to cover it, not just the handshake.
res = requests.post(API, json=payload, timeout=180).json()
if res["errorId"] != 0:
sys.exit(f"{res['errorCode']}: {res['errorDescription']}")
solution = res["solution"]
# Carry the User-Agent downstream — the result was earned under it.
print(solution["aws_token"])
print(solution["userAgent"])Last updated on 2 August 2026