- The URL format is {board}/{CRS|StationName}/{filterType}/{filterCRS|StationName}/{numRows}
or {board}/{CRS|StationName}/{numRows}
where only board and CRS (or a station name) are required.
+ The URL format is {board}/{CRS|StationName}/{filterType}/{filterCRS|StationName}/{numRows}
or {board}/{CRS|StationName}/{numRows}
(arrivals/departures only) where only board and CRS (or a station name) are required.
The filter type can be either to
or from
(case is not important).
A station name can be used in place of CRS codes if the name matches only one station (or matches one exactly) but case is not important. See the CRS section below for more information.
+
+ For all boards you can add an expand=true
parameter to embed all service details into the board response.
+
+ /all/{CRS|StationName}?accessToken={Your GUID token}&expand=true
+
/all/clj
/arrivals/{CRS|StationName}?accessToken={Your GUID token}
/all/{CRS|StationName}?accessToken={Your GUID token}
/next/{CRS|StationName}/{filterType}/{filterCRSs|StationNames}?accessToken={Your GUID token}
Filter stations can be a comma separated list. Filter type and number of rows are ignored.
+/fastest/{CRS|StationName}/{filterType}/{filterCRSs|StationNames}?accessToken={Your GUID token}
Filter stations can be a comma separated list. Filter type and number of rows are ignored.
The delays action performs calculations server side to easily let you know if there are problems on a particular route.