---
title: "Receive inbound SMS messages"
method: POST
path: "receive-inbound-sms-messages"
tags: ["channels", "sms", "inbound-sms"]
---

# Receive inbound SMS messages

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

Receive SMS messages from your subscribers and have them delivered to you in real-time. To use this method, you’d need to:<ol><li><a href="https://www.infobip.com/docs/api/platform/numbers/phone-numbers/purchase-number">Buy a number</a> capable of receiving SMS traffic.</li><li>Specify a forwarding endpoint for the number and optionally configure other <a href="https://www.infobip.com/docs/api/platform/numbers/my-numbers/resource-management/manage-inbound-configuration">inbound settings</a>.</li></ol>We will then send inbound messages to you as soon as they are delivered to us by a mobile network operator.<br>The default format or renderer for the inbound SMS messages is documented in this section. It is referred to as `MO_JSON_2` when configuring inbound settings via HTTP forward actions, and as `inbound-message.sms.v1.json` when configuring via Subscriptions. Both names refer to the same payload.

## Payload

- Cd5e571e477c0b81ca50ad592cf9f67cc32feded2012ec26d7fae09c0c2d5108SmsMoReportResponse
  - `results` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630SmsMoReport[]: An array of result objects.
    - `applicationId` string: Application id linked to the message. For more details, see our [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
    - `messageId` string: Unique message ID.
    - `from` string: Sender ID that can be alphanumeric or numeric.
    - `to` string: The destination address of the message.
    - `text` string: Full content of the message.
    - `cleanText` string: Content of the message without a keyword (if a keyword was sent).
    - `keyword` string: Keyword extracted from the message content.
    - `receivedAt` string, date-time: Indicates when the Infobip platform received the message. Has the following format: `yyyy-MM-dd'T'HH:mm:ss.SSSZ`.
    - `smsCount` integer: The number of parts the message content was split into.
    - `price` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630MoPrice: A price object showing currency and a price per each message.
      - `pricePerMessage` number, double: Price per one SMS.
      - `currency` string: The currency in which the price is expressed.
    - `callbackData` string: Custom callback data sent over the notifyUrl.
    - `entityId` string: Entity id linked to the message. For more details, see our [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
    - `campaignReferenceId` string: ID that allows you to track, analyze, and show an aggregated overview and the performance of individual campaigns per sending channel.
  - `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)