Changelog
Notable changes to the service, the website and the SDKs, newest first.
- APIAn account can hold up to 20 API keys at once, up from 10.
- WebsitePausing, activating or deleting a key from its menu on the API keys page no longer opens the key's page as well.
- WebsiteThe API keys page has a search box, which finds a key by its name or site key whatever the case and the Vietnamese accents, and shows the keys a page at a time, 5, 10, 20 or 50 to a page.
- SDK@waucaptcha-sdk/react 1.7.0 and @waucaptcha-sdk/client 1.8.0: MODAL mode shows a box like auto_check's for every type, a checkbox with “I'm not a robot” that opens the challenge in its dialog and turns into a check mark and “Verified” once it is solved; the auto_check box says only “Checking…”; and object_rotate asks, in English, to turn the object to face the way the arrow points.
- SDK@waucaptcha-sdk/server 1.7.1: the comments of ChallengeType describe object_rotate's two panels, the arrow on the left and the object on the right.
- APIobject_rotate shows the arrow and the object in two panels of each frame, the arrow on the left and the object on the right, seen from the same camera, so the arrow never covers the object. Only boxy objects remain, ten vehicles and pieces of furniture with sharp edges that show which way they face, and the arrow is slimmer, without its outline. Older SDKs keep working.
- SDK@waucaptcha-sdk/server 1.7.0 adds hostnameMatches, and the Java SDK result.hostnameMatches: they check the website a token was solved on against yours, taken as a list or as one string with commas between them, such as an environment variable, and read https://Shop.example.com/, shop.example.com:443 and shop.example.com as the same, with *.example.com for the subdomains; a domain written with https:// no longer refuses every token.
- SDK@waucaptcha-sdk/client 1.7.1 and @waucaptcha-sdk/react 1.6.1: the auto_check box shows the WAU Captcha logo where it showed a shield, purple on light and lime on dark whatever primary colour the site sets.
- SDKThe SDKs move to new names: @waucaptcha-sdk/client 1.7.0, @waucaptcha-sdk/react 1.6.0 and @waucaptcha-sdk/server 1.6.0 on npm, with the same code as the last @wau-captcha releases, and com.waucaptcha:waucaptcha-sdk 1.1.0 for Java; replace @wau-captcha/ with @waucaptcha-sdk/ in package.json and in your imports, as the old packages stay on npm and keep working but get no further releases.
- WebsiteThe new WAU Captcha logo: a W that is also a person raising both arms, in the header, the favicon and the captcha previews, and a banner for links shared to social networks and chat apps.
- APIauto_check now rests on what a bot cannot fake from inside the browser: a puzzle solved earlier earns the browser a clearance (7 days, 6 automatic passes an hour and 24 a day), an address of a cloud or hosting provider never passes automatically, and in balanced mode a first visit without a clearance passes at most 5 times an hour per address. siteverify gives the reason cleared or first_visit; refuse first_visit for sign-ups, logins and payments.
- SDK@wau-captcha/client 1.7.0 and @wau-captcha/react 1.6.0: the widget keeps the clearance of a solved puzzle in localStorage and sends it back with auto_check answers, with counts of how the mouse moves were made; the behaviour recorder gains pointerSummary().
- WebsiteThe About page is in the navigation bar: it introduces the website and says that bots solving every captcha for research and testing are welcome, within limits the terms now state too.
- APIA new challenge type, auto_check (Auto check): most visitors get a token without solving anything, after a proof of work, a few browser checks and the behaviour check, and those the service is unsure of get a challenge of a fallback type instead. siteverify reports auto_check for an automatic pass.
- SDK@wau-captcha/client 1.6.0, @wau-captcha/react 1.5.0 and @wau-captcha/server 1.6.0: ChallengeType.AUTO_CHECK, with a compact box in the widget and <WauCaptcha />, the options fallbackChallengeType and appearance (data-fallback-type and data-appearance), verifyAuto and probeBrowser.
- SDKcom.waucaptcha:wau-captcha-sdk 1.1.0 knows ChallengeType.AUTO_CHECK too, for the tokens verifyToken redeems, and Challenge.fallbackType().
- WebsiteA page for auto_check that says what it stops and what it does not, with a preview of the box and of its fallback.
- APIA new challenge type, object_rotate (Rotate to arrow): in each of two rounds an object stands beside an arrow on the ground, and the person turns it a frame at a time until it faces the arrow. Both rounds must be right, and it works with the keyboard too.
- SDK@wau-captcha/client 1.5.0, @wau-captcha/react 1.4.0 and @wau-captcha/server 1.5.0: ChallengeType.OBJECT_ROTATE, with Rotate left, Rotate right and Done (or the arrow keys and Enter) in the widget and <WauCaptcha />, verifyRotate and trackRotate.
- SDKcom.waucaptcha:wau-captcha-sdk 1.1.0: ChallengeType.OBJECT_ROTATE, Challenge.frameCount() and verifyRotate with RotateRound and RotatePress.
- WebsiteA page and samples for object_rotate, which you can turn with the buttons.
- APIA new challenge type, animal_jump (Jumping animals): two rounds of 2 s in which five animal heads jump; the person clicks the one that jumps highest in each, and both clicks must be right.
- SDKThe Java SDK is back: com.waucaptcha:wau-captcha-sdk 1.0.0 redeems tokens like @wau-captcha/server and fetches and answers challenges of every type, with the site key and the proof of work.
- SDK@wau-captcha/client 1.4.0, @wau-captcha/react 1.3.0 and @wau-captcha/server 1.4.0: ChallengeType.ANIMAL_JUMP, with the two rounds and a Replay button in the widget and <WauCaptcha />, verifyJump and trackJump.
- WebsiteA page and samples for animal_jump, and the Java SDK back in the docs and on the home page.
- APIKeys can be bound to their websites: /challenge/new checks the Origin (DOMAIN_NOT_ALLOWED), an answer must come from the same website and name the same site key, and /siteverify returns hostname.
- APIEach challenge asks for a small proof of work: answers without it are judged at most suspicious, a wrong one automated.
- APIAnswers are compared with the request that fetched their challenge (address, User-Agent), automation clients are refused, and an address with more than 20 wrong answers in 10 minutes is blocked until they are over.
- APIThe scraping check is graded: a flagged key is throttled to 60 challenges a minute for the day, only a key with 5,000 challenges and under 5% answered is suspended, and owners can request a review.
- APINew keys require behaviour data: an answer without it gets 400 BEHAVIOR_REQUIRED. Existing keys keep accepting it until their owner turns the switch on.
- APImotion_noise shows five characters; in image_distort each character gets its own slant and size, the picture a random wave and thin decoy strokes.
- WebsiteKey page: allowed domains, the Require behaviour data switch, today's counters with a review request for a throttled or suspended key, and an activity log.
- WebsiteAdmin console: an Appeals page to approve or reject review requests.
- WebsiteDocs: site binding and hostname, what each SDK version sends, rate limits, the new scraping rules and a Limitations section.
- SDK@wau-captcha/client 1.3.0: sends the site key and the proof of work with every answer, adds three browser hints to the behaviour data, and knows the new error codes.
- SDK@wau-captcha/server 1.3.0: sends the token in the JSON body, returns result.hostname, and accepts only https base URLs (http for localhost).
- SDK@wau-captcha/react 1.2.0: built on @wau-captcha/client 1.3.0, with Vietnamese texts and how long to wait after RATE_LIMITED.
- APIPlain HTTP to api.waucaptcha.com and waucaptcha.com is redirected to HTTPS, and HSTS is on.
- API/siteverify sends no CORS headers; /challenge/new and /challenge/verify allow only the Content-Type header.
- APIA malformed challenge_id is refused with 400 CHALLENGE_ID_INVALID, and internal errors no longer show their details.
- APIRate limits per address, per key and per secret key: 429 RATE_LIMITED with Retry-After.
- APIRequest bodies are capped (64 KiB for /challenge/verify, 4 KiB for /siteverify): larger ones get 413 PAYLOAD_TOO_LARGE.
- API/siteverify takes the token in the body, as JSON or a form; ?token= still works but is deprecated.
- APIAPI replies are marked Cache-Control: no-store.
- WebsiteSecurity headers and a Content-Security-Policy on every page.
- WebsiteNew pages: privacy, terms, pricing, status, about, security, this changelog and sample challenges.
- WebsiteThe docs no longer mention a Java SDK, which does not exist; any backend can call /siteverify directly.
- WebsiteThe CDN snippet pins an exact SDK version with its integrity hash.