---
title: "Get inbound MMS messages"
method: GET
path: "/mms/1/inbox/reports"
tags: ["channels", "mms", "receive-mms"]
---

# Get inbound MMS messages

`GET /mms/1/inbox/reports`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/mms/1/inbox/reports`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

If for some reason you are unable to receive incoming MMS at the endpoint of your choice in real time, you can use this API call to fetch messages. Each request will return a batch of received messages - only once. The following API request will return only new messages that arrived since the last API request.

## Query parameters

- `limit` integer
- `applicationId` string
- `entityId` string

## Response `200`

OK

- 62b589527d7474f21f086ddb07e8698e9fcfbbe16400c91718f1ab58d998c3f1MMSMoReportResponse
  - `results` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bMMSMoReport[]: Results.
    - `messageId` string: ID that uniquely identifies the received message.
    - `to` string: Message destination address.
    - `from` string: Sender ID that can be alphanumeric or numeric.
    - `subject` string: Subject of the received message.
    - `userAgent` string: Identifier of the device from which the message was sent.
    - `message` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bMmsMoMessagePart[]: Received message parts.
      - `origin` string
      - `contentType` string: Content type for media, for example 'image/png'.
      - `contentId` string: Unique identifier within single message.
      - `value` string
    - `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.
    - `receivedAt` string: Tells when Infobip platform received the message. It has the following format: `yyyy-MM-dd'T'HH:mm:ss.SSSZ`.
    - `mmsCount` integer: The number of sent message segments.
    - `callbackData` string: Custom callback data can be inserted during the setup phase.
    - `price` Faad2f34157fead7bc36bdf18ea6d8be6674c0ceb93de05135894a2bf0f2aa1bPrice: MMS price.
      - `pricePerMessage` number: Price per one MMS.
      - `currency` string: The currency in which the price is expressed.
    - `applicationId` string: [Application](https://www.infobip.com/docs/cpaas-x/application-and-entity-management#application) identifier the message belongs to.
    - `entityId` string: [Entity](https://www.infobip.com/docs/cpaas-x/application-and-entity-management#entity) identifier the message belongs to.

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `500`: Internal Server Error

---

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