Mobile Number IntelligenceMobile To UAN List

Mobile Number to All UANs

Retrieve all Universal Account Numbers linked to a mobile number. Covers multiple employers and historical EPFO accounts.

curl -X GET "https://production.deepvue.tech/v1/mobile-intelligence/mobile-to-uan-list?mobile_number=example_string" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN (JWT)" \
  -H "x-api-key: YOUR_API_KEY"
{
  "code": 200,
  "timestamp": 1738039208921,
  "transaction_id": "a20d6da16cb445dbb372e22373b4145f",
  "sub_code": "SUCCESS",
  "message": "UAN Number List successfully fetched",
  "data": {
    "uan_numbers": [
      "1007445347444",
      "1009462376721"
    ]
  }
}
GET
/v1/mobile-intelligence/mobile-to-uan-list
GET
Bearer Token (JWT)
Bearer Tokenstring
Required

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
API Key (header: x-api-key)
x-api-keystring
Required

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token (JWT). ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .

header
x-api-keystring
Required

API Key for authentication. The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.

Query Parameters

Responses

codeinteger
timestampinteger
transaction_idstring
sub_codestring
messagestring
dataobject

Overview

This API retrieves all Unique Account Number (UAN) records associated with a specific phone number. The service queries worker registration data to surface all linked UAN identifiers.

The API accepts a mobile number as input and returns either a list of UAN numbers connected to that phone number, or a "not found" response if no linked UANs exist in the system.

Response outcomes

Successful responses include a transaction ID, timestamp, and status code. The service may return HTTP 200 even when no data is found, distinguishing success through the sub_code field (either SUCCESS or DETAILS_NOT_FOUND).