---
title: "Receive RCS conversation started event"
method: POST
path: "receive-rcs-conversation-started-events"
tags: ["channels", "rcs", "rcs-logs-and-status-reports"]
---

# Receive RCS conversation started event

`POST receive-rcs-conversation-started-events` (webhook)

Webhook notifying that a message's billing model changed from non-conversational to conversational.

## Payload

- B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsConversationStartedEvents
  - `results` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsConversationStartedEvent[], required: Collection of conversation started events.
    - `messageId` string, required: The ID that uniquely identifies the sent/received message.
    - `trafficType` 'A2P_CONVERSATION' | 'A2P_INTERACTIVE_SESSION' | 'P2A_INTERACTIVE_SESSION': Traffic type applied to the inbound or outbound RCS message. Null for non chargeable RCS messages.
    - `sender` string, required: RCS Sender for Outbound messages or MSISDN for Inbound messages.
    - `to` string, required: MSISDN for Outbound messages or RCS Sender for Inbound messages.
    - `direction` 'INBOUND' | 'OUTBOUND', required: Identifier of the message that is being updated. Possible values are: `OUTBOUND` for the RCS outbound/MT message, `INBOUND` for RCS inbound/MO message.
    - `event` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsConversationStartedEventContent, required: Conversation Started event details.
      - `type` 'CONVERSATION_STARTED' | 'CONVERSATION_STARTED', required: Conversation started event type.
    - `conversation` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62RcsConversationStartedInfo, required: Conversation details including type, ID, and time window.
      - `type` 'A2P' | 'P2A' | 'INTERACTIVE_SESSION_A2P' | 'INTERACTIVE_SESSION_P2A', required: Conversation type (Application to Person/Person to Application/Interactive session).
      - `id` string, required: Unique conversation identifier.
      - `startTime` string, date-time, required: Conversation start time.
      - `endTime` string, date-time, required: Conversation end time.
    - `platform` B839d8c276f6f1ef62ce2dce758ba402953b31f455d6d08549a7147d79f50d62Platform, required: Platform options. For more details, see [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).
      - `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).
  - `eventCount` integer, required: The number of events returned in the results array.
  - `pendingEventCount` 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)