London Transit (Transport for London Unified API)
Real-time data for London's entire public transport network. Powered by TfL Open Data.
Interactive Map App
An interactive map dashboard is available alongside this chat. When the app panel is open, your tool results are automatically forwarded to the map — do NOT call the app-open tool again. Just use the data tools below (get status, plan journey, search stops, etc.) and the map will update with the results rendered as map layers: tube lines as colored polylines, stations as markers, bike docks as colored circles, arrivals as floating boards.
Panel routing — start here
When the map panel is open, call the status, journey, or stop read that owns the data — do not call open app again.
| User intent | First panel read | What the map shows |
|---|
| Cold-open the map | open app | Empty map mount |
| Tube line disruptions / status | tube status or line status | Colored line polylines (line_status) |
| Plan A→B journey | journey plan | Journey polyline (journey) |
| Find stops or stations | search stops | Stop markers (stop_search) |
| Santander Cycles docks | bike points | Bike dock markers (bike_points) |
| Live board at a stop | stop arrivals or line arrivals | Arrivals overlay (arrivals) |
Stop list clicks in the widget call stop arrivals with drill-down visibility — prefer that path when the user taps a stop in the panel.
Data Model
- Lines — Transport lines across modes: tube, dlr, overground, elizabeth-line, bus, tram, cable-car, river-bus.
- StopPoints — Stations, bus stops, piers. Identified by NaPTAN IDs (e.g. 940GZZLUVIC for Victoria Tube) or ICS codes (e.g. 1000248).
- Predictions — Live arrival/departure predictions per line or stop. timeToStation is in seconds.
- Journeys — Planned routes between two points with legs, duration, and fare information.
- BikePoints — Santander Cycles docking stations with live bike/empty dock counts.
Key Patterns
- Tube line IDs are lowercase: bakerloo, central, circle, district, hammersmith-city, jubilee, metropolitan, northern, piccadilly, victoria, waterloo-city, elizabeth.
- Journey planner works best with ICS codes (the ics_id field from search results, e.g. 1000108 for Highbury & Islington). Also accepts NaPTAN IDs, Hub IDs (auto-resolved), or coordinates (lat,lon format as a string like 51.5074,-0.1278).
- StopPoint search returns matches with both id (Hub/NaPTAN) and ics_id (ICS code) fields. Use ics_id for journey planning.
- BikePoint additional properties contain NbBikes, NbEmptyDocks, NbDocks.
- Line status severity: 10=Good Service, 9=Minor Delays, 6=Severe Delays, 5=Part Closure, 4=Planned Closure, 1=Part Suspended, 0=Suspended, 20=Service Closed.
Gotchas
- Arrivals are unordered: The /Arrivals endpoint returns predictions in arbitrary order — sorted by timeToStation in tool output.
- Journey planner station IDs: Use ICS codes (e.g. 1000266 for Westminster) or NaPTAN IDs (940GZZLUWSM). Full stop names don't work — use search stops first.
- BikePoint full list is large: ~800 stations. Always search by area name.
- Mode names: Use lowercase with hyphens: tube, dlr, overground, elizabeth-line, bus, tram, cable-car, river-bus.
