TfL Status Scraper: Live London Line Disruptions
Pricing
Pay per usage
Go to Apify Store
TfL Status Scraper: Live London Line Disruptions
Pull live London Underground, DLR, Overground and Elizabeth line status via the public Transport for London API, including disruption reasons. No login, no proxy, no browser.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Naimur Hasan
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
TfL Status Scraper
Pulls live London Underground, DLR, Overground and Elizabeth line status through the public Transport for London API, including the reason for any disruption. No login, no proxy, no browser.
Input
| Field | Type | Notes |
|---|---|---|
modes | string | Required. Comma-separated TfL modes, e.g. tube,dlr,elizabeth-line,overground,tram. |
disruptedOnly | boolean | Return only lines not reporting a good service. Default false. |
Output
One row per line: lineId, lineName, mode, statusSeverity,
statusDescription, isDisrupted, reason, statusCount, allStatuses,
checkedAt.
Notes
- TfL severity runs backwards from intuition: lower is worse.
10is Good Service,6is Severe Delays,1is Closed. Sorting ascending puts the worst disruption first, andisDisruptedis simply severity below 10. - A line can report several statuses at once — part of the route fine, part
suspended. The row summarises the worst one, keeps the count, and lists
them all in
allStatusesrather than silently reporting the first. checkedAtis stamped by this Actor, not by TfL. The API returns a live snapshot with no timestamp of its own, and a status row is not much use without knowing when it was true.- With
disruptedOnlyset, a run during good service across the whole network legitimately matches nothing and fails rather than writing an empty dataset.
