Changelog
This is the changelog for the Liveness Detection API (anti-spoofing). For our approach to versioning, see the API Reference.
You can check the API version via the metadata.ver field (a semantic version) in each response. This page primarily documents changes that affect backward compatibility (Major / Minor).
v1.0.2 — English-only Error Messages (2026-10-20)
error.messagein error responses is now always in English (previously, Japanese and English were mixed).error.codeand HTTP status codes are unchanged. Useerror.codefor programmatic handling.- Corrected the image size limit in the documentation to the actual value: about 7 MB of raw image data (10 MB for the whole Base64-encoded request), and added the
413response returned when the limit is exceeded. This is a documentation fix only; API behavior is unchanged.
v1.0.1 — Detection Engine Update (2026-09-24)
- Updated the detection engine to the latest model. The decision threshold (
0.15) is unchanged. There is no change to pricing. - Malformed requests (missing required fields, wrong types, undefined fields, or a body that cannot be parsed as JSON) now return
400 invalid_requestwith the common error structure, as documented. Previously,422was returned.
v1.0.0 — Initial Release (2026-07-28)
We released the Liveness Detection API.
Available features:
POST /v1/check/liveness— Liveness (fake) detection from a still imageGET /v1/usage— Check current-month usageGET /v1/health— Health check- Customer dashboard (
/console/*) — API key management (two keys, Primary / Secondary, with zero-downtime rotation), plan and usage checks, and Hard Cap toggling - Subscription and onboarding via AWS Marketplace
For future releases, we will add new versions at the top of this page. Before making any breaking changes that involve deprecating
/v1/(and introducing/v2/), we will provide notice on this page and via email or other means at least six months in advance.