Skip to main content

Re-KYC - send Aadhaar OTP

Starts Re-KYC of a logged-in ABHA (X-token). UIDAI sends an OTP to the Aadhaar-linked mobile.

POST/abha/api/v3/profile/account/request/otp

Endpoint: POST /abha/api/v3/profile/account/request/otp

Flow: Profile - Re-KYC - step 1 of 2

  • Previous: none (first call of this flow)
  • Next: Re-KYC - verify Aadhaar OTP

Headers (plus Authorization: Bearer <gateway token>):

Header Required Description
X-token yes User token (Bearer <token>) received after ABHA creation / login.
REQUEST-ID yes Unique UUID for every request.
TIMESTAMP yes Current UTC timestamp in ISO-8601 format.

Request body for this use case:

Field Value / Type Required Description
scope ["ABHA-profile", "re-KYC"] yes Scope that selects this use case. Send exactly the values listed for this API.
loginHint "ABHA-number" yes Type of identifier sent in loginId.
loginId string yes Identifier value, RSA-encrypted with the ABHA public certificate.
otpSystem "Aadhaar" yes System that generates and delivers the OTP (Aadhaar = UIDAI, ABDM = ABDM).

Responses

200

Success: ReKYC-Send OTP

txnIdstring
messagestring
400

Bad Request (request validation failed): Re-KYC- Invalid Scope; Re-KYC- Invalid X-token; Re-KYC- Invalid LoginId; Re-KYC- Invalid Login Hint

Error codes for this module

Invalid Scopestring
timestampstring
401

Unauthorized (invalid / expired gateway token, X-token or benefit access): Invalid access token

Everything returns 401

codestring
messagestring
descriptionstring
500

Internal Server Error.

Error codes for this module