---
title: "Get OMNI failover message logs"
method: GET
path: "/omni/1/logs"
tags: ["channels", "omni-failover", "send-omni-message"]
---

# Get OMNI failover message logs

`GET /omni/1/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/omni/1/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

If you need to show message logs in some GUI use this method. For message delivery status use [OMNI failover delivery reports](#programmable-communications/omni-failover/get-omni-failover-delivery-reports).

## Query parameters

- `from` string
- `to` string
- `bulkId` string[]
- `messageId` string[]
- `generalStatus` 'ACCEPTED' | 'PENDING' | 'UNDELIVERABLE' | 'DELIVERED' | 'EXPIRED' | 'REJECTED'
- `channel` 'SMS' | 'EMAIL' | 'VOICE' | 'PUSH' | 'VIBER' | 'LINE' | 'VKONTAKTE' | 'KAKAO_CHINGU' | 'KAKAO_ALIM' | 'WHATSAPP': Channel that was used for message delivering.
- `sentSince` string, date-time
- `sentUntil` string, date-time
- `limit` integer
- `mcc` string
- `mnc` string

## Response `200`

successful response

- 1bf84e5ebfeebf0839825dcb3ba7bdfe29e9008eef02919c0c668629628db19eOmniLogsResponse
  - `results` E204fb2d0d1568cbfe90b245006e95aab18e580484154f085b8348d2e991bc11OmniLog[]: Collection of logs.
    - `bulkId` string: The ID that uniquely identifies the request.
    - `messageId` string: The ID that uniquely identifies the message sent.
    - `to` string: The message destination address.
    - `from` string: Sender ID that can be alphanumeric or numeric.
    - `text` string: Text of the message that was sent.
    - `sentAt` string, date-time: Tells when the message was sent. It has the following format: `yyyy-MM-dd'T'HH:mm:ss.SSSZ`.
    - `doneAt` string, date-time: Tells when the message was finished processing by Infobip (ie. delivered to destination, delivered to destination network, etc.)
    - `messageCount` integer: The number of sent message segments.
    - `mccMnc` string: Mobile country and network codes.
    - `price` E204fb2d0d1568cbfe90b245006e95aab18e580484154f085b8348d2e991bc11Price: Sent message price.
      - `pricePerMessage` number: Price per message.
      - `currency` string: Currency.
    - `status` E204fb2d0d1568cbfe90b245006e95aab18e580484154f085b8348d2e991bc11Status: Indicates whether the message is successfully sent, not sent, delivered, not delivered, waiting for delivery or any other possible status.
      - `groupId` integer: Status group ID.
      - `groupName` string: Status group name.
      - `id` integer: Status ID.
      - `name` string: Status name.
      - `description` string: Human-readable description of the status.
      - `action` string: Action that should be taken to eliminate the error.
    - `channel` 'SMS' | 'EMAIL' | 'VOICE' | 'PUSH' | 'VIBER' | 'LINE' | 'VKONTAKTE' | 'KAKAO_CHINGU' | 'KAKAO_ALIM' | 'WHATSAPP': Channel that was used for message delivering.

## Other responses

- `400`: bad request 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)