PAN Aadhaar Link Status

API reference

curl -X POST "https://__mock__/verification/v1/panaadharlinkstatus/uniqueaadhar" \  -H "Content-Type: application/json" \  -d '{    "aadhar": "stringstring",    "pan": "stringstri"  }'

{
  "requestid": "string",
  "result": {
    "linked": true,
    "message": "string"
  }
}

{
  "detail": {},
  "message": "string"
}

{
  "detail": {},
  "message": "string"
}

Overview

Call POST /verification/v1/panaadharlinkstatus/uniqueaadhar from your backend with Authorization: Bearer <token> and JSON pan (10 chars), aadhar (12 digits), and optional consent (Y or N). On 200 OK, read result.linked (boolean) and result.message for the outcome text, plus requestid for support.

Key features

• Regulatory alignment: Supports scenarios that require link status between identifiers.
• Aadhaar handling: Treat aadhar as sensitive; store only under vault or tokenization policies your compliance team defines.

Implementation

Step 1: Call from your backend

POST /verification/v1/panaadharlinkstatus/uniqueaadhar HTTP/1.1
Host: <verification-api-base-url>
Authorization: Bearer <token>
Content-Type: application/json

{
  "pan": "ABCDE1234F",
  "aadhar": "123456789012",
  "consent": "Y"
}

Step 2: Use result

Branch your workflow on linked and persist requestid for audits.

Error handling

Security notes

• Never send full Aadhaar to browser clients or third-party analytics.

Benefits

• Single API call for link status when you already hold both identifiers under policy.

Next steps

• Authenticate
• Verification API index