Mobile Number to Name Lookup
Find the name linked to any Indian mobile number. Useful for identity verification, pre-fill onboarding, and fraud screening.
curl -X GET "https://production.deepvue.tech/v1/mobile-intelligence/mobile-to-name?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-name?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-name?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-name?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-name?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": 1738036065614,
"transaction_id": "4db2591f472a47679f46780a39e642c8",
"sub_code": "SUCCESS",
"message": "Name fetched successfully",
"data": {
"name": "MOSD NIHARIKA"
}
}
{
"code": 200,
"timestamp": 1738027653598,
"transaction_id": "ba5a47bfd6d44df5bac93ca7b5f76b38",
"sub_code": "DETAILS_NOT_FOUND",
"message": "Unable to fetch Name from Mobile Number"
}
{
"detail": "Inactive client_id"
}
{
"detail": "Not authenticated"
}
{
"detail": "Not a valid token"
}
{
"code": 422,
"timestamp": 1738036065229,
"transaction_id": "ae46cffd4e4647589749bcf05175a209",
"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-name
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
The Mobile to Name API retrieves the name associated with a given phone number. It enables businesses to fetch user identity information linked to a mobile number for verification and onboarding purposes.
The API accepts a mobile phone number as a query parameter and returns the associated user's name if available. The service searches against available data sources to match the provided number to registered user information.
Response outcomes
The API supports two primary success scenarios:
- Name successfully retrieved — Returns the matched name associated with the mobile number.
- Details not found — Returns a successful response but indicates no matching name exists for the provided number.
Last updated 4 weeks ago
Built with Documentation.AI