Check a National ID in two calls
- Match or no match, never the record itself
- Four fields: NIN, full name, gender and date of birth
- Tokens last 30 minutes, so one token serves many checks
- Called from your server, so credentials never reach an app
How it works
-
Get a token
Your server sends its client ID and password and receives a token valid for 30 minutes.
-
Verify the details
Send the NIN, full name, gender and date of birth in Bikram Sambat, with the token.
-
Read the answer
The reply is match or no match. It never says which field was wrong.
A check
curl -H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{ "nin": "1234567890",
"fullName": "Sita Sharma",
"gender": "F",
"dobLoc": "२०५८-०५-१२" }' \
https://verify-nin-citizenportal.donidcr.gov.np/api/nin/verify
{ "detailMatch": true }Specifications
- Fields
- nin, fullName, gender, dobLoc
- nin
- 10 digits, no dashes
- Date of birth
- Bikram Sambat, Devanagari digits
- Reply
- detailMatch: true or false
- Token life
- 30 minutes
- Where to call from
- Your server
Questions
Do I get the person’s record back?
No. You send what the person says is true and receive match or no match. No record comes back.
Why does a wrong field not say which one was wrong?
The answer is deliberately a single yes or no, so the check cannot be used to discover someone’s details by trial.
What if one of the four fields is missing?
All four must be sent. If any is missing the answer is no match.
How do I get access?
Write to Ninja Infosys at info@ninjainfosys.com or 01-5922361.