Soliton Identity Verification
Two ways to integrate.
Both start with the same backend: your server creates a session, issues its hosted link and reads the result with your API key. Choose Standard, Medium, or High liveness in that server request, then choose how your user reaches the camera step. The same verification link works either way, in sandbox and production.
01
Choose your hand-off
Pick one; you can switch later without backend changes.
Set tier in the server helper, or checks[].configuration.liveness_tier on POST /api/v2/sessions: standard uses the camera, medium adds sound, and high adds sound and light. Choose your tier explicitly. Both methods below automatically use the selected tier; no separate SDK or endpoint is needed. See the tier contract.
Server + redirect
Use the v2 session API or server helper to create a check and its link. Send your user to the hosted page, then read the result on your server.
Web SDK (embedded)
Keep the user on your page: the same hosted flow in a full-screen overlay iframe instead of a redirect. A small browser library on top of the exact same backend API.
Not sure? Start with Server + redirect: it is the least code and needs nothing in the browser. You can move to the Web SDK later without touching your backend integration.
02
Before you start
What we need to provision your account.
Create a sandbox API key in the console and keep it on your server. Use your deployment’s API and verification origins. Sandbox and production have separate credentials, sessions and embedding permissions.
- Server + redirect: no embedding-origin registration is required. Your server issues the hosted link, and the user opens it as a page. The session API does not accept a customer return URL; your application can poll for completion while the user returns manually.
- Web SDK: send Soliton the exact origin (scheme, hostname and port) of the page embedding verification, including local development origins, and specify the account and environment. Nested embeds also need every ancestor origin registered for the same environment. Wildcards are not accepted.
- Results: save the session ID against your authenticated user. Read its result from your server, then apply your own access policy. Browser callbacks never authorize a user.
The optional Node.js helper creates the session and link in one function call. Raw API examples remain available for other languages. Sandbox checks use real camera captures; the console’s sample request/response drawer is illustrative.
For embedding setup, see Register your origins. A registered origin applies on the next page load; send yours before you start testing.