---
title: "Receive LINE Official Account inbound messages and events"
method: POST
path: "receive-inbound-line-oa-messages"
tags: ["channels", "line-oa", "line-oa-inbound-messages"]
---

# Receive LINE Official Account inbound messages and events

`POST receive-inbound-line-oa-messages` (webhook)

Set up logic for processing inbound messages and events (for example TEXT, IMAGE, FOLLOW, UNFOLLOW, POSTBACK). Payloads are forwarded in real time to the endpoint provided during account setup. Send the `replyToken` from the inbound payload back in your next message to have it delivered free of charge (reply tokens are single-use and valid for one minute).

## Payload

- 53932f53b54839fd583eae39fe878805e79c364296f164379eb97a5f2c4b6c59LineOaInboundMessages
  - `results` 53932f53b54839fd583eae39fe878805e79c364296f164379eb97a5f2c4b6c59InboundMessageLineOaInboundContent[]: Collection of mobile originated messages.
    - `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).
    - `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.
    - `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` 53932f53b54839fd583eae39fe878805e79c364296f164379eb97a5f2c4b6c59LineOaInboundContent, required: Message content.
      - `type` 'TEXT' | 'IMAGE' | 'VIDEO' | 'AUDIO' | 'FILE' | 'LOCATION' | 'STICKER' | 'FOLLOW' | 'UNFOLLOW' | 'JOIN' | 'LEAVE' | 'MEMBER_JOIN' | 'MEMBER_LEAVE' | 'POSTBACK' | 'BEACON' | 'ACCOUNT_LINK' | 'THINGS' | 'UNSEND', required
    - `price` 53932f53b54839fd583eae39fe878805e79c364296f164379eb97a5f2c4b6c59MessagePrice, required: Sent message price.
      - `pricePerMessage` number: Price per one message.
      - `currency` string: The currency in which the price is expressed.
  - `messageCount` integer: The number of messages returned in the results array.
  - `pendingMessageCount` integer: 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)