Amazon WAF CAPTCHA
AWS WAF answers suspicious requests with a CAPTCHA challenge on the page itself: the visitor solves a puzzle and the site lets the request through with a token. You see it on stores, download areas and account pages that are protected by Amazon Web Services.
EndCaptcha solves these challenges through the same API as every other CAPTCHA type. You send the challenge values from the protected page, poll for the result and receive a token, and then your page submits that token so the request passes.
What you need from the target page
- Key - the key value inside the script that renders the challenge on that page.
- Page URL - the full address where the challenge appears, including its path.
- iv - the iv parameter of that same script.
- context - the context parameter of that same script.
- Proxy - optional but recommended, HTTP proxies only, so the address that solves the challenge and the address that submits the form match.
Solve it through the API
- Submit with type=16 to http://api.endcaptcha.com/upload.
- Poll the returned id every 3 seconds.
- Take the token and submit it where the protected page expects it, next to the challenge it belongs to.
The full parameter list, an example and the error table live on the Amazon WAF API guide.
What it costs
WAF challenges are charged in credits like every other CAPTCHA, and some types cost more credits than others. The packages and their credit prices are on the pricing block of the home page, and a challenge that solved incorrectly is not billed when you report it.
Amazon WAF questions
Where do the key, iv and context come from?
All three live in the script that renders the challenge: the key
parameter of that script, and its iv and context parameters.
Which proxies are supported?
HTTP proxies only, and only when you send them with the payload.
How long does a solve take?
Poll every 3 seconds until the token arrives. The home page publishes a
seven second service level agreement for the service.

