post https://connect.routee.net/viber/otp
After authentication, you can make a request to the Viber OTP endpoint to send an OTP.
RESPONSE PARAMETERS
KEY | DESCRIPTION |
---|---|
trackingId | A unique tracking identifier for the OTP request. Used for logging and tracking. |
to | The recipient’s phone number, confirming who the OTP was sent to. |
from | The sender's name or identifier. |
country | The country code or name of the recipient’s country. |
status | The status of the OTP request, containing: |
status.status | The current status of the OTP, e.g., "QUEUED" (waiting to be sent). |
status.date | The timestamp when the status was updated. |
applicationName | The name of the application sending the OTP. |
direction | The direction of the message, typically "Outbound". |
ttl | Time-to-live in seconds for the OTP message, matching the value provided in the request. |
seq | The sequence number, matching the value provided in the request. |
label | The label or type of the message, such as "transactional", confirming the purpose of the OTP. |
type | The type of OTP message, such as "PRIMARY_ONLY", confirming the message type. |
templateId | The template ID used for the OTP message, matching the template in the request. |
templateParams | The parameters used in the template, such as the OTP pin. |
templateParams.pin | The PIN number |
templateLang | The language used in the template, confirming the language of the OTP message. |
ERROR CODES
STATUS | DESCRIPTION |
---|---|
401 | Invalid or expired access token.. |
403 | Access to the resource is denied. |
404 | The sender information was not found. |