

The authentication token is generated upon bot creation and can be viewed by the account’s admins in the “edit info” screen of their bot or on the Viber Admin Panel. Each API request must include an HTTP Header called X-Viber-Auth-Token containing the account’s authentication token. It is used to authenticate request in the Viber API and to prevent unauthorized persons from sending requests on behalf of a bot. The authentication token (also known as application key) is a unique and secret account identifier.

All API requests and callbacks mentioned in the diagram will be explained later in this document. The following diagram describes the flow of sending and receiving messages by the account. Our partners will be able to provide you with further details about the service, such as pricing. You can see which partners cover your geographical area in their description in the link above. If you wish to message users based on their phone number and using an API, we offer a service called Business Messages that supports this.Īpplication to use this service is done via one of our official partners.Note that users’ first message to the bot will make them subscribed, but will not result in a Subscribed callback. You can see whether a user is subscribed in the subscribed parameter of the conversation_started callback.

You can find the subscriber ID in the sender.id property of the Message callback, or the user.id property of the Subscribed callback.
#Homedale park in spring free#
#Homedale park in spring android#
#Homedale park in spring code#
Note: an active Viber account is needed to receive the login code to access the bot creation page. This account will automatically be set as the account administrator during the account creation process. An Active Viber account on a platform which supports bots (iOS/Android).In order to implement the API you will need the following:
