Create a verification session
Called from your backend with the secret key. Mints a single-use sst_ client token — returned exactly once, only its hash is stored. Products and thresholds are fixed here, server-side; the client can never change them. Fails fast with 402 if your balance is empty, so you never hand out a doomed token.
Authorizations
Your secret key (sk_live_…), server-side only. Also accepted as an x-api-key header.
Body
Which checks to run on the capture. Defaults to both. Liveness only = 1 credit, deepfake only = 2, both = 3.
face_liveness, deepfake Per-product threshold override, e.g. {"face_liveness": 0.6}. Values in [0,1]. Defaults to your org settings.
How long the session stays usable. Clamped to 60–3600.
60 <= x <= 3600Your own user/transaction id, echoed back on reads.
256Arbitrary JSON, at most 4096 bytes, echoed back on reads.
Response
Session created
verification_session vs_… id. Keep server-side to fetch the result later.
created sst_… token for the SDK. Returned exactly once — only its hash is stored.
Bound into the submit payload; also available to the SDK via session_info.
