Integration guide
Your page.
One script from our server.
Add this code where verification should appear. The SDK renders directly on your page and loads its styles, runtime, WASM, and model from the same PROOViD server.
01 · Frontend
Copy this into your page
No framework installation or inline JavaScript is required. The URL shown points to this running server. Use your deployed PROOViD server URL for production.
data-session-endpoint is a route on your own website. Keep session tokens in memory; never put a token or API key in this markup.
<div data-proovid
data-session-endpoint="/api/verification-session"
data-active-reentry-endpoint="/api/verification-active-reentry"></div>
<script src="https://sdk-uat.proovid.net/_proovid/browser/proovid-sdk-0.3.3.js"></script>
<script>ProovidID.mountAll()</script>
02 · Backend
Provide a session token
Implement POST /api/verification-session on your backend. Authenticate your customer, select the configured flow, and create a PROOViD session using your private API key. Return only its short-lived access.token in this response, with Cache-Control: private, no-store.
For opted-in passive-to-active restart, implement POST /api/verification-active-reentry. Bind its sourceSessionId to your authenticated applicant, call the buyer-only active-reentry API with your private key, and return the new { sdkToken }. The SDK asks the applicant to continue, clears the old mount and starts the fresh active flow. Omit this attribute if your application handles the restart itself.
PROOViD hosts the public verification proxy. Register your website origin on the SDK server using NUXT_PROOVID_HOSTED_ALLOWED_ORIGINS before connecting a different website.
HTTP 200
Content-Type: application/json
Cache-Control: private, no-store
{ "sdkToken": "<access.token from PROOViD>" }
03 · Live example
The same single script, running here
This example uses our demonstration session endpoint with the Uzbekistan workflow. Your integration uses your authenticated backend endpoint above. Start verification to try the actual SDK.
Closing releases the camera and stops local requests. Checks already submitted continue on the server. Verification decisions are delivered to your backend.