Skip to main content

Login verify user

Verify the selected ABHA user during the login journey after the user has searched or identified available ABHA accounts.

POST/abha/api/v3/profile/login/verify/user

It confirms that the user is proceeding with the correct ABHA number and validates the requested authentication flow. This step helps securely continue login for the chosen account and prevents access to the wrong profile. It is typically used when multiple ABHA accounts are available against the same mobile number or identifier. After successful verification, the user can proceed with the remaining authentication steps.

Authorizations

Authorizationbearer tokenRequired

Headers

T-tokenstringRequired
REQUEST-IDstringRequired
TIMESTAMPstringRequired

Body

ABHANumberstringRequired
txnIdstringRequired

Responses

200

The 200 response code indicates a successful request.<br><br> <p><strong>

400

The 400 response code indicates a bad request. In this context, it refers to various errors encountered during the OTP (One-Time Password) verification process due to invalid inputs or parameters. <p><br><strong>Types of OTP Verification Errors:</strong></p> <ol> <li> <p><strong>Invakid T-Token:</strong> This error occurs when the T -token.</p> </li> </ol> <ol start="2"> <li> <p><strong>Verify OTP - Invalid Abha Number:</strong> This error occurs when the authentication methods provided for invalid abha number are invalid.</p> </li> </ol>

Error codes for this module

401

<strong>Unauthorized:</strong><br> Indicates that the request requires user authentication. The server returns a 401 status code when the client has not provided valid authentication credentials.

Everything returns 401

500

<b>Internal Server Error</b><br><br> An Internal Server Error (500) indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.

Error codes for this module