Compatibility matrix
Choose the VOVE ID SDK for your client platform.
Use the SDK guide for your client platform and install the package version your team has tested and approved. Check that version's release notes for version-specific changes.
Shared lifecycle
Your backend creates a session with
POST /v2/sessions.The intended client receives the short-lived token and matching public key.
The client initializes its SDK and starts the journey.
Your backend receives and verifies the webhook.
Your backend retrieves
GET /v2/users/{refId}before applying the final decision.
Each SDK uses its own enum names and casing. Follow the platform guide and the declarations shipped with the installed package.
Upgrades
Before upgrading, review the SDK release notes, pin the chosen version, compile a minimal integration, test permissions on physical devices, exercise every documented result branch, and repeat the webhook and result-retrieval flow.
Last updated