Stadia Maps provides a full suite routing APIs with frequent (approximately weekly) data updates from OpenStreetMap and other data sources. Our APIs are extremely flexible, and power applications as diverse as route planners and turn-by-turn navigation for golf carts.
The routing endpoint is divided up into several purpose-built endpoints, which we've grouped for convenience.
The turn-by-turn directions APIs provide detailed maneuver instructions in over 25 languages, polylines for each step, ETAs, and more. In addition to standard costing models (aka profiles) for car, bicycle, etc., we give developers an immense amount of room to fine tune routes for any application.
The classic turn-by-turn directions API: specify which locations you want to visit in order, and we do the rest.
Save time and cut travel costs by finding an optimal route between multiple locations.
Turn recorded points or an encoded polyline into turn-by-turn directions.
The road information APIs help you find detailed information about roads and intersections. The endpoints have slightly different responses and there is some nuance to this. As a rule of thumb, if you have a route shape/polyline (which may be either a suggested route or recoding), you probably want the trace attributes endpoint. If however you are interested in data at a single point, prefer the nearest road endpoint.
We really tried to think of a better name for this category, but this is what we ended up with! Spatiatemporal APIs help you answer mobility questions like "what's the travel time between all these start and end points", "how far can I travel in 5 minutes via car", or "is this location reachable within 10 minutes on foot."