The error codes and messages listed in this article might not be up-to-date. For the most updated list of error codes, visit Viber's documentation here.
Here is a list of Viber error codes, their possible causes, and suggested solutions:
| Error code | Description | Possible cause and suggested solution |
| 1 | Invalid URL | The webhook URL provided is not valid. Please check the URL format and ensure it is accessible. |
| 2 | Invalid auth token | The authentication token provided is not valid. Please verify your token and try again. |
| 3 | Bad data | There is an error in the request due to bad data, such as a missing comma or brackets. Please check your request format. |
| 4 | Missing data | Some mandatory data is missing from your request. Please review the required fields and ensure all necessary information is included. |
| 5 | Receiver not registered | The message could not be delivered because the receiver is not registered on Viber. Please check the recipient’s registration status. |
| 6 | Receiver not subscribed | The message could not be sent because the receiver is not subscribed to the account. Please ensure the recipient has subscribed. |
| 7 | Public account blocked | The message could not be delivered because the account is blocked. Please contact support to resolve the account issue. |
| 8 | Public account not found | The message could not be sent because the account associated with the provided token does not exist. Please verify the token. |
| 9 | Public account suspended | The message could not be delivered because the account is suspended. Please contact support to address the account suspension. |
| 10 | Webhook not set | The message could not be sent because no webhook is set for the account. Please configure a webhook to proceed. |
| 11 | Receiver has no suitable device | The message could not be delivered because the receiver is using a device or Viber version that doesn’t support accounts. Please check compatibility. |
| 12 | Too many requests | The message could not be sent due to a rate control breach. Please reduce the frequency of your requests and try again later. |
| 13 | API version not supported | The message could not be delivered because the minimum API version specified is not supported by all user’s devices. Please ensure that the recipient devices meet the required API version for successful delivery. |
| 14 | Incompatible with version | The message could not be delivered because the minimum API version specified is not compatible with the required message fields. Please ensure your API version aligns with the message requirements. |
| 15 | Public account not authorized | The message could not be delivered because the account is not authorized. Please check your account status and ensure you have the necessary permissions to send messages. |
| 16 | Inchat reply message not allowed | The message could not be delivered because inline messages are not allowed. Please ensure your message complies with the supported formats for this channel. |
| 17 | Public account is not inline | The account is not configured for inline messaging; please ensure inline messaging capabilities are enabled. |
| 18 | No public chat | Your message could not be sent to the public account because the bot is missing a Public Chat interface. Please verify that your bot is properly configured to access Public Chat features. |
| 19 | Cannot send broadcast | Your attempt to send a broadcast message has failed. Please check your account settings and ensure that broadcasting features are enabled for your account. |
| 20 | Broadcast not allowed | The message could not be delivered because sending broadcast messages from the bot is not allowed. Please check your message type and try again with an individual recipient. |
| 21 | Unsupported country | The message could not be delivered because it is not supported in the destination country. Please verify the destination and ensure that messages are allowed in that region. |
| 22 | Payment unsupported | The message could not be delivered because the bot does not support payment messages. Please check if payment functionality is enabled for your bot or use a different messaging option. |
| 23 | Free messages exceeded | The message could not be delivered because the bot has reached its monthly threshold for free messages. To continue sending messages, consider upgrading your plan or managing your message usage. |
| 24 | No balance | The message could not be delivered because there is no balance for the billable bot. Please add funds to your account to enable message delivery. |
| other | General error | Something went wrong. Please try again later |