Trainline: Search Journeys
Trainline via Parse · travel
Search for train journeys between two locations. Returns up to 8 available journeys with departure/arrival times, duration, distance, and CO2 emissions. Use station URNs from search_locations as origin and destination. Results are sorted by departure time. Each journey includes leg count for identifying direct vs connecting services. API for searching train stations and journeys on Trainline.com. Search for station locations by name to get URNs, then use those URNs to search for available train journeys between stations. Fulfilled by Parse from trainline.eu.
- maps-geo
- other
- parse
- platform-key
- trainline
- trainline-eu
- travel
Price and execution
- Price
- $0.10 USD credits / call
- Trust tier
- Verified
- Execution
- Managed call
- Capability group
- travel
Interface snapshot
- Protocol
- HTTP operation
- Operation
- POST /scraper/447b13bc-e3c7-4dca-a183-dbdaa6edee8a/search_journeys
- Interface artifact
- sha256:6f4e9f84b211e103c53fe24d1e3aac924620a56e041976c9b7d187c224a1c71d
- Manifest digest
- sha256:532fbd3a367bf3ff4259e195aea0e97d495a9c5e363219d829f3a3451c2552f7
Request fields
- origin (string, required): Origin station URN from search_locations (e.g. 'urn:trainline:generic:loc:182gb').
- destination (string, required): Destination station URN from search_locations (e.g. 'urn:trainline:generic:loc:115gb').
- departure_date (string): Departure date and optional time in ISO format. Accepts YYYY-MM-DD (time defaults to 09:00) or YYYY-MM-DDTHH:MM:SS. If omitted, defaults to tomorrow at 09:00 UTC.
Example queries
- {"origin":"urn:trainline:generic:loc:182gb","destination":"urn:trainline:generic:loc:115gb","departure_date":"2026-06-18"}