POST
/
api
/
v1
/
verify-otp
{
  "identifierString": "customer@example.com",
  "otp": "123456",
  "methodId": "email-test-12345678-1234-1234-1234-123456789012"
}

{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyLXRlc3QtMTIzNDU2NzgtMTIzNC0xMjM0LTEyMzQtMTIzNDU2Nzg5MDEyIiwiaWF0IjoxNzA1MzE4ODAwLCJleHAiOjE3MDUzMjI0MDB9.example-signature"
}

​
Request Body

​
identifierString
string
required
The same email or phone number used in the login request
​
otp
string
required
The 6-digit OTP code sent to the customer
​
methodId
string
required
The method ID returned from the login-customer endpoint
{
  "identifierString": "customer@example.com",
  "otp": "123456",
  "methodId": "email-test-12345678-1234-1234-1234-123456789012"
}

{
  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJ1c2VyLXRlc3QtMTIzNDU2NzgtMTIzNC0xMjM0LTEyMzQtMTIzNDU2Nzg5MDEyIiwiaWF0IjoxNzA1MzE4ODAwLCJleHAiOjE3MDUzMjI0MDB9.example-signature"
}
The returned token is a JWT that must be included in the Authorization: Bearer {token} header for subsequent authenticated requests to customer endpoints.

Authorizations

​
X-API-Key
string
header
required

Body

application/json

Response

OTP verified successfully.

The response is of type object.