Error Reference Document

API Error Description Suggested Instructions to the user

The provided Personal Identity information didn't match. Please re-enter
"Pi" (basic) attributes of demographic data did not
100 your
match
<name, lname, gender, dob, dobt, age, phone, email> details correctly.

The provided Personal Address information didn't match.Please re-enter

"Pa" (address) attributes of demographic data did
200 your <co (care of), house, street, lm (land mark), loc (locality), vtc, subdist,
not match
dist, state, pc (postal pin code), po (post office)>.

Ensure correct aadhaar number is entered for authentication

Try authenticating using different finger in case of biometric mismatch
Follow best practices
300 Biometric data did not match
AUA application must invoke Best Finger Detection to find the best finger
for authentication

Resident should provide distinct fingers (two different fingers) for "two
310 Duplicate fingers used
finger" authentication.
Resident should provide distinct fingers (two different Iris) for "two Iris"
311 Duplicate Iris used
authentication.

FMR and FIR ( Finger Image Record) cannot be Technical Issue with AUA Application. AUA Application must follow the
312
used in same transaction UIDAI API Specification.

Single FIR ( Finger Image Record)record contains Technical Issue with AUA Application. AUA Application must follow the
313
more than one finger UIDAI API Specification.

Number of FMR(Finger Minutiae Record )/FIR ( Technical Issue with AUA Application. AUA Application must follow the
314
Finger Image Record) should not exceed 10 UIDAI API Specification.

Number of IIR ( Iris Image Record) should not Technical Issue with AUA Application. AUA Application must follow the
315
exceed 2 UIDAI API Specification.

Number of FID ( Face Image Data )should not Technical Issue with AUA Application. AUA Application must follow the
316
exceed 1. UIDAI API Specification.

Resident must unlock his biometrics

330 Biometrics locked by Aadhaar holder by invoking Resident portal or M-Aadhaar and get his biometric unlocked
and get himself authenticated
 Resident must ensure that the correct OTP value is provided for
authentication .
400 "OTP" validation failed The resident is advised to generate new OTP in case of repeated
authentication failures.

“txn” value did not match with “txn” value used in Technical Issue with AUA Application. AUA Application must follow the
402
Request OTP API. UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
500 Invalid Skeyencryption
UIDAI API Specification.
Invalid value for "ci" attribute in "Skey" Technical Issue with AUA Application. AUA Application must follow the
501
element UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
502 Invalid Pid Encryption
UIDAI API Specification.

Technical Issue with AUA Application. AUA Application must follow the
503 Invalid HMac encryption
UIDAI API Specification.

Session key re-initiation required due to expiry or Technical Issue with AUA Application. AUA Application must follow the
504
key out of sync UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
505 Synchronized Skey usage is not allowed
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
510 Invalid Auth XML format
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
511 Invalid PID XML format
UIDAI API Specification.
Resident concent to do aadhaar based authentication must be mandatorily
Invalid Aadhaar holder consent in “rc” attribute of taken by the AUA application.
512
“Auth” Without explicit informed consent of the Aadhaar holder AUA/Sub-AUA
application should not call this API
Technical Issue with AUA Application. AUA Application must follow the
513 Invalid Protobuf Format
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
520 Invalid “tid” value
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
521 Invalid “dc” code under Meta tag
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
524 Invalid “mi” code under Meta tag
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
527 Invalid “mc” code under Meta tag.
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
528 Device - Key Rotation policy
UIDAI API Specification.
 Technical Issue with AUA Application. AUA Application must follow the
530 Invalid authenticator code
UIDAI API Specification.

Technical Issue with AUA Application. AUA Application must follow the
540 Invalid Auth XML version
UIDAI API Specification.

Technical Issue with AUA Application. AUA Application must follow the
541 Invalid PID XML version
UIDAI API Specification.

Technical Issue with AUA Application. AUA Application must follow the
542 AUA not authorized for ASA.
UIDAI API Specification.

Technical Issue with AUA Application. AUA Application must follow the
543 Sub-AUA not associated with "AUA"
UIDAI API Specification.

Technical Issue with AUA Application. AUA Application must follow the
550 Invalid "Uses" element attributes
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
552 WADH Validation failed
UIDAI API Specification.

Registered devices currently not supported. This Technical Issue with AUA Application. AUA Application must follow the
553
feature is being implemented in a phased manner. UIDAI API Specification.

Technical Issue with AUA Application. AUA Application must follow the
554 Public devices are not allowed to be used
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
555 rdsId is invalid and not part of certification registry
UIDAI API Specification.
rdsVer is invalid and not part of certification Technical Issue with AUA Application. AUA Application must follow the
556
registry. UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
557 dpId is invalid and not part of certification registry.
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
558 Invalid dih
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
559 Device Certificate has expired
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
560 DP Master Certificate has expired
UIDAI API Specification.

Request expired ("Pid-

Technical Issue with AUA Application. AUA Application must follow the
561 >ts" value is older than N hours where N is a
UIDAI API Specification.
configured threshold in authentication server)
 Timestamp value is future time (value specified
Technical Issue with AUA Application. AUA Application must follow the
562 "Pid->ts" is ahead of authentication server time
UIDAI API Specification.
beyond acceptable threshold)

Duplicate request (this error occurs when exactly Technical Issue with AUA Application. AUA Application must follow the
563
same authentication request was re-sent by AUA) UIDAI API Specification.

