RCS Webhook Notifications

Webhooks allows you to receive real-time HTTP notifications of changes to specific request, incoming message etc. For example, RBM sends a notification when a user receives a message or when a template is rejected or approved.

RBM posts notifications, updates, incoming messages etc. to a Webhook at real time to ensure an automated workflow for messaging and compliance to effective business rules of Meta. Notifications are posted with JSON Payloads of pre-defined format for different type of events as RAW Body in the HTTP Request.

Each RCS Project needs to have a Webhook configured to receive notifications posted.

Important Points

  • HTTPS Host: All posts on your Webhook are sent using HTTPS, so your server must be able to receive and process HTTPS requests,
  • TLS/SSL Certificate: Webhook Host must have a valid TLS/SSL Certificate installed. Self-signed certificates are not supported.
  • Raw Body Posts: JSON Contents are posted over Webhook as Raw Body. So, Webhook must look to read Raw Body to process and take necessary action.
  • HTTP 200 Response: Any notification or message posting to Webhook URL must be acknowledged by returning HTTP 200 header in the same connection. Given below an example of responding with HTTP 200 using PHP Code:
header("HTTP/1.1 200 OK");

Type of Notifications

The following type of notifications and messages will be posted to the Webhook: