CPaaS X
Subscriptions
Event formats

Event format assignment


Event format assignment defines how inbound messages are structured and delivered to your webhook.

Each subscription automatically receives a default format, which is channel-specific to ensure consistent processing. If the default format does not meet your requirements, you can select another supported format for available channels. This allows you to control the payload structure that is sent to your webhook.


Default formats by channel

Each subscription automatically assigns a default format for handling inbound messages. These formats are channel-specific to ensure consistent processing of inbound messages.

Supported channels use the following predefined JSON-based formats to structure and process inbound messages:

ChannelFormat
Apple Messages for BusinessMO_OTT_CONTACT
Facebook MessengerMO_OTT_MSISDN
LINEMO_OTT_MSISDN
MMSMO_MMS_2
RCSMO_OTT_MSISDN
SMSMO_JSON_2
Viber Business MessagesMO_OTT_MSISDN
WhatsAppMO_OTT_CONTACT
ZaloMO_OTT_MSISDN


Selectable event formats

Early access

Use event formats to choose the payload in which you want to receive events to your webhook.

Event formats are currently available for selection for Apple Messages for Business, Facebook Messenger, MMS, SMS, Open Channel, Blocklist, and Mobile Identity events. If you need to change the format for other channels or events, contact Support.

You can choose between two options:

  • Static formats: Fixed payload schema that corresponds to a specific API version (for example, SMS API v3 or MMS API v1). All events of that type are delivered in the selected schema, regardless of how the original message was sent.
  • Adaptive subscription format: Dynamic schema where the system delivers the payload that matches the API you used to send the original message.

Select the categories below to see which formats are available for selection.



Apple Messages for Business
EventFormat nameFormat payload
Deliveryadaptive.subscription.formatPayload is picked based on the API used in your submission
delivery.apple-messages-for-business.v3.jsonExample: Receive AMB delivery reports (opens in a new tab)
delivery.apple-messages-for-business.v4.jsonExample: Receive delivery reports (opens in a new tab)
Inbound messageinbound-message.apple-messages-for-business.v1.jsonExample: Receive incoming message (opens in a new tab)
inbound-message.apple-messages-for-business.v2.jsonExample: Receive inbound messages (opens in a new tab)
Facebook Messenger
EventFormat nameFormat payload
Deliveryadaptive.subscription.formatPayload is picked based on the API used in your submission
delivery.facebook.v5.jsonExample: Receive delivery reports (opens in a new tab)
delivery.facebook.v4.jsonExample: Receive Messenger delivery reports (opens in a new tab)
Inbound messageinbound-message.facebook.v1.jsonExample: Receive incoming message (opens in a new tab)
inbound-message.facebook.v2.jsonExample: Receive inbound message (opens in a new tab)
Marketing opt-inmarketing.facebook.v1.jsonExample: Receive Messenger Opt In Marketing event (opens in a new tab)
Marketing opt-outmarketing.facebook.v1.jsonExample: Receive Messenger Opt Out Marketing event (opens in a new tab)
SMS
EventFormat nameFormat payload
Clicktracking.sms.v1.jsonExample: Receive SMS tracking notifications (opens in a new tab)
Deliveryadaptive.subscription.formatPayload is picked based on the API used in your submission
delivery.sms.v2.jsonExample: Receive delivery status report (opens in a new tab)
delivery.sms.v3.jsonExample: Receive outbound SMS message report (opens in a new tab)
delivery.sms.v4.jsonExample: Receive outbound SMS message reports (opens in a new tab)
delivery.sms.v5.jsonExample: Receive delivery reports (opens in a new tab)
Inbound messageinbound-message.sms.v1.jsonExample: Receive inbound SMS messages (opens in a new tab)
inbound-message.sms.v2.jsonExample: Receive inbound messages (opens in a new tab)
MMS
EventFormat nameFormat payload
Clicktracking.mms.v1.jsonExample: Receive MMS tracking notifications (opens in a new tab)
Deliveryadaptive.subscription.formatPayload is picked based on the API used in your submission
delivery.mms.v1.jsonExample: Receive outbound MMS message report (opens in a new tab)
delivery.mms.v3.jsonExample: Receive delivery reports (opens in a new tab)
delivery.mms.v4.jsonExample: Receive MMS delivery reports (opens in a new tab)
Inbound messageinbound-message.mms.v1.jsonExample: Receive inbound MMS messages (opens in a new tab)
inbound-message.mms.v2.jsonExample: Receive inbound messages (opens in a new tab)
Open Channel
EventFormat nameFormat payload
Deliveryevent.open-channel.v1.jsonExample: Receive Open Channel outbound Message (opens in a new tab)

How to select a different format

You can select a different format when creating or editing a subscription.

Web interface

  1. Log in (opens in a new tab) and go to Developer Tools > Subscriptions Management.
  2. Find your SMS or MMS subscription in the list.
  3. Open the three-dot menu next to the subscription name and select Edit.
  4. On the Select events screen, choose your preferred event format from the dropdown. Subscriptions - Select event format
  5. Save your subscription to apply the new settings.

API

You can configure event formats when creating (opens in a new tab) or updating (opens in a new tab) a subscription by including the format field in the events object.


Example without a format (default will be applied):

json
"events": [
  "DELIVERY"
]

Example with a selected format:

json
"events": [
  {
    "event": "DELIVERY",
    "format": "delivery.sms.v3.json"
  }
]

IMPORTANT

If the format field is not provided, the system automatically assigns the default format for that event and channel.







Need assistance

Explore Infobip Tutorials

Encountering issues

Contact our support

What's new? Check out

Release Notes

Unsure about a term? See

Glossary
Service status

Copyright @ 2006-2025 Infobip ltd.

Service Terms & ConditionsPrivacy policyTerms of use