---
title: "Get inbound SMS messages"
method: GET
path: "/sms/1/inbox/reports"
tags: ["channels", "sms", "inbound-sms"]
---

# Get inbound SMS messages

`GET /sms/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/sms/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 you are unable to receive incoming SMS to 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 API request will only return new messages that arrived since the last API request. 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>

## Query parameters

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

## Response `200`

successful response

- 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.

## Other responses

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

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification-2.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification-2/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification-2/revisions/4a6f8044a927?raw)