Notable changes to the platform, the public API, and the SDKs are recorded here. Entries are added as releases ship.
API key permission scopes, simplified
Section titled “API key permission scopes, simplified”The permission scopes you grant an API key are now fewer and clearer, grouped by what they control (verification, session tokens, reports, adjudication, configuration, compliance and billing). Every scope now has a plain-language description in the console and in Create an API key, and scopes that carry extra risk (full applicant data, the full-evidence report, skipping a verification step) are called out where you grant them.
A handful of scopes were renamed or combined as part of this change, and a few unused ones were removed. If you use API keys, check the scope names you grant against the current list and re-issue any key that still references an old name; the removed scopes were not gating anything. See Choosing scopes for your key for guidance on common integration patterns.
Identity document verification — biometric face check
Section titled “Identity document verification — biometric face check”The id_verification check now supports an optional biometric face
check. Configure it per workflow template with the Face match control:
- Selfie — a single selfie matched 1:1 against the document photo.
- Active liveness — a guided face scan (movement-based, no flashing lights) that confirms a real, present person before matching to the document.
The biometric check is strictly opt-in and the modes are mutually exclusive; the default stays document-only. Active liveness is processed within your region, with EU streams pinned to the EU region.
Reviewers can now view the captured identity-document images (front, back, and the biometric image) on the applicant detail page. Every view is authorized and audited, images are streamed through the console with no shareable link, and a deleted image shows an “Image removed” state.
See Choose the right check types, What the applicant sees, and Biometric data.