Skip to main content
POST
/
abdm
/
na
/
v1
/
registration
/
aadhaar
/
verify
Verify OTP
curl --request POST \
  --url https://api.eka.care/abdm/na/v1/registration/aadhaar/verify \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "mobile": "<string>",
  "otp": "<string>",
  "txn_id": "<string>"
}'
{
  "eka": {
    "min_token": "<string>",
    "oid": null,
    "uuid": null
  },
  "hint": null,
  "profile": {
    "abha_address": "shyam@abdm",
    "abha_number": "12-3456-7856-8912",
    "address": null,
    "day_of_birth": null,
    "first_name": null,
    "gender": "M",
    "kyc_verified": null,
    "last_name": null,
    "middle_name": null,
    "mobile": null,
    "month_of_birth": null,
    "pincode": null,
    "year_of_birth": null
  },
  "refresh_token": null,
  "skip_state": "abha_end",
  "token": null,
  "txn_id": "<string>"
}

Authorizations

​
Authorization
string
header
required

The API requires a Bearer token (JWT) for authentication.

Headers

​
X-Pt-Id
string

Eka User ID (OID)

​
X-Partner-Pt-Id
string

Partner User ID

​
X-Hip-Id
string

Partner HIP ID

Body

application/json
​
mobile
string
required

10 digit mobile number to be linked with ABHA, this mobile number can be different from the mobile number linked with the Aadhaar. ABHA Created will be linked with this mobile number.

​
otp
string
required

OTP received on the mobile number.

​
txn_id
string
required

Transaction ID received in the previous api response.

Response

OK

​
eka
object

Eka IDs, will be present if SkipState is abha_end

​
hint
string | null

Hint for the mobile number

​
profile
object
​
refresh_token
string | null

Refresh token of the user, issued by abdm

​
skip_state
enum<string>
Available options:
abha_end,
confirm_mobile_otp,
abha_select,
abha_create
​
token
string | null

Abha token of the user, issued by abdm

​
txn_id
string

Transaction ID required for the next API call.