Skip to main content
POST
/
v2
/
verification
/
pan-aadhaar-link
PAN-Aadhaar Linkage Verification
curl --request POST \
  --url https://bgv.konnectnxt.com/api/v2/verification/pan-aadhaar-link/ \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "pan_number": "ABCDE1234F",
  "aadhaar_number": "123456789012"
}
'
{
  "status": "success",
  "code": 200,
  "message": "Operation completed successfully",
  "data": {
    "is_linked": true,
    "message": "PAN & Aadhaar are linked"
  },
  "credits_used": 5,
  "credits_remaining": 95.5
}

Documentation Index

Fetch the complete documentation index at: https://docs.konnectnxt.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

The PAN-Aadhaar Linkage Verification API allows you to verify whether a specific PAN (Permanent Account Number) is linked to a given Aadhaar number. This is essential for compliance workflows, KYC processes, and ensuring that customers have completed mandatory PAN-Aadhaar linkage as per government requirements.

​
Key Features

  • Real-time Verification: Instant validation of PAN-Aadhaar linkage status
  • Simple Binary Result: Clear is_linked boolean response
  • Compliance Ready: Helps meet regulatory requirements for PAN-Aadhaar linkage
  • Detailed Messages: Descriptive messages explaining linkage status
  • Batch Support: Optional task_id and group_id for tracking bulk verifications

​
Government Requirement

As per Income Tax regulations, linking PAN with Aadhaar is mandatory for most taxpayers. This API helps verify compliance with this requirement.

​
Best Practices

  1. Format Validation: Validate PAN and Aadhaar formats client-side before API calls
  2. Case Sensitivity: Ensure PAN is in uppercase before sending
  3. Remove Spaces: Strip any whitespace from both PAN and Aadhaar numbers
  4. Error Handling: Implement retry logic for 500 and 503 errors with exponential backoff
  5. Compliance Checks: Use this API as part of your KYC/onboarding workflows
  6. Data Privacy: Handle PAN and Aadhaar data in compliance with data protection regulations

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
​
pan_number
string
required

PAN number (must be valid format - 5 uppercase letters, 4 digits, 1 uppercase letter)

Pattern: ^[A-Z]{5}[0-9]{4}[A-Z]$
Example:

"ABCDE1234F"

​
aadhaar_number
string
required

Aadhaar number (12 digits)

Pattern: ^\d{12}$
Example:

"123456789012"

Response

Verification completed successfully (both linked and not-linked cases)

​
status
enum<string>
required

Overall status of the API

Available options:
success,
error
​
code
integer
required

HTTP status code

Example:

400

​
message
string
required

Description of the response or error

Example:

"Invalid request parameters"

​
data
object
required
​
credits_used
integer
required

Represents the total number of credits used in this request.

Example:

3

​
credits_left
integer
required

Represents the remaining credits available for use.

Example:

4040