Technical Issue with AUA Application. AUA Application must follow the
564 HMAC Validation failed
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
565 AUA License key has expired
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
566 Invalid non-decryptable license key
UIDAI API Specification.
Invalid input (this error occurs when some
unsupported characters were found in Indian Technical Issue with AUA Application. AUA Application must follow the
567
language values, UIDAI API Specification.
"lname" or "lav")
Technical Issue with AUA Application. AUA Application must follow the
568 Unsupported Language
UIDAI API Specification.

Digital signature verification failed (this means that

Technical Issue with AUA Application. AUA Application must follow the
569 authentication request XML was modified after
UIDAI API Specification.
it was signed)

Invalid key info in digital signature (this means that

certificate used for signing the authentication
request is not valid – it is either expired, or does Technical Issue with AUA Application. AUA Application must follow the
570
not UIDAI API Specification.
belong to the AUA or is not created by an
approved Certification Authority)

Invalid biometric position (This error is returned if

biometric position value - "pos" attribute in "Bio" Technical Issue with AUA Application. AUA Application must follow the
572
element - is not applicable for a given biometric UIDAI API Specification.
type - "type" attribute in "Bio" element.)

Technical Issue with AUA Application. AUA Application must follow the
573 Pi usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
574 Pa usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
575 Pfa usage not allowed as per license
UIDAI API Specification.
 Technical Issue with AUA Application. AUA Application must follow the
576 FMR usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
577 FIR usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
578 IIR usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
579 OTP usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
580 PIN usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
581 Fuzzy matching usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
582 Local language usage not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
586 FID usage not allowed as per license.
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
587 Name space not allowed.
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
588 Registered device not allowed as per license
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
590 Public device not allowed as per license.
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
710 Missing "Pi" data as specified in "Uses"
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
720 Missing "Pa" data as specified in "Uses"
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
721 Missing "Pfa" data as specified in "Uses"
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
730 Missing PIN data as specified in "Uses"
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
740 Missing OTP data as specified in "Uses"
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
800 Invalid biometric data
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
810 Missing biometric data as specified in "Uses"
UIDAI API Specification.

Your Biometric data is not available in CIDR.

Missing biometric data in CIDR for the given
811 Please contact UIDAI helpdesk to inform about the issue and to
Aadhaar number
understand the steps for the updation of biometric information in CIDR.
 Resident has not done "Best Finger Detection". You have not done best finger detection so kindly proceed with the BFD
Application should initiate BFD application to help process for successful authentication.
812
resident identify their best fingers. See Aadhaar Refer Aadhaar Best Detection API specifications for details on the BFD
Best Finger Detection API specification. process.

Missing or empty value for "bt" attribute in "Uses" Technical Issue with AUA Application. AUA Application must follow the
820
element UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
821 Invalid value in the "bt" attribute of "Uses" element
UIDAI API Specification.
Invalid value in the “bs” attribute of “Bio” element Technical Issue with AUA Application. AUA Application must follow the
822
within “Pid” UIDAI API Specification.

No authentication data found in the request (this

Technical Issue with AUA Application. AUA Application must follow the
901 corresponds to a scenario wherein none of the
UIDAI API Specification.
auth data – Demo, Pv, or Bios – is present)

Invalid "dob" value in the "Pi" element (this

corresponds to a scenarios wherein "dob" attribute
Technical Issue with AUA Application. AUA Application must follow the
902 is not of the format "YYYY" or "YYYY-MM-DD", or
UIDAI API Specification.
the
age of resident is not in valid range)
Technical Issue with AUA Application. AUA Application must follow the
910 Invalid "mv" value in the "Pi" element
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
911 Invalid "mv" value in the "Pfa" element
UIDAI API Specification.
Technical Issue with AUA Application. AUA Application must follow the
912 Invalid "ms" value
UIDAI API Specification.
Both "Pa" and "Pfa" are present in the
Technical Issue with AUA Application. AUA Application must follow the
913 authentication request (Pa and Pfa are mutually
UIDAI API Specification.
exclusive)
Technical Issue with AUA Application. AUA Application must follow the
UIDAI API Specification.
940 Unauthorized ASA channel

Technical Issue with AUA Application. AUA Application must follow the
941 Unspecified ASA channel
UIDAI API Specification.
Technical Issue at UIDAI end . AUA/Resident can reach UIDAI contact
950 OTP store related technical error center for more details.
Voice @ 1947 and e-Mail “[email protected]”
 Technical Issue at UIDAI end . AUA/Resident can reach UIDAI contact
951 Biometric lock related technical error center for more details.
Voice @ 1947 and e-Mail “[email protected]”
Your Aadhaar number is suspended .AUA/Resident can reach UIDAI
995 Aadhaar suspended by competent authority contact center for more details.
Voice @ 1947 and e-Mail “[email protected]”

Your Aadhaar is cancelled , Resident shall visit Permanent Enrolment

Centre with document proofs and follow the re-enrollment process..
996 Aadhaar Cancelled
AUA/Resident can reach UIDAI contact center for more details.
Voice @ 1947 and e-Mail “[email protected]” .

Your Aadhaar is suspended, Resident shall visit Permanent Enrolment

Centre with document proofs and follow the enrolment update process.
997 Aadhaar Suspended
AUA/Resident can reach UIDAI contact center for more details.
Voice @ 1947 and e-Mail “[email protected]” .

Invalid Aadhaar Number 0r Non Availability of Ensure you have entered correct Aadhaar number. Please retry with
998
Aadhaar data correct Aadhaar number after sometime.