/omio/journeys/search

POST /api/omio/journeys/search

Price: 20 credits

List departures for an Omio route (mode, origin and destination city). Provide a date (YYYY-MM-DD) to search that specific travel day, or omit it to list the nearest travel day. Returns ranked journeys with departure and arrival stations (name, country, coordinates), scheduled and estimated departure/arrival times, duration, price, operating carrier, stop count and the individual legs (connections) with transport ids and live-update status. Origin and destination are city slugs as used in Omio route URLs (resolve them via the positions search). For price trends across future dates use the prices endpoint.

How to use it

List Omio journeys for a route (mode = train/bus/flight/ferry, origin and destination city slugs). Pass date (YYYY-MM-DD) for a specific future day or omit it for the nearest travel day. Returns journeys with id, mode, departure/arrival places (name, country, coordinates), departure_at, arrival_at, estimated times, duration_minutes, price, currency, carrier_name/code, stop_count and connections (per-leg transport_id, times, live-update status). For future-date price trends use journeys/prices.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• mode string required — Travel mode (one of: "train", "bus", "flight", "ferry"; examples: "train")
• origin string required — Origin city slug as used in the Omio route URL (examples: "barcelona"; minLength: 1)
• destination string required — Destination city slug as used in the Omio route URL (examples: "madrid"; minLength: 1)
• count integer required — Max number of journeys to return (min: 1)
• date string nullable — Travel date (YYYY-MM-DD) for the outbound search; omit to list the nearest travel day (examples: "2026-09-05")

Response

• @type string (default: "OmioJourney")
• id string nullable
• mode string nullable
• departure object nullable
  • @type string (default: "OmioJourneyPlace")
  • id string nullable
  • name string nullable
  • country string nullable
  • country_code string nullable
  • latitude number nullable
  • longitude number nullable
• arrival object nullable
  • @type string (default: "OmioJourneyPlace")
  • id string nullable
  • name string nullable
  • country string nullable
  • country_code string nullable
  • latitude number nullable
  • longitude number nullable
• departure_at string nullable
• arrival_at string nullable
• estimated_departure_at string nullable
• estimated_arrival_at string nullable
• duration_minutes integer nullable
• price number nullable
• currency string nullable
• carrier_id string nullable
• carrier_name string nullable
• carrier_code string nullable
• stop_count integer nullable
• provider_id string nullable
• is_bookable boolean nullable
• booking_url string nullable
• connections array (default: [])
  • @type string (default: "OmioJourneyConnection")
  • carrier_name string nullable
  • carrier_code string nullable
  • transport_id string nullable
  • departure_id string nullable
  • arrival_id string nullable
  • mode string nullable
  • scheduled_departure_at string nullable
  • estimated_departure_at string nullable
  • scheduled_arrival_at string nullable
  • estimated_arrival_at string nullable
  • has_live_data boolean nullable
  • is_cancelled 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 journeys found for the given route 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.