New Contract for PAN-Aadhaar Link Status

We have deployed a new contract for this API. Consequently, the previous contract has been marked deprecated. The API contract has changed as per our POST to GET thought process, which you can read about here.

API Name	New Contracts	Deprecated Contracts
PAN-Aadhaar Link Status	{sandbox_host}/kyc/pan-aadhaar/status	{sandbox_host}/it-tools/pans/{pan}/pan-aadhaar-status

Changes in the API request

The API is now a POST request, requiring pan and aadhaar_number to be passed in the request body. Furthermore, the following keys are now required as well:

@entity
consent
reason

You can compare the response as per the old and new contract below:

curl --request POST \
     --url https://api.sandbox.co.in/kyc/pan-aadhaar/status \
     --header 'accept: application/json' \
     --header 'authorization: eyJhbGciOi....' \
     --header 'content-type: application/json' \
     --header 'x-api-key: key_live_T43....' \
     --data '
{
  "@entity": "in.co.sandbox.kyc.pan_aadhaar.status",
  "pan": "XXXPX1234A",
  "aadhaar_number": "123456789012",
  "consent": "Y",
  "reason": "For KYC"
}
'

curl --request GET \
     --url 'https://api.sandbox.co.in/it-tools/pans/XXXPX1234A/pan-aadhaar-status?aadhaar_number=123456789012' \
     --header 'accept: application/json' \
     --header 'authorization: eyJhbGciOi....' \
     --header 'x-api-key: key_live_T43....' \

Changes in the API response

The following keys have been added

@entity
aadhaar_seeding_status

You can compare the response as per the old and new contract below:

{
  "code": 200,
  "timestamp": 1614696176218,
  "transaction_id": "611335dc-8be4-40d1-8438-b86526462939",
  "data": {
    "@entity": "in.co.sandbox.kyc.pan_aadhaar.status.response",
    "aadhaar_seeding_status": "y",
    "message": "Your PAN is linked to Aadhaar Number  XXXX XXXX 9999."
  }
}

{
  "code": 200,
  "timestamp": 1614696176218,
  "transaction_id": "611335dc-8be4-40d1-8438-b86526462939",
  "data": {
    "message": "Your PAN <AAXXXXXX9A> is linked to Aadhaar number <XXXXXXXX9999>"
  }
}

Discontinuation of old contracts

The old contracts have been deprecated and will be discontinued soon. Timelines will be communicated.