Use these methods to send an OTP code to the holder after enrollment.
The OTP delivery channel depends on the otpType set during enrollment:
- SMS — OTP sent via SMS to the holder's mobile number
- EMAIL — OTP sent via email
- WHATSAPP — OTP sent via WhatsApp to the holder's mobile number (requires LRA authorization and template configuration)
Methods:
- sendOtp — standard method
- sendOtpDisposable — deprecated, use
sendOtpinstead
Both methods return an empty body on success.
| HTTP Status | Description |
|---|---|
200 | OTP sent successfully. Response body is empty |
All errors below return HTTP 500.
| Error code | Description |
|---|---|
| 2 | Some required fields are missing |
| 6 | Generic exception — internal exception |
| 62 | The certIdOtp is not valid |
| 66 | The device OTP is not active |
| 71 | The device OTP is disabled |
| 85 | The deviceCode is not valid |
| 99 | OTP was not sent |
| 100 | The mobile phone number is not valid |
| 101 | SMS blocked by the watchlist |
| 102 | The email address is not valid |
| 103 | The OTP service has exceeded the timeout |
| 138 | The device OTP is not an SMS OTP device |
| 231 | OTP is blocked |
| 241 | LRA not authorized to use this OTP type |
| 240 | No email template configured for this LRA |
For authentication errors, see Authentication.
For details on how to handle errors, see How to handle errors.