timetable

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

Changed on

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.

post/timetable/{id}/path_steps/local_track_names

Request

  • Base URL: https://demo.osrd.fr/api
  • URL: https://demo.osrd.fr/api/timetable/{id}/path_steps/local_track_names
  • Auth: none declared

Path parameters

idinteger required

A timetable ID

Request body

infra_idinteger required
operational_point_referencesobject 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

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 required

Changes

  • 1840dbbd64acRevision changes
    • breaking

      removed subschema #2: OperationalPointReferenceTrigram from the / request property oneOf list

    • info

      added subschema #2: OperationalPointReferenceDomestic to the / request property oneOf list

  • dff80f0a6343Revision changes
    • breaking

      removed subschema #2: OperationalPointReferenceDomestic from the / request property oneOf list

    • info

      added subschema #2: OperationalPointReferenceTrigram to the / request property oneOf list