Adding the ability to support in-app conversations just got a whole lot easier.

Note: You can license our APIs to run in your own infrastructure or pay by request/subscription on AWS Marketplace. The choice is yours.


Adding the ability to support in-app conversations just got a whole lot easier. All you need to do is build a couple of UI components leveraging our Conversation API, and you would be good to go. We support both private and group conversations.


  • Conversation API includes about 25 REST Endpoints to help serve a fair bit of your backend conversational needs. Whether you are building a new application from scratch, or adding features/enhancements to existing apps, you can rely on the API to do a lot of the backend heavy lifting.
  • Create private or group conversations, send messages, see read receipts, archive/delete/leave group conversations, and more.
  • You can integrate the API into your existing systems in almost no time. The time between you deciding to subscribe to the API, and your development team writing their first line of code to leverage the API should be 30 minutes or lesser.

Start Building

Whatever it is that you are building, you can integrate this API to leverage the power of conversations. Why spend time building when we already have it working, and all you have to do is integrate. As simple as that!


How you leverage this API depends on your needs. Build a Slack App, or a Native Mobile App, or a Web App, or Server Side Microservices. That's entirely up to you.

Subscribe to API

You can subscribe to the API by clicking "View Purchase Options". When you do this, you will be redirected to a Registration Page where you will be asked to enter some details. It should take no more than a few seconds, and once you've done that, we will send you an email with the API Key.

This email should take about 5 minutes to reach your inbox. If you do not see the email after a few minutes, check your spam folder. Do not hesitate to reach out to us if you need help.

API Features

Let's take a look at some of the features offered by the Conversation API.

  • Create a private conversation (1 on 1)
  • Create a group conversation (with 2 or more users)
  • Private conversations support Read Receipts (so you know if and when your message was read)
  • Group conversations can be archived, deleted or left
  • You can hide archived conversations
  • When a user leaves a conversation, they will not receive any more messages sent to that thread
  • User can delete a conversation they are still part of, or one that they left. In the former case, it will implicitly "leave" the user, and in both cases, the conversation would be deleted for the particular user.
  • If the conversation is left with 2 users after the last member leaves, it will become a private conversation at that point


Walkthrough of our APIs