Skip to main content

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Routing API

[1.1.0] - 2026-10-19​

Added​

  • pt object on public transport routes: fare, frequency, respects_all_conditions and buy_ticket_urls, each returned only when the value is known

Fixed​

  • Documented that an explicit departure_time with transport: "public" is local time at the departure stop, as in the SDK

[1.0.3] - 2026-10-05​

Fixed​

  • sections documented as an object with one array per requested section type (schema and car route example), not as an array
  • Instruction distance and time are measured from the previous instruction (0 for the first), not from the route start
  • instructions are returned only for details: "full"; points are not returned for details: "timedistance"
  • Documented the segments array, the battery fields beginSoC, endSoC and chargeTime, and the error object returned for invalid requests (HTTP 400, with its own schema) and when no route can be computed (HTTP 200)
  • Battery state of charge is also returned for e-bike routes, as a fraction of the battery capacity
  • Route types accepted per transport mode; public transport accepts only fastest and no track
  • alternatives: default 0, at most 9 for public transport and 2 otherwise, and only for routes with exactly 2 waypoints
  • waypoints: at least 2, or 1 with roundtrip; optional when a track is given, and not allowed with accurate: false; track.waypoint_index range and default
  • turnaround default for public transport and emergency mode; EV routing requires charger_ports and range
  • vehicle: speed per transport mode and greater than 0; mass is the e-bike mass for bike transport; negative dimensions are rejected; fuel defaults to diesel
  • track.restrictions default follows accurate; pt defaults: minimum_transfer_time 1 min, maximum_transfer_time 300 min, maximum_walk_distance 5000 m
  • locale takes ISO 639-1 and ISO 639-2 codes with an optional region and falls back to the closest available language; departure_time is a Unix timestamp in seconds; fitness outside 0–1 is rejected; top-level profile documented in the guide and the schema
  • Path alt is present on road-network points, not on inaccurate-track or public transport shapes; terrain is not returned for public transport or details: "timedistance"
  • roundabout_exit is on the instruction entering a roundabout; climb slope is in percent and grade is the climb category
  • Removed alternatives from the multi-waypoint examples and the outdated departure_time from the public transport example

[1.0.2] - 2026-10-03​

Fixed​

  • Response documented as a single JSON object with info and routes, not as an array; examples updated accordingly
  • points coordinates documented under coordinates (with type "LineString"), not coords
  • Road class sections documented as road_class, not road_info
  • bbox order documented as [west, south, east, north]
  • locale documented as an ISO 639-1 language code
  • Country section iso documented as an ISO 3166-1 alpha-3 code

[1.0.1] - 2025-11-27​

Fixed​

  • Restructured oneOf in track and points schemas for proper documentation rendering

[1.0.0] - 2025-11-14​

Initial release

Isochrones API

[1.0.3] - 2026-10-05​

Fixed​

  • distance and time of an isochrone both carry its requested range value
  • Documented the error object returned for invalid requests (HTTP 400, with its own schema) and when no isochrone can be computed (HTTP 200)
  • Route types accepted per transport mode; ranges: at most 10 values, each greater than 0
  • Isochrone coordinates carry no altitude
  • locale uses the same codes as the Routing API; the isochrone result contains no translated text
  • vehicle: speed per transport mode and greater than 0; mass is the e-bike mass for bike transport; negative dimensions are rejected
  • hillskip is a number in 0–1; fitness outside 0–1 is rejected; top-level profile and the truck transport mode documented
  • Example requests: removed a bike profile from the car example and set a realistic e-bike mass

[1.0.2] - 2026-10-03​

Fixed​

  • Response documented as a single JSON object with info and routes, not as an array; example updated accordingly
  • points coordinates documented under coordinates, not coords
  • bbox order documented as [west, south, east, north]
  • locale documented as an ISO 639-1 language code

[1.0.1] - 2025-11-27​

Fixed​

  • Restructured oneOf in points response schema for proper documentation rendering

[1.0.0] - 2025-11-14​

Initial release

Last updated on