/omio/stations

POST /api/omio/stations

Price: 10 credits

Get details for an Omio station by its station page path. Returns the station id, name, type, address, coordinates, distance to the city centre, IATA code (airports), phone numbers, public transport connections, ticket office opening hours and a full facilities breakdown (wifi, ATMs, parking, taxi, toilets, accessibility, dining, luggage storage, shops, hotels, lounges, ticket and information desks, bike and car services and more) with descriptive details where available. The station path is the link returned by the route and journey endpoints, e.g. train-stations/spain/barcelona/barcelona-sants.

How to use it

Get an Omio station by its station page path (the station link from route/journey endpoints, e.g. train-stations/spain/barcelona/barcelona-sants). Returns id, name, type, address, latitude/longitude, distance_to_center_km, iata_code, phones, public_transport_connections, ticket_office_hours and a facilities object with has_* flags and detail lists (wifi, dining, hotel, atm, accessibility, luggage_storage and more).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• station string required — Station page path as returned in a station's link, e.g. train-stations/spain/barcelona/barcelona-sants (examples: "train-stations/spain/barcelona/barcelona-sants"; minLength: 1)

Response

• @type string (default: "OmioStation")
• id string nullable
• name string nullable
• type string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• distance_to_center_km integer nullable
• iata_code string nullable
• phones array (default: [])
• public_transport_connections array (default: [])
• ticket_office_hours array (default: [])
• link string nullable
• facilities object nullable
  • @type string (default: "OmioStationFacilities")
  • has_wifi boolean nullable
  • wifi array (default: [])
  • has_atm boolean nullable
  • atm array (default: [])
  • has_parking boolean nullable
  • parking array (default: [])
  • has_taxi boolean nullable
  • has_toilet boolean nullable
  • has_accessibility boolean nullable
  • accessibility array (default: [])
  • has_dining boolean nullable
  • dining array (default: [])
  • has_luggage_storage boolean nullable
  • luggage_storage array (default: [])
  • has_shopping boolean nullable
  • shopping array (default: [])
  • has_hotel boolean nullable
  • hotel array (default: [])
  • has_lounge boolean nullable
  • has_ticket_office boolean nullable
  • ticket_office array (default: [])
  • has_information_desk boolean nullable
  • information_desk array (default: [])
  • has_waiting_room boolean nullable
  • has_lost_and_found_office boolean nullable
  • has_businesses boolean nullable
  • businesses array (default: [])
  • has_shower boolean nullable
  • has_bike_parking boolean nullable
  • has_bike_rental boolean nullable
  • has_car_rental boolean nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No station found for the given station page path Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.