Verify with Privue

Privue runs the verification flow so you don’t have to. You start a verification for a user, redirect them to our hosted screens where they complete the steps, and poll our API for the result. You never handle the user’s documents or identity data directly.

How it works

Start a verification

POST /verifications with the user’s phone. We create their session and return a user_id.

Send the user to the hosted flow

Redirect them to https://verify.privue.ai/<your-slug>. They sign in with that phone and complete the steps on our screens.

Get the user back

When they finish we redirect them to your return_url with user_id and status appended. Treat these as display hints, not proof - always confirm by polling.

Read the result

Poll GET /verifications/{user_id} for status and GET /verifications/{user_id}/data for the collected data.

Quickstart

curl -X POST https://api.verify.privue.ai/verifications \
  -H "Authorization: Bearer $PRIVUE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "mobile": "+919876543210",
    "return_url": "https://yourapp.com/kyc/done",
    "reference_id": "your-own-id-123"
  }'
# 201 -> { "user_id": "user_2ab...", "reference_id": "your-own-id-123", "status": "created" }

curl https://api.verify.privue.ai/verifications/user_2ab... \
  -H "Authorization: Bearer $PRIVUE_API_KEY"
# 200 -> status, per-step progress, and lifecycle timestamps

curl https://api.verify.privue.ai/verifications/user_2ab.../data \
  -H "Authorization: Bearer $PRIVUE_API_KEY"
# 200 -> each step with its collected data and documents

New to the API? Read Authentication and the Verification lifecycle next. Every endpoint is documented under the API reference tab.

⌘I

Get started

Concepts

Reference

How it works

Quickstart

​How it works

​Quickstart

How it works

Quickstart