This API operates on a skip logic basis. If the mobile number provided in the second step differs from the one linked to the Aadhaar, this API will be used to verify the new mobile number.
The API requires a Bearer token (JWT) for authentication.
Eka User ID (OID)
Partner User ID
Partner HIP ID
OID is used to Identify the user.
OK
Abha profiles of the user.
Refresh token of the user, issued by abdm
abha_end, confirm_mobile_otp, abha_select, abha_create Abha token of the user, issued by abdm
Transaction ID required for the next API call.