Skip to main content
Integration reference for VU’s identity products. Everything below is written for whoever is going to write the code: endpoints, contracts, status codes, and the traps that only show up in production.
The VU Identity Link API is only available on the Premium and Pro plans. The Basic plan has no API access: POST /oauth/token answers 401 invalid_client. See Plans for what each plan includes.

VU Identity Link

End-to-end identity verification. Single-use links, document capture, OCR, liveness, and adaptive flow. One integration covers the whole journey.OAuth2 · REST · Webhooks

VU Cloud Services

APIs you integrate one at a time. ID Analysis reads the document, Face Analysis compares the faces, Facial Antispoofing confirms the selfie is a real person, and Connection Fingerprint identifies the device.Api-Key · REST · No SDK · Available now

1. Verify anyone in three steps

Create a link, share it, read the result. POST /links hands you a linkUrl you can send however you already reach your customer — email, WhatsApp, SMS, or a QR code. No app to install, no SDK to ship: it runs in the browser they already have.

2. Their documents never travel through WhatsApp

You share a link, not an ID photo. The document and the selfie go straight to VU inside the link’s own session, which is single-use and closes on a timer you set. Past that window the API answers 410 for the record and 404 for the images, whatever the messaging app still holds.

3. Go Premium and integrate by API

OAuth2 client credentials, a REST API, and webhooks signed with HMAC-SHA256 so your server can trust what it receives. Premium raises the quota to 100 verifications a month and unlocks full branding — your name, your logo, your color on every screen your customer sees.

4. Go Pro and have it fit your rules

Support sets your verification quota and both expiration windows to the exact values you need, in minutes rather than fixed options. Pro is also the only plan that can run somewhere other than the shared SaaS.

5. Returning customers verify with a selfie

Adaptive flow routes a customer who already verified to a face-only branch and skips the document capture entirely. The status endpoint reports which branch ran as method: FACE or DOCUMENT. Available from version 2.2.0.

Get started in five minutes

The status endpoint is public and has required the linkId query parameter since version 2.2.0. It carries no Authorization header. Details in Authentication and KYC.

Go straight to what you need

Base URLs

Api-keys and clientSecret values live in your backend, in a secrets manager. Never inside a mobile app or a frontend bundle: anyone can extract them from the binary.

Resources

Changelog

Versions, behavior changes, and migration guidance.

Wiki

Additional internal documentation for VU teams.

Support

Write in with the transaction id, the environment, and the timestamp.

VU Security is Latin America’s digital identity platform. Non-technical material — solutions by use case, industries, certifications, and about VU — lives on vusecurity.com.
Last modified on September 9, 2026