Deutsche Bahn Timetables
Mock the Deutsche Bahn Timetables API to test trip-planning clients, departure boards, and station-info tools without registering for DB API credentials.
[01]
About
Mock all four endpoints of the Deutsche Bahn Timetables API: fetch planned departures, real-time changes, station info, and the recent-changes feed. Mock responses follow the same XML shape the live DB API returns. Useful for trip-planning prototypes, travel apps, or any client that consumes DB station timetables.
Endpoints
4 across 1 resource group
Methods
GET 4 none deprecated
OpenAPI
3.0.1 spec version 1.0.213
Source spec
27 KB · YAML
[02]
Endpoints
| GET |
/fchg/{evaNo}
|
Returns all known changes for a station Returns a Timetable object (see Timetable) that contains all known changes for the station given by evaNo. The data includes all known changes from now on until ndefinitely into the future. Once changes become obsolete (because their trip departs from the station) they are removed from this resource. Changes may include messages. On event level, they usually contain one or more of the 'changed' attributes ct, cp, cs or cpth. Changes may also include 'planned' attributes if there is no associated planned data for the change (e.g. an unplanned stop or trip). Full changes are updated every 30s and should be cached for that period by web caches. Mocked via Mockzilla.
|
| GET |
/plan/{evaNo}/{date}/{hour}
|
Returns planned data for the specified station within an hourly time slice Returns a Timetable object (see Timetable) that contains planned data for the specified station (evaNo) within the hourly time slice given by date (format YYMMDD) and hour (format HH). The data includes stops for all trips that arrive or depart within that slice. There is a small overlap between slices since some trips arrive in one slice and depart in another. Planned data does never contain messages. On event level, planned data contains the 'plannned' attributes pt, pp, ps and ppth while the 'changed' attributes ct, cp, cs and cpth are absent. Planned data is generated many hours in advance and is static, i.e. it does never change. It should be cached by web caches.public interface allows access to information about a station.
|
| GET |
/rchg/{evaNo}
|
Returns all recent changes for a station Returns a Timetable object (see Timetable) that contains all recent changes for the station given by evaNo. Recent changes are always a subset of the full changes. They may equal full changes but are typically much smaller. Data includes only those changes that became known within the last 2 minutes. A client that updates its state in intervals of less than 2 minutes should load full changes initially and then proceed to periodically load only the recent changes in order to save bandwidth. Recent changes are updated every 30s as well and should be cached for that period by web caches.
|
| GET |
/station/{pattern}
|
Returns information about stations matching the given pattern This public interface allows access to information about a station.
|