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

# List scenarios for a specific IVR

`GET /ivrs/{ivrId}/scenarios`

Retrieves all scenarios (call flow variants) attached to a specific IVR. A scenario defines a complete call flow — which menu options are available, how calls are routed, and what happens at each step. An IVR typically has one default scenario but can have multiple variants for different contexts (e.g., business hours vs. after-hours). The total count is in the `list_count` field.

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

**Monitoring impact:**
- **OFF:** Returns only scenarios from IVRs **assigned to you**.
- **ON:** Returns **all scenarios** for the specified IVR.

## Path parameters

- `ivrId` integer, required

## Response `200`

Successful operation — returns the list of scenarios.

- ScenarioList
  - `list_count` integer — The size of the list
  - `list` 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

- `204` — No scenarios found for this IVR.
- `401` — Unauthorized — invalid or missing API token, or missing `IVRs Read` permission.
- `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)