InfraNode.dev
MCP InfraNode is also available as an MCP server for AI assistants like Claude and ChatGPT.

Real-time public transport API for German cities

Real-time departures at stops in major German cities through a free, keyless REST API. The data is based on DELFI and GTFS plus regional transit associations, delivered as consistent JSON with source and timestamp on every response.

What data you get

For each city the endpoint returns the next departures at a central stop: line, direction, planned and predicted departure time and delay. A parallel endpoint returns arrivals in the same shape.

  • Line
  • Direction and destination
  • Planned departure time
  • Predicted departure time
  • Delay
  • Stop

Source: DELFI, GTFS and regional transit associations. License: CC BY 4.0 or association-specific. Source, license URL and timestamp are included in every API response in the meta and attribution block.

How to fetch it

A simple GET request, no key and no sign-up:

curl https://infranode.dev/api/v1/cities/berlin/station-departures

For another city, just put the slug from the cities list into the path.

No key, no sign-up, free.

Open quickstart Endpoint reference

Covered cities

Real-time departures are available for cities with connected association or DELFI data.

Available for all 84 covered cities. The exact per-city status is on the coverage and status page, the full list of cities on the cities overview.

Straight to the largest covered cities: Berlin , Hamburg , München , Köln , Frankfurt am Main , Stuttgart , Düsseldorf , Leipzig , Dortmund , Essen .

Endpoint reference

All parameters, fields and response examples are in the API reference for this endpoint. InfraNode is also available as an MCP server for AI assistants.

Frequently asked questions

Is the public transport API free and keyless?
Yes. No key, no sign-up, free, a single GET request is enough. The rate limit is 300 requests per minute per IP.
What data does a departure contain?
Line, direction and destination, the planned and predicted departure time and the delay, at a central stop in the city.
Which sources are behind it?
DELFI and GTFS plus regional transit associations. The applicable license and attribution note are included in every API response.

More data types