---
title: "Receive RCS user action event"
method: POST
path: "inbound-events-receive-inbound-rcs-events"
tags: ["channels", "rcs", "rcs-inbound-events"]
---

# Receive RCS user action event

`POST inbound-events-receive-inbound-rcs-events` (webhook)

Set up logic for processing incoming events to customize two-way communication. Inbound events are forwarded in real time to the endpoint provided during the account setup.

## Payload

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsInboundEvents
  - `results` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsInboundEvent[], required: Collection of mobile originated events.
    - `campaignReferenceId` string: ID that allows you to track, analyze, and show an aggregated overview and the performance of individual campaigns per sending channel.
    - `sender` string, required: Number which sent the message.
    - `to` string, required: Sender provided during the activation process.
    - `integrationType` string, required: Integration type.
    - `receivedAt` string, date-time, required: Date and time when Infobip received the message. Has the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ.
    - `interactionType` 'EVENT', required: The interaction type of the message that was sent. Note: this describes the message structure, not the billing category, which may differ.
    - `keyword` string: Keyword extracted from the message text.
    - `messageId` string, required: The ID that uniquely identifies the received message.
    - `pairedMessageId` string: Message ID of paired outgoing message if matched by Infobip platform.
    - `callbackData` string: Callback data sent through ‛callbackData‛ field when sending message.
    - `message` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsInboundEventContent, required: Message content.
      - `type` 'SUGGESTION', required
    - `price` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsMoEventMessagePrice, required: Price object with traffic type information.
      - `trafficType` string: Always will be null, events are not chargeable.
      - `pricePerMessage` number: Price per one message.
      - `currency` string: The currency in which the price is expressed.
    - `conversation` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsConversationInfo, required: Conversation information associated with the message.
      - `canInitiate` boolean, required: Indicates whether this message can initiate or trigger a conversation. If the message already belongs to a conversation, the value is false.
      - `id` string: Unique conversation identifier. Present when the message belongs to a conversation, null otherwise.
    - `platform` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsPlatformInfo, required: Platform information associated with the message.
      - `applicationId` string: Used when specifying an application in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
      - `entityId` string: Used when specifying an entity in outbound send requests. It is also returned in notification events. For detailed usage, refer to the [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
  - `messageCount` integer, required: The number of events returned in the results array.
  - `pendingMessageCount` integer, required: The number of events that have not been pulled in.

## Acknowledgement `200`

Your server returns this code if it accepts the callback.

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)