---
title: "Return a list of scenarios"
method: GET
path: "/scenarios"
tags: ["scenarios"]
---

# Return a list of scenarios

`GET /scenarios`

## Query parameters

- `study_id` integer, required
- `page` integer
- `page_size` integer
- `ordering` 'NameAsc' | 'NameDesc' | 'CreationDateAsc' | 'CreationDateDesc' | 'LastModifiedDesc' | 'LastModifiedAsc'

## Response `200`

A paginated list of scenarios

- object — Statistics about a paginated editoast response Provides the pagination settings issued in the request alongside a few convenience fields useful to navigate the paginated results. # Expected usage This struct is meant to be used and flattened in the response of a paginated query. ``` #[derive(Serialize, ToSchema)] struct MyPaginatedResponse { #[schema(flatten)] pagination: PaginationStats, result: Vec<MyData>, // any other field that makes sense in a paginated response } ``` We named the data field `result` to cope with the old pagination schema which enforced this name. For new paginated responses, the field name is up to your imagination :)
  - `count` integer, required — The total number of items
  - `current` integer, required — The current page number
  - `next` integer, nullable, required — The next page number, if any
  - `page_count` integer, required — The total number of pages
  - `page_size` integer, required — The number of items per page
  - `previous` integer, nullable, required — The previous page number, if any
  - `results` ScenarioWithDetails[], required
    - `creation_date` string, date-time, required
    - `description` string, required
    - `electrical_profile_set_id` integer
    - `id` integer, required
    - `infra_id` integer, required
    - `last_modification` string, date-time, required
    - `name` string, required
    - `study_id` integer, required
    - `tags` string[], required
    - `timetable_id` integer, required
    - `infra_name` string, required
    - `timetable_type` 'CALENDAR' | 'HOURLY', required
    - `train_schedules_count` integer, required

## Other responses

- `404` — Project or study doesn't exist

---

[API](https://skmtc.net/openrailassociation/apis/osrd-editoast.md) · [All operations](https://skmtc.net/openrailassociation/apis/osrd-editoast/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/openrailassociation/osrd-editoast/versions/1840dbbd64ac/schema)