API reference

Liveness, uptime and a one-line feed summary.

Machine-readable list of every endpoint and its filters.

Feed header, per-file load report, and static-join statistics.

Re-read the data directory and rebuild every index.

Vehicle positions, freshest first, with route and stop names joined on.

One vehicle by id.

Predicted arrivals and departures per trip, freshest first.

One trip with every stop time update, untruncated.

Service alerts, soonest-starting first, with an isActive flag.

One alert by feed entity id.

Routes present in the feed, named, with per-route entity counts.

Everything the feed says about one route, in a single response.

Every stop id mentioned anywhere in the feed, named, with counts.

Predicted calls at a stop, earliest first, across all trips.

Alerts affecting a stop, with the same station/platform expansion.

What the forecasts are built from, and — importantly — what they cannot do.

A delay forecast for every remaining call of a trip that is in the feed.

A forecast for a trip this snapshot does not carry — one being planned, say.

How punctual the network is right now, as a distribution and a histogram.