Line status by mode
GET /Line/Mode/{modes}/Status returns real-time status and disruption information for all lines that belong to one or more modes (for example tube for London Underground). This is the Lines operation included in the API playground.
OpenAPI description (playground scope)
Download tfl-playground.json: documents this path plus GET /StopPoint/Search/{query} and GET /BikePoint only.
Resource
Each item in the response array is a line. It has identifiers, a display name, a mode, and nested lineStatuses (severity, disruption text, and related metadata). The response can include additional fields, so make sure your client accepts unknown properties.
Operation
| Method | GET |
| Path | /Line/Mode/{modes}/Status |
| Base URL | https://api.tfl.gov.uk |
Parameters
| Name | In | Required | Description |
|---|---|---|---|
modes | Path | Yes | Comma-separated mode identifiers (no spaces). Examples: tube, bus, dlr, overground, tram, national-rail. |
detail | Query | No | If true, requests richer disruption detail where the API supports it. Default false. |
Responses
| Code | Description |
|---|---|
200 | Success: JSON array of line status objects. |
400 | Bad request: unknown or malformed modes. |
404 | No data for the requested combination. |
429 | Rate limited. |
500 | Server error. |
Example requests
Single mode:
curl "https://api.tfl.gov.uk/Line/Mode/tube/Status"
Multiple modes:
curl "https://api.tfl.gov.uk/Line/Mode/tube,dlr/Status"
With detail:
curl "https://api.tfl.gov.uk/Line/Mode/tube/Status?detail=true"
Other TfL line endpoints
The full Unified API also exposes paths such as GET /Line/{ids}/Status for specific line IDs. Those are not in the playground OpenAPI file; use TfL's full documentation when you need that surface.