Isochrone store version and assumptions
GET/v1/isochrone/meta
GET
/v1/isochrone/meta
The active store version and its assumptions.
The frontend reads this for attribution, for the v= cache key, and to
learn which directions/modes actually exist rather than assuming.
Responses
Section titled “Responses”Successful Response
IsochroneMetaResponse
GET /v1/isochrone/meta (routers.isochrone.get_isochrone_meta)
object
assumptions
required
IsochroneAssumptions
Routing assumptions echoed from the store. Keys are store-defined; the current set is listed but extra keys are allowed. (routers.isochrone._assumptions)
directions
required
Directions
Array<string>
max_minutes
required
Max Minutes
integer
modes
required
Modes
Array<string>
version
required
Version
string
Example
{ "assumptions": { "max_trip_duration_min": 60, "transit_departure": "2026-07-15T08:00:00", "transit_percentile": 10, "transit_window_min": 60 }, "dest_set": "bb_pairs/all", "directions": [ "to", "from" ], "max_minutes": 60, "modes": [ "walk", "bike", "transit" ], "version": "rn1_tn34"}Not modified (If-None-Match matched the ETag); no body, no tokens charged
Backend temporarily unavailable (debit-unavailable, store-unavailable); may set Retry-After
Problem
RFC 9457 problem detail. Served as application/problem+json. Additional
members appear for some problem types (e.g. errors). (core.problems.problem)