Deutsche Bahn Timetables API

This connector calls Deutsche Bahn's official Timetables API v1 on the DB API Marketplace. It is the source of truth for what is happening at a station right now, published by DB itself (CC BY 4.0). It does not plan journeys — pair it with the Deutsche Bahn Fahrplan connector for that.

Getting a key: create a free account at https://developers.deutschebahn.com, create an application, subscribe it to the Timetables API (free plan, 60 requests/minute) and copy the application's Client ID and API Key into DB_CLIENT_ID / DB_API_KEY.

Workflow

1. dbt_search_stations resolves a name (prefix), a DS100 code or an EVA number to the station's eva (e.g. 8000107 = Freiburg(Breisgau) Hbf, 8011160 = Berlin Hbf, 8000105 = Frankfurt(Main)Hbf, 8000261 = München Hbf). Umlauts in a prefix are unreliable — search 'Munchen' or 'Muenchen' as well as 'München'.
2. dbt_get_station_board returns the planned timetable of one hour: every train with its id, category (ICE, RE, S …), number, planned arrival/departure time and platform, and the route (from / to are the stop lists as |-separated strings).
3. dbt_get_changes returns all known changes for the station (updated every 30 s): per train id, the changed time (ct), changed platform (cp), status (cs: c = cancelled, a = added) and messages. dbt_get_recent_changes is the same feed limited to the last two minutes — poll it instead of the full feed when watching a station.
4. Match the id from the plan with the id in the changes; delay in minutes = changed time − planned time.

Times are yyMMddHHmm in local German time (2609151427 = 15 Sep 2026, 14:27). The plan is sliced by hour: date is yyMMdd, hour is HH (00–23), both of the current local time in Germany.

Changes without a matching plan entry are trains that stop at the station in another hour; fetch that hour's plan if they matter.

Limits: 60 requests per minute on the free plan. Attribution: Deutsche Bahn AG, Timetables API, CC BY 4.0.