Integrate
Connect your backend to identity and age verification. Choose a journey and copy examples for your stack.
Loading integration status…
1Get an API keyChoose a server key
Create a scoped key for the backend that starts verification sessions. Store the secret on your server; it is shown only when created.
Manage API keys →Keys with sessions:create access can start sessions after verification is enabled.
2Choose a workflowSelect a journey
LetsGetVerified selects the active workflow from the journey you send when creating a session. A workflow ID is not required in the request.
3Add a webhookReceive signed status updates
Use an HTTPS destination to receive status.updated events. Verify the timestamp and HMAC signature before trusting the payload.
Signing secrets are shown once when created. This guide never reveals or copies them.
4Connect your appServer-side HTTP integration
Your backend creates a session and returns its verification URL to the browser. The browser can open that URL; a desktop user can continue on a phone through the QR handoff.
Set the value in your server secret manager. Never put an API key in browser code or commit it.
5Run your first verificationWaiting for the first session
Integration reference
API request format
POST /api/sessions accepts a viewer or creator journey, an AussiePorn account reference prefixed with that journey, and an AU or NZ issuing country. It returns a verification ID and applicant URL. GET /api/sessions/:id returns status with a key that has read access.
Webhook signature
Each event includes X-LGV-Event-ID, X-LGV-Timestamp in Unix seconds, and X-LGV-Signature as lowercase hex HMAC-SHA256 over timestamp + "." + raw JSON body. Compare in constant time and reject timestamps more than five minutes old.