Login

This endpoint allows users to log in to the Digital Identity system using their phone number and password. If the user is logging in from a new device, they may be required to enter an OTP sent via SMS.

Workflow for Login Endpoint

  1. User Initiates Login: The user sends a POST request to the /Login endpoint with their geoLocation, imei, phoneNumber, and password.

  2. Server Validation:

    • The server validates the provided phoneNumber and password.

    • If logging in from a new device, the server may require an OTP sent to the user's phone number.

  3. Response:

    • If the credentials are correct and any required OTP is verified, the server responds with an access token and user details.

    • If the credentials or OTP are incorrect, or any required fields are missing, an appropriate error response is returned.

User login to the Digital Identity system

post
Body
phoneNumberstringRequired
passwordstring | nullableOptional
imeistringRequired
imsistring | nullableOptional
phoneNumberOtpRequestIdstring | nullableOptional
phoneNumberOtpstring | nullableOptional
isPhone2FAEnabledbooleanOptional
smsProviderinteger · enumOptionalPossible values:
Responses
200

Success

post
/api/DigitalIdentity/Login
200

Success

To refresh the access token upon its expiration, you can use the below endpoint.

post
Body
refreshTokenstring | nullableOptional
Responses
200

Success

post
/api/DigitalIdentity/RefreshToken
200

Success


Admin login to the Digital Identity system

post
Body
tenancyNamestring · max: 256Required
userNameOrEmailAddressstring · max: 256Required
passwordstring · max: 32Required
Responses
200

Success

post
/api/credentials/Login
200

Success

To refresh the access token upon its expiration, you can use the below endpoint.

post
Body
refreshTokenstring | nullableOptional
Responses
200

Success

post
/api/credentials/RefreshToken
200

Success

Last updated