---
title: "Get a specific scenario for an IVR"
method: GET
path: "/ivrs/{ivrId}/scenarios/{scenarioId}"
tags: ["ivrs"]
---

# Get a specific scenario for an IVR

`GET /ivrs/{ivrId}/scenarios/{scenarioId}`

Retrieves detailed information about a specific scenario within an IVR. The response includes the full call flow definition — menu steps, routing rules, audio prompts, and queue configuration. Both `ivrId` and `scenarioId` must match for the scenario to be returned.

**Permission:** `IVRs Read` required.

**Monitoring impact:**
- **OFF:** Returns the scenario only if the parent IVR is **assigned to you**. Returns `404` otherwise.
- **ON:** Returns **any scenario** for any IVR in the team.

## Path parameters

- `ivrId` integer, required
- `scenarioId` integer, required

## Response `200`

Successful operation — returns the scenario details.

- Scenario
  - `scenario_id` integer — The scenario identifier
  - `ivr_id` integer — The unique identifier of the IVR. Use `GET /ivrs` to discover available IVR IDs.
  - `name` string — The name of the scenario
  - `color` string
  - `scenario_type` 'menu' | 'announce' | 'queue' | 'sms' | 'webhook' | 'input' — The type of the scenario
  - `is_default` boolean

## Other responses

- `400` — Invalid IVR or scenario identifier.
- `401` — Unauthorized — invalid or missing API token, or missing `IVRs Read` permission.
- `404` — Scenario not found, or not accessible with current monitoring level.
- `500` — Internal server error.

---

[API](https://skmtc.net/ringover/apis/ringover-public-api.md) · [All operations](https://skmtc.net/ringover/apis/ringover-public-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ringover/ringover-public-api/revisions/9da73dd2f99e/schema)