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"
import requests
import json
url = "https://production.deepvue.tech/v1/mobile-intelligence/mobile-to-uan-list?mobile_number=example_string"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN (JWT)",
"x-api-key": "YOUR_API_KEY"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://production.deepvue.tech/v1/mobile-intelligence/mobile-to-uan-list?mobile_number=example_string", {
method: "GET",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN (JWT)",
"x-api-key": "YOUR_API_KEY"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("GET", "https://production.deepvue.tech/v1/mobile-intelligence/mobile-to-uan-list?mobile_number=example_string", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN (JWT)")
req.Header.Set("x-api-key", "YOUR_API_KEY")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://production.deepvue.tech/v1/mobile-intelligence/mobile-to-uan-list?mobile_number=example_string')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN (JWT)'
request['x-api-key'] = 'YOUR_API_KEY'
response = http.request(request)
puts response.body
{
"code": 200,
"timestamp": 1738039208921,
"transaction_id": "a20d6da16cb445dbb372e22373b4145f",
"sub_code": "SUCCESS",
"message": "UAN Number List successfully fetched",
"data": {
"uan_numbers": [
"1007445347444",
"1009462376721"
]
}
}
{
"code": 200,
"timestamp": 1737920869343,
"transaction_id": "8e6637f1d8834c22bcece74808b63437",
"sub_code": "DETAILS_NOT_FOUND",
"message": "No linked UAN found"
}
{
"error": "Bad Request",
"message": "The request contains invalid parameters or malformed data",
"code": 400,
"details": [
{
"field": "email",
"message": "Invalid email format"
}
]
}
{
"detail": "Not authenticated"
}
{
"detail": "Not a valid token"
}
{
"code": 422,
"timestamp": 1737920868278,
"transaction_id": "a00dfc26eaf744bd98f442af2d91b70d",
"sub_code": "INVALID_MOBILE_NUMBER",
"message": "Invalid Mobile Number Pattern"
}
{
"code": 500,
"timestamp": null,
"transaction_id": "string",
"sub_code": "INTERNAL_SERVER_ERROR",
"message": "Internal Server Error"
}
{
"code": null,
"timestamp": null,
"transaction_id": "string",
"message": "Source Unavailable"
}
/v1/mobile-intelligence/mobile-to-uan-list
ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
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
Bearer token (JWT). ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
API Key for authentication. The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Query Parameters
Responses
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).
Last updated 4 weeks ago
Built with Documentation.AI