Access status: Trackser Live is not publicly accessible. The API currently serves the Trackser app exclusively. If you have a project that would benefit from this data, get in touch.
Where to start
API Reference →
Complete endpoint reference — live data, replay, timetables, and admin. Includes example requests and response schemas.
Architecture →
How Trackser Live is built: Cloudflare Workers, Durable Objects, R2, KV, and the full data processing pipeline from TfL fetch to snapshot publish.
Integration Guide →
How to make requests, handle gzip, verify data freshness, and avoid common mistakes. Includes JS, Python, and cURL examples.
Data Sources →
How TrackerNet and the TfL Unified API work, what each provides, and how Trackser Live merges them.
Glossary →
Definitions for terms like stall detection, reformation, track circuit codes, stopping patterns, and leading car numbers.
FAQ →
Common questions about data accuracy, the stall detection algorithm, what reformation means, and how API access works.
Quick reference
Base URL:
${BASEURL}(You'll receive this when you get access)
Authentication: X-API-Key header or
?key= query parameter.
Most-used endpoints
| Endpoint | What it returns |
|---|---|
GET /live/{lineId}/map/latest.json |
All trains in the map area for a line, gzip-compressed. Primary feed for the Trackser app. |
GET /live/{lineId}/line/latest.json |
All trains on the full line including terminals, gzip-compressed. |
GET /live/{lineId}/line/latest-stats.json |
Stats only — train count, build time, source health. No trains array. |
GET /live/all/line/latest.json |
All lines combined in one response. |
GET /admin/status |
Per-line health snapshot. admin |
Line IDs
metropolitan chiltern bakerloo central circle district
hammersmith-city jubilee northern piccadilly victoria waterloo-citySupport
For technical questions, data accuracy issues, or API access enquiries: support@curiosity175.co.uk