Choose the right routing profile for your use case — driving supported today, cycling in progress.
Powered by OSRM and OpenStreetMap.
✅ No credit card required 🇪🇺 Hosted in the EU
Get Free API KeyAmsterdam: Centraal Station → Van Gogh Museum. Same waypoints, two profiles — see how the routes diverge.
# swap "driving" → "bike" to change the profile — same coordinates, different route
curl "https://api.simplerouting.io/osrm/route/v1/driving/4.9004,52.3791;4.8814,52.3581?overview=full&geometries=geojson" \
-H "Authorization: Bearer 988b35cc-6183-4922-bbc0-857e1a1d318d"
This is a live demo with a real API key (feel free to steal it).
A routing profile tells the engine how to traverse the road network — what roads to use, what speeds to assume, and what turn restrictions to respect. A car profile takes highways and avoids footpaths; a bike profile favors cycle lanes and penalizes fast roads. Choosing the right profile means your distances, durations, and geometries actually reflect how your users will travel.
Motorways, trunk roads, and urban streets. The car profile uses the complete OSM road network with realistic speed estimates per road class.
Every response includes duration (seconds) and distance (meters) for the full route and each leg — ready to display to drivers.
OSM turn restriction relations are respected. No routes that require illegal U-turns or ignore one-way streets.
Bicycle routing is rolling out now — favoring cycle lanes, avoiding motorways, and respecting OSM cycling infrastructure. It's currently available in select geographies, with more regions being added.
Prefers dedicated cycle lanes and bike-friendly streets. Avoids motorways and roads where cycling is restricted or dangerous.
Routes are built from OpenStreetMap's cycling tags — cycleway, bicycle=yes/no, and surface quality — so you get routes cyclists actually use.
Currently rolling out region by region. Email us with your target area — demand drives which regions we add next.
The profile is part of the URL path — swap driving for e.g. bike:
# /osrm/route/v1/{profile}/{coordinates} — swap "driving" for "bike"
curl "https://api.simplerouting.io/osrm/route/v1/driving/4.9004,52.3791;4.8814,52.3581?overview=full&geometries=geojson" \
-H "Authorization: Bearer YOUR_API_KEY"
Hitting the limits, want more countries, or need a bespoke solution? Email [email protected] — we'll figure it out.
Use driving for anything involving cars, trucks, or delivery vehicles. It respects motorway access, one-way streets, and turn restrictions from OpenStreetMap. If you're building for cyclists or pedestrians, check back — those profiles are in progress.
It's rolling out now in select geographies. If your target area isn't covered yet, email [email protected] — demand is how we prioritize which regions to add next.
Yes. The endpoint follows the standard OSRM Route Service spec: /route/v1/{profile}/{coordinates}. If you're already calling a self-hosted OSRM instance, switching is a one-line URL change plus an Authorization header.