Repository navigation
Add liveness sessions for API contract 2.0.0 - #9
Merged
Merged
Conversation
createLivenessSession (named in each language's style) starts a session and returns its ID, the challenges to show in order and the expiry. completeLivenessSession submits the frames with mirrored and returns isLive, the steps and, when the session passed, the liveness token used for enrolment. LIVENESS_SESSION_INVALID surfaces as the typed API error. Completion is retried only on 429: any other answer, 503 included, means the session was already used up, so a retry could only fail. BREAKING: activeLiveness results no longer carry the token fields, because the API stopped returning them. This is a new major version, pinned to contract 2.0.0, with migration notes in the CHANGELOG.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
createLivenessSession (named in each language's style) starts a session
and returns its ID, the challenges to show in order and the expiry.
completeLivenessSession submits the frames with mirrored and returns
isLive, the steps and, when the session passed, the liveness token used
for enrolment. LIVENESS_SESSION_INVALID surfaces as the typed API error.
Completion is retried only on 429: any other answer, 503 included, means
the session was already used up, so a retry could only fail.
BREAKING: activeLiveness results no longer carry the token fields,
because the API stopped returning them. This is a new major version,
pinned to contract 2.0.0, with migration notes in the CHANGELOG.
Verification
Part of the liveness-challenges change (backend, engine, console and the five SDKs ship together).