---
title: "Get a specific scenario by ID"
method: GET
path: "/scenarios/{scenarioId}"
tags: ["ivrs"]
---

# Get a specific scenario by ID

`GET /scenarios/{scenarioId}`

Retrieves a specific scenario by its unique ID, regardless of which IVR it belongs to. This is a shortcut alternative to `GET /ivrs/{ivrId}/scenarios/{scenarioId}` when you already know the scenario ID but not the parent IVR ID.

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

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

## Path parameters

- `scenarioId` integer, required

## Response `200`

Successful operation

- 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 scenario ID format
- `401` — Unauthorized — invalid API key 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)