Next-generation Omnichannel API is well underway
Over the last few months we’ve been setting the direction of our Omnichannel messaging API and our development team has started working on it. Considering transparency, we wanted to share the progress we’ve made on the API and give our clients something to look forward to, as well as helping clients prepare their systems for the next generation of our A2P messaging API.
What will our Omnichannel API do?
The term “omnichannel” has become the standard term for A2P messaging through several messaging channels in a single API. Our plan is to combine over-the-top (OTT) messaging channels, SMS, and Rich Communication Service (RCS) into a single API. A single API call will handle several channels, understanding which channel is best to reach a particular end user and handset, based on the information provided by our client.
It’s exciting to be working on our next-gen messaging platform, but there are a couple of caveats. First, Viber is the only OTT channel that has opened its API to messaging platforms like us, so far. Note, that Viber has over one-billion users globally, so it is a powerful communications channel for brands and businesses. We plan on adding other OTT channels as they become available, like WhatsApp and Facebook Messenger.
Second, RCS is still considered to be in beta with Google and mobile network operators. We’re working with Google as a beta partner, but it is ultimately up to Google and its telco partners to deem RCS ready for mass use. We’re optimistic about RCS, but it also comes down to user adoption across Android handset owners. We’ll see how it plays out and we’ll be ready to give our clients yet another channel in our Omnichannel API.
API architecture will make it even easier for clients
Our SMS API is simple to deploy and we’re keeping it that way with our Omnichannel API. Yet we’re bringing the next-gen messaging API up to more modern standards.
The API will adhere to RESTful API standards and data communication will be in JSON format. Since there are a plethora of use cases for messaging, and businesses tend to integrate messaging into other services, aligning with these standards makes it easier to integrate the API across several different services. Developers will be able to more easily connect Messente’s API to their systems and send messages based on trigger events from any other service.
Securing our API is top priority. The Omnichannel API will utilize HTTP Basic Authentication with whitelisted IP addresses, so only certain IP addresses can make API calls. All connections will be encrypted, and credentials are consistently verified.
We’ll also be making changes on the backend, like upgrading our history and statistics services. There’s quite a bit of data here, so it’s somewhat of a large project. Yet the idea behind it is to use better data services so that we can show clients more detailed statistics and information in our online dashboard. We’ve listened to our client requests and we’re making moves with their suggestions in mind.
Important to note
Ultimately, the Omnichannel API will replace our SMS API. However, clients that do not want to make any changes do not have to. Our SMS API will always be stable, it will be supported, as it will still exist. In addition, the Omnichannel API plans do not affect the verification API.
Brands and businesses that want to take advantage of several channels to connect and communicate with their customers will have the opportunity to do so with our Omnichannel API. Those that want to stick with SMS while the OTT market matures can continue using the SMS API or choose to migrate to the next-generation Omnichannel API and simply only use it for SMS –the choice is yours.
If there are any questions, send us a note to firstname.lastname@example.org, ping us in live chat on our website, or reach out to your account manager.