---
title: "Receive Livechat inbound messages"
method: POST
path: "receive-inbound-livechat-messages"
tags: ["channels", "live-chat"]
---

# Receive Livechat inbound messages

`POST receive-inbound-livechat-messages` (webhook)

Set up the logic for processing incoming messages to enable customized two-way communication. Inbound messages will be forwarded in real-time to the specified endpoint. [Set the inbound configuration](/docs/api/platform/numbers/my-numbers/resource-management/manage-inbound-configuration) for the number by specifying your endpoint, and we will send inbound Live Chat messages to you.<br/>The name of the default format or renderer for the inbound Live Chat messages is `MO_OTT_CONTACT`, and is documented in this section.

## Payload

- 245a74e48cd7ce0a3e2f108689f6fc8d5a08a4d75c5aeb1883fc983443d62958LivechatInboundMessages
  - `results` 245a74e48cd7ce0a3e2f108689f6fc8d5a08a4d75c5aeb1883fc983443d62958LivechatInboundMessage[], required: Incoming messages.
    - `from` string, required: Live Chat registration ID of the person who sent the message.
    - `to` string, required: Live Chat widget ID which was used to send the message.
    - `integrationType` string, required: Message channel which was used to send the message. It is always LIVE_CHAT in this case.
    - `receivedAt` string, date-time, required: Date and time when Infobip received the message.
    - `messageId` string, required: The ID that uniquely identifies the received message.
    - `callbackData` string, nullable: Callback data sent through the ‛callbackData‛ field when sending a message.
    - `message` 245a74e48cd7ce0a3e2f108689f6fc8d5a08a4d75c5aeb1883fc983443d62958LiveChatInboundContent, required: Message content.
      - `type` 'TEXT' | 'IMAGE' | 'VIDEO' | 'AUDIO' | 'DOCUMENT' | 'SURVEY_RESPONSE' | 'PRE_CHAT_FORM' | 'FORM_RESPONSE' | 'BUTTON_RESPONSE' | 'BUNDLE' | 'CUSTOM_DATA'
    - `threadId` string, nullable: The ID that uniquely identifies the conversation thread.
    - `currentLanguage` string, nullable: Widget language at the time the message was sent.
    - `userData` 245a74e48cd7ce0a3e2f108689f6fc8d5a08a4d75c5aeb1883fc983443d62958LiveChatInboundUserData: Data about the user who sent the message.
      - `cdpPersonId` integer, required: Internal person ID in People.
      - `userIdentity` 245a74e48cd7ce0a3e2f108689f6fc8d5a08a4d75c5aeb1883fc983443d62958LiveChatInboundUserIdentity: Information about the user who sent the message.
        - `identityType` 'EMAIL' | 'PHONE' | 'EXTERNAL_ID', required: Unique Person identifier type.
        - `identityValue` string, required: Unique Person identifier.
        - `pushRegistrationId` string: Push registration ID.
    - `price` 245a74e48cd7ce0a3e2f108689f6fc8d5a08a4d75c5aeb1883fc983443d62958MessagePrice, required: Sent message price.
      - `pricePerMessage` number: Price per one message.
      - `currency` string: The currency in which the price is expressed.
  - `messageCount` integer, required: The number of messages returned in the results array.
  - `pendingMessageCount` integer, required: The number of messages 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)