OTP Authentication

Integrate secure Uvio-based login into your platform. Users receive a one-time code in the Uvio mobile app — no passwords needed.

For full endpoint details, parameters, and error codes — see the API Reference (OTP section).

Integration Flow

OTP authentication lets you verify Uvio users on your platform in two API calls.

1

User enters email or username

On your site, the user provides their Uvio email or username.

2

You request an OTP

Your server calls POST /otps with the user identifier.

3

User receives the code

A 6-digit code arrives in the Uvio mobile app. The code is valid for 10 minutes.

4

You verify the code

Your server calls POST /otp-verifications with the code. On success you receive user data: id, email, first_name, last_name.

Legal Requirements

Before the user enters the OTP code on your platform, your interface must include the following:

Required UX Disclosures
  • Data disclosure: state which user data will be transferred to your company (ID, email, first name, last name).
  • Link to your privacy policy — required on the OTP entry screen.
  • Link to Uvio notice: https://law.uvio.chat/rf/ru/shared/login-with-uvio/
  • Subscription: if successful verification creates or reactivates a subscription to your company in Uvio, disclose this upfront.
When a Separate Checkbox Is Needed
  • If data is used only for login, registration, and account support — no separate checkbox required.
  • If data is used for marketing, promotional messaging, or profiling — you must obtain separate user consent.