Mobile Number to All UPI VPAs
Retrieve every UPI VPA linked to a mobile number across all payment apps. Comprehensive UPI discovery for fraud and compliance.
curl -X GET "https://production.deepvue.tech/v1/mobile-intelligence/mobile-to-multiple-upi?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-multiple-upi?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-multiple-upi?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-multiple-upi?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-multiple-upi?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": 1738007863554,
"transaction_id": "c257f23d964f4ae69d2d22b8ea310db1",
"sub_code": "SUCCESS",
"message": "Linked VPA Fetched Successfully.",
"data": {
"name_at_bank": "MOSD NIHARIKA",
"vpas": [
"8277182000@ptyes",
"8277182000@ibl",
"8277182000@axl",
"8277182000@ybl"
]
}
}
{
"code": 200,
"timestamp": 1738039208921,
"transaction_id": "c19286e562584a079d02b1e6bd708432",
"sub_code": "NO_VPA_LINKED",
"message": "No VPA Linked to Mobile Number."
}
{
"detail": "Not authenticated"
}
{
"detail": "Not a valid token"
}
{
"code": 422,
"timestamp": 1738007864132,
"transaction_id": "220f3ab2c4ea4e85b2c106924a96918f",
"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"
}
/v1/mobile-intelligence/mobile-to-multiple-upi
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 an account holder's name and all associated UPI identifiers by supplying their phone number. The service queries banking systems to identify all VPA (Virtual Payment Address) accounts linked to a specific mobile number.
Response outcomes
- Successful VPA discovery — When multiple UPI IDs are found, the response includes the account holder's registered bank name and a complete list of associated VPA addresses.
- No VPA found — When no UPI identifiers are linked to the provided mobile number, the API returns a specific status indicating this condition rather than an error.
The mobile number parameter must conform to valid phone number formatting standards. Requests with improperly formatted mobile numbers are rejected with a validation error response.
Last updated 4 weeks ago
Built with Documentation.AI