DIN to PAN Lookup
Retrieve the PAN number linked to a Director Identification Number. Cross-verify director identity for compliance checks.
curl -X GET "https://production.deepvue.tech/v1/business-compliance/din-to-pan?din_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/business-compliance/din-to-pan?din_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/business-compliance/din-to-pan?din_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/business-compliance/din-to-pan?din_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/business-compliance/din-to-pan?din_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": 1738135067385,
"transaction_id": "a1faecaf4cb64d6e9cf9113392203086",
"sub_code": "SUCCESS",
"message": "PAN details fetched successfully.",
"data": {
"din_number": "00000001",
"din_status": "Approved",
"pan_number": "AAAPT0002F",
"first_name": "RATAN",
"middle_name": "NAVAL",
"last_name": "TATA",
"date_of_birth": "1937-12-28",
"father_first_name": "NAVAL",
"father_middle_name": "HORMUSJI",
"father_last_name": "TATA",
"resident_of_india": "Y",
"membership_number": ""
}
}
{
"code": 200,
"timestamp": 1738135067385,
"transaction_id": "14e97f4d6d284a6ab3028bfc5e98110c",
"sub_code": "INVALID_ID_OR_NO_DATA_FOUND",
"message": "No Linked PAN found or Invalid DIN."
}
{
"detail": "Not authenticated"
}
{
"detail": "Invalid client_id, access Denied"
}
{
"detail": "Could not validate credentials"
}
{
"detail": "Incorrect client_id or client_secret"
}
{
"detail": "Not a valid token"
}
{
"detail": "Access forbidden"
}
{
"code": 422,
"timestamp": 1738135067385,
"transaction_id": "73082a6f0b6642caa9fa31610cea8995",
"sub_code": "INVALID_INPUT",
"message": "Invalid DIN Number"
}
{
"detail": "Internal Server Error"
}
{
"code": 500,
"timestamp": null,
"transaction_id": "string",
"sub_code": "SOURCE_FAILURE",
"message": "Source failure. Unable to validate."
}
/v1/business-compliance/din-to-pan
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 fetches the PAN Number and its details from the DIN Number. It enables verification of Director Identification Numbers by retrieving the associated Permanent Account Number information.
Successful responses return comprehensive director information including name components, date of birth, father's details, residency status, and associated PAN. The API also handles cases where no linked PAN exists or the provided DIN is invalid.
The API provides detailed error responses covering authentication failures, token expiration, invalid DIN formatting, and source system unavailability, with appropriate HTTP status codes and descriptive messages for troubleshooting.
Last updated 4 weeks ago
Built with Documentation.AI