TfL London Scraper — Live Transport Data
Pricing
from $2.00 / 1,000 results
TfL London Scraper — Live Transport Data
Transport for London data — line status, live arrivals by line or stop, stop search and line stops across tube, bus, DLR, Overground and more. Free, no key needed.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
Ponderable Hydrometer
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
London transport data from the official TfL Unified API in one actor —
live arrivals, line status & disruptions, routes and stops for Tube, bus, DLR, Overground,
Elizabeth line and tram. Clean, flat, normalized JSON — no TfL $type envelope. Runs keyless.
Perfect for live departure boards, trip planners, disruption alerts, transport dashboards and datasets.
Keyless (optional BYO key)
Runs keyless at TfL's standard rate — no key required. For a higher rate limit, register a
free app key at https://api-portal.tfl.gov.uk/ and set it in the optional appKey input
(stored as a secret). It works fine without one.
Modes
| Mode | What it returns |
|---|---|
line-status | Status / disruptions for a set of modes (tube, bus, dlr, …) |
arrivals-by-line | Live arrivals for one or more lines (e.g. victoria, central, a bus route) |
arrivals-by-stop | Live arrivals at one or more stopIds (NaPTAN, e.g. 940GZZLUOXC) |
stop-search | Stops matching a query (name/place) — returns ids to use elsewhere |
line-stops | All stop points on a line |
What you get
- Arrivals — station, line, platform, direction,
towards,destinationName, vehicle id, current location,timeToStationSeconds,expectedArrival - Line status — line, mode,
statusSeverity,statusDescription, disruption reason/category and validity window - Stop search — id, name, lat/lon, modes, fare
zone, ics id - Line stops — NaPTAN id, name, stop type, lat/lon, modes, zone, lines served, WiFi flag
Example inputs
Tube status
{"mode":"line-status","modes":["tube"]}
Live arrivals on lines
{"mode":"arrivals-by-line","lines":["victoria","central"]}
Arrivals at a stop
{"mode":"arrivals-by-stop","stopIds":["940GZZLUOXC"]}
Search a stop
{"mode":"stop-search","query":"Oxford"}
Typical flow: stop-search → grab a stop id → arrivals-by-stop.
Output (one arrival)
Fields below are the real normalizer output:
{"stationName": "Oxford Circus Underground Station","naptanId": "940GZZLUOXC","lineId": "victoria","lineName": "Victoria","platformName": "Northbound - Platform 3","direction": "inbound","towards": "Walthamstow Central","destinationName": "Walthamstow Central","vehicleId": "234","currentLocation": "At Green Park","timeToStationSeconds": 120,"expectedArrival": "2026-07-12T10:15:30Z","timestamp": "2026-07-12T10:13:30Z","modeName": "tube"}
Why this actor
- All modes in one actor — Tube, bus, DLR, Overground, Elizabeth line and tram.
- Tidy schema — flat normalized rows, no TfL
$typenoise or nested envelope. - Reliable — requests retry with backoff on 429/5xx.
Pricing
Pay per result — $2.00 per 1,000 results (one result = one arrival / status / stop / match). No subscription or platform fees; runs keyless (bring a key only for higher throughput).
Related actors
- Transitland Scraper — public transit worldwide (operators, routes, stops, departures).
- Vienna Wiener Linien — live Vienna departures & stops.
Notes & limits
- Live arrival predictions and disruption status change constantly; treat each run as a snapshot.
- Independent tool sourcing the official TfL Unified API; not affiliated with or endorsed by Transport for London. Powered by TfL Open Data. You are responsible for compliant use.