Routing · Route API · In development
Route API: Valhalla-compatible /route
/route takes Valhalla’s request body and returns Valhalla’s trip object, so a client written for Valhalla needs a new base URL. On Berlin the responses were byte-identical to Valhalla 3.9.1 on 100/100 auto, 30/30 pedestrian, 30/30 bicycle routes, on tiles geolith built.
Status · In development
In development, not deployed: there is no routing endpoint to call yet, on geolith.app or api.geolith.app, and no routing plan, price or key.
Berlin · same data, same requests
Against the reference engine
Measured on geolith/routing main. Only sets that were run are shown; no speed or cost is measured.
| Set | Requests | Byte-identical |
|---|---|---|
| Auto | 100 | 100/100 |
| Pedestrian | 30 | 30/30 |
| Bicycle | 30 | 30/30 |
Detail
Request
A POST to /route with a JSON body, as Valhalla documents it. ROUTER_HOST stands for a router you run; there is no hosted one.
Detail
Response
A Valhalla trip object: length and time in total and per leg, the shape as an encoded polyline with precision 6, and maneuvers with English instructions. Spoken (verbal_*) instructions are in progress.
Detail
Errors
Errors use Valhalla’s error body (error_code, error, status_code, status) with the HTTP status of the same number.
Questions
Route API: questions
No. Routing is not deployed, so there is no key, plan or price for it. A geolith API key today covers geocoding and vector tiles (India tile set today; planet tiles in development) only.
Routing · In development
More on routing
Sources
- Routing API (planned), geolith docs (read 2026-11-08)
- Valhalla turn-by-turn API reference, Valhalla (open source, MIT) (read 2026-11-08)
Routing · In development
Follow routing progress.
Read how the router works today and what has to pass before it is deployed.