---
title: "Retrieve list of local track names for each path step of each train schedule
that match the given operational point references list"
method: POST
path: "/timetable/{id}/path_steps/local_track_names"
tags: ["timetable"]
---

# Retrieve list of local track names for each path step of each train schedule
that match the given operational point references list

`POST /timetable/{id}/path_steps/local_track_names`

TODO: this endpoint uses a HashMap for both its
request and response, instead of the ordered list convention used by our other
endpoints. This is an intentional experiment and depending on whether
this proves easier to work with on the frontend and in editoast, we'll either
migrate the other endpoints to this format for consistency or change back the current one to the previous convention.

## Path parameters

- `id` integer, required

## Request body

- object
  - `infra_id` integer, required
  - `operational_point_references` object, required — A list of key/operational point reference pairs for which local track names should be retrieved from the timetable train schedules paths. The key is an arbitrary string chosen by the client, that will be used in the response to return the corresponding local track names set.

## Response `200`

For each requested operational point reference, returns under its client-provided key the set of local track names found in the timetable's train schedules path step inputs

- object

---

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