List transport stations

  • Booking
  • Transport
  • 1 route
How do I list the transport stations available for a locale?

This scenario explains how to retrieve the transport stations available for a given locale. It also supports filtering by B2C or B2B usage and restricting the result set to stations in the same country as the currently selected station.

It fits transport search, quotation preparation, and assisted-sales journeys.

Overview

This scenario helps an application populate a departure-station selector for a specific locale.

Prerequisites

  • An accept-language header matching the target locale.
  • Optionally a tags filter to distinguish b2c and b2b usage.
  • Optionally the parameter that restricts results to the country of the currently selected station.

Expected result

The application receives an exploitable list of transport stations with identifiers, labels, types, and usage tags.

1

List the available transport stations

Mandatory

This route returns the transport stations available for the current locale. Use it to populate a departure-station selector before building a transport-related search flow.

Prerequisites

  • Send accept-language and x-api-key.
  • Optionally provide a filter query parameter to narrow the returned stations.
  • Reuse the current locale so the labels stay consistent with the rest of the journey.

Calling CURL

curl -X 'GET' \
  'https://api.clubmed.com/v1/transport_stations' \
  -H 'accept: application/json' \
  -H 'accept-language: en-US' \
  -H 'x-api-key: YOUR_API_KEY'

Example answer

[
  {
    "id": "CDG",
    "city_id": "PAR",
    "type": "AIRPORT",
    "label": "PARIS-ROISSY CDG",
    "is_main_city_station": true,
    "tags": ["INTERNATIONAL"]
  }
]

info: Reuse the returned station id in later transport-search or transport-selection steps instead of relying on the display label.

Response codes

  • OK Response (200): returns the list of transport stations available for the current locale.
  • Error (400): the filter is invalid or the request payload is malformed.
  • Error (401): non documented in Swagger.
  • Error (404): non documented in Swagger.
GET/v1/transport_stations
See more