The Sinch Conversation API offers one single API endpoint for sending and receiving messages globally using SMS, RCS, WhatsApp, Viber Business, Facebook messenger and other popular channels.
How does Conversation API work?
The Sinch Conversation API offers one single API endpoint for sending and receiving messages across the most popular channels (SMS, RCS, WhatsApp, Viber Business, Facebook messenger and more) using one unified format. For more advanced messaging use cases, it offers conversations, contacts, switching between Bot and Human chats and much more for the advanced chatbot and conversational messaging application developer.
Different message channel (bearer) features and functions are supported through built-in transcoding. As a developer, you have the option to use either a global message template and for it to be automatically transcoded to each message channel format, or simply ignore transcoding and specify an exact layout for the channel you are interested in.
The benefits of this approach are that a developer needs to only become familiar with one Messaging API and yet have the power of conversations across all supported channels, still offering full control over channel specific features if required.
Further, it does not matter which conversation channel the customer engages over, or switch between a single callback contains all aspects of the conversation for easy integration into the Sinch portfolio of services, or any third-party platform.
With the Sinch Conversation API, you are always in control of your customer conversation whether it be over SMS, RCS, MMS, WhatsApp, Viber or Facebook Messenger. Of course, the API will support additional channels as they become available.
The Sinch Developer Documentation site contains comprehensive documentation and tutorials, which show you how you use Conversation API.
