Route planning for Berlin public transport (BVG) using the v6.bvg.transport.rest API. Use when the user asks for: (1) route suggestions between two addresses or stops, (2) live next-departure info for a stop, (3) arrival-time–based journey planning (arrive-by or depart-at). Supports outputting 2–3 options ranked by travel time, transfers, and walking, and returning step-by-step directions and refresh tokens for live updates.
Purpose
When to use
Core behavior
from and to into either stop IDs (preferred) or address/POI objects using GET /locations or /locations/nearby.Outputs
References
Examples (triggers)
Notes for implementers
/journeys endpoint requires base IBNR codes only (6 digits), not the full ID with :: suffixes.
de:11000:900110001::3 or de:11000:900110001900110001 (extract base 6-digit code from /stops results)/stops?query=... first, extract the 6-digit id from results, use that for /journeys.urllib.parse.quote() or equivalent. Examples:
%20ö → %C3%B6ü → %C3%BCÄ → %C3%84&, ?, # → their percent-encoded equivalentsSchönhauser Allee → Sch%C3%B6nhauser%20Allee/stops?query=... to resolve names → base IBNR.stopovers=true to build readable step lists; include entrances=true when walking-to-entrance accuracy is important.results=3 then offer the top 2–3 to the user.