Live

Live-ÖPNV-Abfahrten der VRR-Kernstädte + VVS Stuttgart je Station (Mentz-EFA, Tier C)

Changed on

Liefert die Echtzeit-Abfahrtstafel einer Station in einer der sechs VRR-Kernstädte (duesseldorf, dortmund, essen, duisburg, bochum, wuppertal, keylose Mentz-EFA efa.vrr.de) oder in Stuttgart (VVS, keylose Mentz-EFA www3.vvs.de): je Abfahrt Linie, Richtung, Minuten bis zur Abfahrt und Verspätung in Sekunden. Der Slug wählt die Stadt (Stadt-Scoping über das AGS5-Präfix); ein Nicht-EFA-Slug liefert 404. Der Query-Parameter station ist ein Stationsname (Default Hauptbahnhof der Stadt), intern via StopFinder auf die EFA-Global-ID aufgelöst. Der meta-Block trägt zusätzlich as_of und refresh_seconds (60). Tier C live-only: die EFA-Lizenz ist nicht klar offen (source license = unknown), reine Live-Daten, nur kurzlebig im Redis-Cache gehalten. Attribution je Verbund "Verkehrsverbund Rhein-Ruhr (VRR)" bzw. "Verkehrs- und Tarifverbund Stuttgart (VVS)". Toggle aus -> 200 source_status="disabled"; unbekannte Station oder keine Abfahrten -> 200 source_status="no_data"; toter Upstream ohne Cache -> 503 mit Hint.

get/api/v1/live/{slug}/departures

Request

Path parameters

slug'duesseldorf' | 'dortmund' | 'essen' | 'duisburg' | 'bochum' | 'wuppertal' | 'stuttgart' required

EFA-Verbund-Stadt-Slug: VRR-Kernstädte (duesseldorf, dortmund, essen, duisburg, bochum, wuppertal) oder VVS Stuttgart (stuttgart). Andere Städte liefern 404.

Query parameters

stationstring

Stationsname (Default Hauptbahnhof der Stadt).

Response

Live-Abfahrten-Envelope (CanonicalRecord oder null)

Example response

{
  "data": {
    "attribution": {
      "text": "Wikidata"
    }
  }
}

Changes

    • breaking

      added to the ///// response property oneOf list for the response status

    • warning

      added the new amtliches_werk enum value to the ///// response property for the response status

    • warning

      added the new ec_reuse enum value to the ///// response property for the response status

    • info

      added the optional property ////////// to the response with the status

    • info

      added the optional property ////////// to the response with the status

    • info

      added the optional property ////////// to the response with the status

    • info

      added the optional property ////////// to the response with the status

    • info

      added the optional property ////////// to the response with the status

    • info

      added city_base air_quality weather poi traffic_event transit_stop charging_station water_level flood_warning pollen_uv demographics energy_asset admin_boundary election_result holiday hospital road_event accident bathing_water bike_parking business_registrations charging_status_city charging_status civil_protection_warning count_station crime_stats district_heating event fire_danger fuel_price hospital_atlas indicator_series indicators insolvencies land_values mobility_point office_wait_times park_and_ride parking_onstreet parking population_density power public_tender regional_stat sharing solar solar_roofs station_arrivals station_catalog station_departures station_facilities tax_rates traffic_flow transit_departure transit_route_status transit_trip vehicle_registration weather_warning discriminator mapping keys to the ///// response property for the response status

    • info

      removed from the ///// response property oneOf list for the response status