---
title: "Get specific OMNI failover scenario"
method: GET
path: "/omni/1/scenarios/{scenarioKey}"
tags: ["channels", "omni-failover", "configuration"]
---

# Get specific OMNI failover scenario

`GET /omni/1/scenarios/{scenarioKey}`

## 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/scenarios/{scenarioKey}`
- 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

See configuration of a specific failover scenario.

## Path parameters

- `scenarioKey` string, required

## Response `200`

successful response

- 9ac20aaa973a4193ff0ca88a25f8778624dcef15967a470e5d05a9222eb15517Scenario
  - `key` integer: Key used to uniquely identify OMNI scenario.
  - `name` string: OMNI scenario name.
  - `flow` E204fb2d0d1568cbfe90b245006e95aab18e580484154f085b8348d2e991bc11Step[]: Sender used in OMNI scenario’s step for sending message.
    - `from` string: Sender used in OMNI scenario’s step for sending message.
    - `channel` 'SMS' | 'EMAIL' | 'VOICE' | 'PUSH' | 'VIBER' | 'LINE' | 'VKONTAKTE' | 'KAKAO_CHINGU' | 'KAKAO_ALIM' | 'WHATSAPP': Channel that was used for message delivering.
  - `default` boolean: Indicates if created scenario should be set as a default.

## Other responses

- `400`: bad request responses
- `401`: Unauthorized
- `403`: Forbidden
- `404`: scenario not found
- `409`: invalid scenario
- `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)