POST /api/omio/routes/reviews
Price: 20 credits
Get traveller reviews for an Omio route (mode, origin and destination city). Returns individual reviews with the author name, star rating (with best/worst bounds), full review text and publisher. The total number of reviews behind the route's aggregate rating is returned in the X-Total-Available-Results response header. Origin and destination are city slugs as used in Omio route URLs.
Get traveller reviews for an Omio route (mode, origin and destination city slugs). Returns reviews with author_name, rating, best_rating, worst_rating, text and publisher. For the aggregate rating value and count use the routes overview endpoint.
access-token string requiredtimeout 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 reviews to return (min: 1)@type string (default: "OmioReview")author_name string nullablerating number nullablebest_rating number nullableworst_rating number nullabletext string nullablepublisher string nullable422 — 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 reviews 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.