---
title: "Get outbound SMS message logs"
method: GET
path: "/sms/3/logs"
tags: ["channels", "sms", "logs-and-status-reports"]
---

# Get outbound SMS message logs

`GET /sms/3/logs`

## 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/3/logs`
- 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

Use this method to obtain the logs associated with outbound messages. The available logs are limited to those generated in the last 48 hours, and you can retrieve a maximum of only 1000 logs per call. See [message delivery reports](#channels/sms/get-outbound-sms-message-delivery-reports-v3) if your use case is to verify message delivery.

## Query parameters

- `mcc` string: Mobile Country Code.
- `mnc` string: Mobile Network Code. Mobile Country Code is required if this property is used.
- `sender` string
- `destination` string
- `bulkId` string[]
- `messageId` string[]
- `generalStatus` 'ACCEPTED' | 'PENDING' | 'UNDELIVERABLE' | 'DELIVERED' | 'EXPIRED' | 'REJECTED': Status group name that describes which category the status code belongs to, i.e., [PENDING](https://www.infobip.com/docs/essentials/response-status-and-error-codes#pending-general-status-codes), [UNDELIVERABLE](https://www.infobip.com/docs/essentials/response-status-and-error-codes#undeliverable-general-status-codes), [DELIVERED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#delivered-general-status-codes), [EXPIRED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#expired-general-status-codes), [REJECTED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#rejected-general-status-codes).
- `sentSince` string, date-time
- `sentUntil` string, date-time: The logs will only include messages sent before this date. Use it alongside sentSince to specify a time range for the logs, but only up to the maximum limit of 1000 logs per call. Has the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ.
- `limit` integer
- `entityId` string
- `applicationId` string
- `campaignReferenceId` string[]
- `useCursor` boolean
- `cursor` string

## Response `200`

OK

- 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630LogResponseSmsLogSmsMessageContent
  - `results` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630SmsLogSmsMessageContent[]: An array of message log results, one object per each message log entry.
    - `sender` string: The sender ID which can be alphanumeric or numeric.
    - `destination` string: Message destination address.
    - `bulkId` string: Unique ID assigned to the request if messaging multiple recipients or sending multiple messages via a single API request.
    - `messageId` string: Unique message ID for which a log is requested.
    - `sentAt` string, date-time: Date and time when the message was sent. Has the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ.
    - `doneAt` string, date-time: Date and time when the Infobip services finished processing the message (i.e., delivered to the destination, network, etc.). Has the following format: yyyy-MM-dd'T'HH:mm:ss.SSSZ.
    - `messageCount` integer: The number of messages content was split to.
    - `price` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630MessagePrice: Sent message price.
      - `pricePerMessage` number: Price per one message.
      - `currency` string: The currency in which the price is expressed.
    - `status` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630MessageStatus: Indicates the [status](https://www.infobip.com/docs/essentials/response-status-and-error-codes#api-status-codes) of the message and how to recover from an error should there be any.
      - `groupId` integer: Status group ID.
      - `groupName` 'ACCEPTED' | 'PENDING' | 'UNDELIVERABLE' | 'DELIVERED' | 'EXPIRED' | 'REJECTED': Status group name that describes which category the status code belongs to, i.e., [PENDING](https://www.infobip.com/docs/essentials/response-status-and-error-codes#pending-general-status-codes), [UNDELIVERABLE](https://www.infobip.com/docs/essentials/response-status-and-error-codes#undeliverable-general-status-codes), [DELIVERED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#delivered-general-status-codes), [EXPIRED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#expired-general-status-codes), [REJECTED](https://www.infobip.com/docs/essentials/response-status-and-error-codes#rejected-general-status-codes).
      - `id` integer: Status code ID.
      - `name` string: [Status code](https://www.infobip.com/docs/essentials/response-status-and-error-codes#api-status-codes) name.
      - `description` string: Human-readable description of the status.
      - `action` string: Action to take to recover from the error.
    - `error` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630MessageError: Indicates whether an [error](https://www.infobip.com/docs/essentials/response-status-and-error-codes#error-codes) occurred during the query execution.
      - `groupId` integer: Error group ID.
      - `groupName` 'OK' | 'HANDSET_ERRORS' | 'USER_ERRORS' | 'OPERATOR_ERRORS': Error group name that describes which category the error code belongs to.
      - `id` integer: Error ID.
      - `name` string: [Error name](https://www.infobip.com/docs/essentials/response-status-and-error-codes#error-codes).
      - `description` string: Human-readable description of the error.
      - `permanent` boolean: Indicates whether the error is recoverable or not.
    - `platform` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630Platform: Platform options. For more details, see [documentation](https://www.infobip.com/docs/cpaas-x/application-and-entity-management).
      - `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).
    - `content` union: Message content.
      - object
        - `text` string, required: Content of the message being sent.
        - `transliteration` 'NONE' | 'TURKISH' | 'GREEK' | 'CYRILLIC' | 'SERBIAN_CYRILLIC' | 'CENTRAL_EUROPEAN' | 'BALTIC' | 'NON_UNICODE' | 'PORTUGUESE' | 'COLOMBIAN' | 'BULGARIAN_CYRILLIC' | 'ALL': The transliteration of your sent message from one script to another. [Transliteration](https://www.infobip.com/docs/sms/language#sms-transliteration) is used to replace characters which are not recognized as part of your defaulted alphabet. `ALL` means that the transliteration process will recognize all supported languages.
        - `language` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630SmsLanguage: Sets the language parameters for the message being sent.
          - `languageCode` 'NONE' | 'TR' | 'ES' | 'PT' | 'AUTODETECT': [Language code](https://www.infobip.com/docs/sms/language#national-language-identifier) for the correct character set. `AUTODETECT` lets the platform select the character set based on message content only for supported languages.
          - `singleShift` boolean: Uses a single shift table which enhances only the extension table of the GSM default alphabet. Allows you to selectively improve character support without altering the entire message.
          - `lockingShift` boolean: Uses a locking shift table which allows you to represent characters beyond the standard GSM default alphabet. This flexibility enables better language support.
      - object
        - `dataCoding` integer: Binary content data coding. The default value is (`0`) for GSM7. Example: (`8`) for Unicode data.
        - `esmClass` integer: “Esm_class” parameter. Indicate special message attributes associated with the SMS. Default value is (`0`).
        - `hex` string, required: Hexadecimal string. This is the representation of your binary data. Two hex digits represent one byte. They should be separated by the space character.
    - `campaignReferenceId` string: ID of a campaign that was sent in the message.
    - `mccMnc` string: Mobile country and network codes.
  - `cursor` 20085a4036d67f66ebf204560d55d58a7c131c15d42c8ed9442747c488e08630CursorPageInfo: Cursor information.
    - `limit` integer: Requested limit.
    - `nextCursor` string: The `cursor` value you will use in your next request to fetch the subsequent set of results.

## Other responses

- `401`: Unauthorized
- `403`: Forbidden
- `429`: Too Many Requests
- `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)