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

# Receive inbound MMS messages

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

If you want to receive MMS messages from your subscribers we can have them delivered to you in real time. [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 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 MMS messages is documented in this section. It is referred to as `MO_MMS_2` when configuring inbound settings via HTTP forward actions, and as `inbound-message.mms.v1.json` when configuring via Subscriptions. Both names refer to the same payload.

## Payload

- 62b589527d7474f21f086ddb07e8698e9fcfbbe16400c91718f1ab58d998c3f1MMSMoWebhookRequest
  - `results` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bMMSMoWebhookResult[]
    - `entityId` string: The ID of the entity, if application and entity management is used.
    - `applicationId` string: The ID of the application, if application and entity management is used.
    - `from` string: Sender ID that can be alphanumeric or numeric.
    - `to` string: Message destination address.
    - `receivedAt` string, date-time: Date and time when Infobip received the message.
    - `messageId` string: ID that uniquely identifies the received message.
    - `pairedMessageId` string: Message ID of paired outgoing message if matched by Infobip platform.
    - `callbackData` string: Custom callback data can be inserted during the setup phase.
    - `userAgent` string: Identifier of the device from which the message was sent.
    - `message` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bMmsMoMessageSegment[]: All parts of the received message.
      - union: All parts of the received message.
        - object
          - `contentType` string: Content type of the message segment `text/plain`.
          - `value` string: Message text.
        - object
          - `contentType` string: Content type of the message segment `image/jpeg`.
          - `url` string: URL from which content can be downloaded.
    - `group` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bMoDestination[]: Recipients of group MMS.
      - union: Recipients of group MMS.
        - object
          - `to` string: Message destination address.
        - object
          - `cc` string: Message destination address, carbon copy.
    - `price` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bPrice: MMS price.
      - `pricePerMessage` number: Price per one MMS.
      - `currency` string: The currency in which the price is expressed.
  - `messageCount` integer: Number of returned messages in this request.
  - `pendingMessageCount` integer: Number of remaining new messages on Infobip servers ready to be returned in the next request.

## 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)