Skip to main content

Login via Mobile number - verify user (select ABHA)

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

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

Flow: Login - Mobile Number - step 3 of 3

  • Previous: *Login via Mobile number - verify OTP*
  • Next: none (last call of this flow)

---

This API is used to verify the selected ABHA user during the login journey after the user has searched or identified available ABHA accounts. 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

The access token from POST /api/hiecm/gateway/v3/sessions, sent with a Bearer prefix.

Headers

T-tokenstringRequired

Short-lived token (Bearer <token>) returned by *Login via Mobile number - verify OTP*.

REQUEST-IDstringRequired

Unique UUID for every request.

TIMESTAMPstringRequired

Current UTC timestamp in ISO-8601 format.

Body

ABHANumberstringRequired

The 14 digit ABHA number to sign in to, chosen from the accounts the previous call listed.

txnIdstringRequired

The transaction ID returned by the previous call in this flow.

Responses

200

The 200 response code indicates a successful request.

**

tokenstring
expiresIninteger
refreshTokenstring
refreshExpiresIninteger
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.

Types of OTP Verification Errors:

Invakid T-Token: This error occurs when the T -token.

Verify OTP - Invalid Abha Number: This error occurs when the authentication methods provided for invalid abha number are invalid.

Error codes for this module

messagestring
timestampstring
401

Unauthorized: 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

codestring
messagestring
descriptionstring
500

Internal Server Error

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