Introduction to the RingCentral Social Messaging APIs

Last updated: 2024-02-08Contributors
Edit this page

RingCentral Social Messaging API is in beta

The RingCentral's Social Messaging API is currently in beta. Developers should be aware of the following:

  • Their feature sets are not reflective of the full scope currently planned.
  • Backwards compatibility is not guaranteed from one release to the next during the beta period. Changes can be introduced at any time that may impact your applications with little notice.
  • During the Beta phase, each account will have monthly limits on the total number of conversations/messages sent or received via these APIs. While these conversations/messages will be free of charge during Beta, customers will need to purchase usage bundles once these APIs are officially launched for general availability.

Coming Soon!

Soon, you will have access to all the resources necessary to build an app successfully using our Social Messaging API’s. As and when we release more APIs, we will augment this section with "Getting Started" guide, API descriptions and sample code.

Developers interested in leveraging Social Messaging API’s for CX use cases can fill out the following form to sign up for accesss.

Social Messaging Developer Signup Form »

Getting Started

The RingCentral Social Messaging APIs are available to RingCentral MVP customers, ISVs building apps for RingCentral customers, and third-party developers building apps designed for their customers. The social messaging platform is made up of a number of APIs that can open up following use cases:

  • MVP user/extension (With RingCentral Business phone number) wanting to build an app to support their end customers via WhatsApp channel.
  • MVP user/extension wanting to build an app to support their end customers over multiple channels like Facebook messanger, Apple business chat, etc with OmniChannel approach.
  • ISV partners wanting to build user experience application for RingCentral customers for multi-user Shared Inbox capabilities over social channels.

Once you fill in the above access form - 1. You will be contacted by RingCentral, and we will help set up your account for this Beta access. 2. Once you have an application with necessary "social-messaging" permissions, and other setup on RingCentral side, you will receive a welcome email. 3. In that email, you will get a link to create and configure your channels that you intend to use. For example, if you want to use WhatsApp as a channel, then it's in this step you will connect to you facebook account and to WhatsApp business profile with RingCentral business phone number. 4. Once channel(s) are set up, you can start using the APIs.

We will soon provide a dedicated "Getting Started" page to detail each and every step.


Now let's walk through some initial concepts every Social Messaging Developer should know about to use our features.


A channel (or source) is referred to as a digital medium for customers to connect with enterprises. We currently support the following channels/sources through the API’s:

  • WhatsApp
  • Apple Messages for Business (AMB)
  • Google Messages for Business
  • Facebook
  • Twitter
  • Instagram
  • LinkedIn
  • YouTube
  • Google Reviews
  • Viber

To get messages from these channels you would need to have an account which can be connected, authorized and set up to start getting messages.


Content refers to messages that are sent/received on the configured channels. Content could be simple text messages, rich structured messages (e.g. carousels, rich link, etc.) or attachments in the form of files or videos. The Contents API will allow developers to both obtain and send content out on the configured source/channel.

How to configure a channel

Each channel like WhatsApp, Viber, and Facebook is a medium through which agents can communicate with customers. Once your account and application is fully set up, you will receive an email with the link to configure channels for your account. At that time you can refer to the following documentation on how to setup and configure a channel.


Social Messaging provides a Webhook API to be notified when events occur. This API is near real time and provides an alternative to polling the REST API. The purpose is to be able to trigger event-based behavior. This way you will be able to build a shared inbox with multiple users, gamification mechanism, live dashboard, synchronizing contents, etc. The current event type supported through Social Messaging webhook is as below

Resource Types

Type Description
content.imported When a new content has been imported from the source/channel (e.g. WhatsApp) to your account.

This section will be expanded further with more events, and their usage.

Content API

Get Content

This method lists contents ordered by creation date (descending) as a flat list (not nested).

RingCentral production servers are accessible on Please note that for security reasons connection is allowed using only HTTPS protocol to the default HTTPS port 443, so the port can be omitted in the URI. Be sure to set the proper authorization header for your deployment.


An Example with Facebook

There are several IDs in the GET /content API. Each has a different meaning. As an example with Facebook developers can interpret the meanings of the IDs as such:

ID Name Description
foreignId This is the ID supplied by the channel. In this case, with Facebook, the ID consists two numeric parts, delimited by an underscore (_). The first part is the post ID of the post in Facebook. The second part, after the underscore, is the reply ID from Facebook.

Intervention IDs

Intervention IDs are only used on the RingCentral platform. You will notice that if a user responds to a post/message, the intervention ID will be populated, but any post/reply from the API will not have an intervention ID.

Get Content from a Specific Channel

You can create multiple channels including, but not limited to, WhatsApp, Facebook, and LinkedIn. When you want to retrieve the contents of a single channel, you must first find the sourceId from the channel. With this sourceId, you can then get the contents just for that source.


These parameters go into the query string. There are lot more parameters supported like sortedBy, etc and will be added to this documentation soon.

Paginating Through Content

When retreiveing content, only the last 30 posts are returned by default. You can change the number of results per page as well as move from page to page using the paging object.

To change the number of results (posts) per page, set the perPage object:


Then to move to the next page, use the pageToken to move to the next page of results.


Theses parameters belong in the query string, so the entire request URL with paginating to the second page with 10 objects per page would look like this:


Create Content

This method allows you to create new content for use in discussions. It can be a reply to another piece of content or be used to initiate a discussion. If authorized, the token’s user will be used as the content author. Content will be created and pushed asynchronously to the source.

Replying to a customer's content is usually possible (unless the source/conversation is read only).

Composing a content on the contrary depend on the source itself:

  • The source may not support it (and be purely reactive like Instagram, Messenger ...)
  • Some sources (usually public account) like Twitter or Facebook page allows you to publish content without targeting specific individuals.
  • Some sources (usually non public media) require specific targeting (phone number for SMS, email address for email, customer_id ...) to be able to create a content. This is source specific and detailed under the generic parameters.

Authorization​: only users that can reply or initiate discussion (= compose) on given source. it renders also an error if in_reply_to isn’t synchronized or if in_reply_to content is not under an ​open intervention.

RingCentral production servers are accessible on Please note that for security reasons connection is allowed using only HTTPS protocol to the default HTTPS port 443, so the port can be omitted in the URI. Be sure to set the proper authorization header for your deployment.


Identities API

A single end user can use many different channels. To identify the end user, we have the identities API. This identity is then linked to each post in the form of an alphanumeric ID. To find the name of the end user, or typically known as the sender or poster, look for the authorIdentityId object and pass that into the query string using the identities API.


In the response object, you will look for the screenName field for the name of the user.

You can also get a list of all known identities by not specifying the ID: