captcha.js. Passing it sets the aws-waf-token cookie, and the site lets the browser through until the token expires.
Each solve is charged.
Before you start
Start a browser and create a page-levelcdp session as in the CAPTCHA setup example. AWS WAF is solved automatically only when Captcha.autoSolve lists it in types.
Manual captcha solving
SendCaptcha.solve once the captcha page has loaded:
success means the captcha page did not come back. There is no solution: the page keeps its own aws-waf-token cookie.
A page that only checks the browser, without a puzzle, needs no solve: the browser passes it by itself.
Automatic captcha solving
Attach listeners and enable automatic mode before navigating:Captcha.solveCompleted, wait for the site’s own content before reading the page.
Troubleshooting
failed means AWS WAF showed its captcha page again; retry, or use another proxy. A captcha that a site draws into its own page, instead of AWS WAF’s captcha page, is not solved: the command fails with No captcha detected on the page.
See CAPTCHA troubleshooting for shared errors and DevTools to inspect a running attempt.
Questions? Contact support.