Verify a User OTP [v1]
This API helps you validate the OTP sent to a user as a response to resolve user. If the OTP is validated, the user token is provided which can be used in subsequent API calls
Request Body required
This is the mobile number of the user.
The user_agent is a characteristic string that lets servers and network peers identify the application, operating system, vendor, and/or version of the requesting user agent.
A unique numerical identifier for every device or network that connects to the internet. Typically assigned by an internet service provider (ISP), an IP address is an online device address used for communicating across the internet
This is a unique device id generated by the client using a standard library such as fingerprint.js
This is unique order_id generated in the response of create-order
This is the otp submitted by the user
- 200
- 4XX
- 5XX
When the OTP submission is successful, the response will be as below
Schema
Possible values: [true
]
This key will always be true
for a successful response
item object required
This is the user information fetched from Nimbbl depending on the user details shared during the resolve user API call
The unique internal id of the consumer
This is the email address of your consumer stored at Nimbbl
This is the first name of your consumer stored at Nimbbl
This is the last name of your consumer stored at Nimbbl
Default value: +91
This is the country code as defined by the Internation Telecom Union
This is the mobile number of your consumer shared by you
This is the unique identifier for the consumer on Nimbbl
This is the user token, you will need to add it to the Header for subsequent API calls
This is the expiry of the token, it is expressed in UTC. If the token has expired, you will need to create a new order
{
"success": true,
"item": {
"id": 1145,
"email": "wonderwoman@themyscira.gov",
"first_name": "Diana",
"last_name": "Prince",
"country_code": "+91",
"mobile_number": 9876543210,
"user_id": "user_78hsjkdhb2482ndk",
"token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjo0LCJleHAiOjE2MTc4ODkxMjJ9.mBz-d9hizuhLaIBVHYR8eGL5E9mJ0F2gsRfS5VNqrAw",
"token_expiration": "2021-01-09T09:49:57.715413"
}
}
When the OTP submission is not successful, the response will be as below
Schema
The HTTP error status
The message from the server explaining the error
error object
The HTTP error status
The message from the server explaining the error
This is the http status code
The transaction status
error object
The transaction status
The message from the server explaining the error
{}
When there is a problem on the server, the response will be as below
Schema
The HTTP error status
The message from the server explaining the error
{
"status": 500,
"error": "HTTP 500: Internal Server Error"
}