Skip to main content
VU Identity Link uses OAuth2 client credentials flow. You exchange your clientId and clientSecret for a short-lived Bearer token, then include that token in the Authorization header of every subsequent API request.

Where to find your credentials

Log in to the VU portal and call GET /users/me with a valid token. The response includes your clientId, clientSecret, and webhookSecret:
Treat clientSecret and webhookSecret as sensitive credentials. Never commit them to version control or expose them in client-side code.

Request a token

Send a POST request to /oauth/token with the Authorization: Basic header containing base64(clientId:clientSecret).

Token response

Using the token

Include the token in the Authorization header of every protected endpoint:
Cache the access_token and reuse it until it expires. Do not request a new token for every API call. A simple in-memory cache with a 3500-second TTL avoids unnecessary 401 errors and reduces latency.

Common errors

The full status-code reference lives on the Errors page.

Next steps

  • Create your first verification link in the Links guide.
  • Review the full list of authentication errors on the Errors page.
Last modified on August 28, 2026