---
title: "Update a scenario"
method: PATCH
path: "/scenarios/{scenario_id}"
tags: ["scenarios"]
---

# Update a scenario

`PATCH /scenarios/{scenario_id}`

## Path parameters

- `scenario_id` integer, required

## Request body

- ScenarioPatchForm — This structure is used by the patch endpoint to patch a scenario
  - `description` string, nullable
  - `electrical_profile_set_id` integer, nullable
  - `infra_id` integer, nullable
  - `name` string, nullable
  - `tags` string[]

## Response `200`

The scenario was updated successfully

- ScenarioWithDetails
  - `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

---

[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)