Routing APIs
Use Radar's routing APIs to calculate travel distances between origins and destinations.
Quickstart#
First, sign up for Radar and get an API key.
Then, call one of the routing APIs below, either directly or using the SDK.
From there, use the APIs to build location features in your app or website, such as store locators, address autocomplete, or delivery tracking.
Endpoints#
Distance#
Use the distance API to calculate the travel distance and duration between an origin and a destination. You can specify one or more travel modes, including foot, bike, and car.
Use cases for this endpoint include calculating the distance and duration of a trip from point A to point B, calculating the ETA for a pickup or delivery, or calculating the walking and driving distance to a nearby store.
See the distance API reference here.
Matrix#
Use the matrix API to calculate travel distances and durations between multiple origins and destinations.
Use cases for this endpoint include calculating the walking or driving distance to multiple nearby stores (e.g., in a store locator) or optimizing routes.
See the matrix API reference here.
Route matching#
Use the route matching API to snap points collected along a route to roads that were most likely traveled on. Returns the matched path and road information.
Use cases for this endpoint include producing clean paths that can be displayed on a map, used for accurate mileage tracking and other analysis, as well as retrieving road context such as speed limits and road names along a traveled path.
See the route matching API reference here.
Directions#
Use the directions API to calculate the most efficient route between two or more locations to visit in order.
Use cases for this endpoint include calculating and displaying paths between locations on a map.
See the directions API reference here.
Route optimization#
Use the route optimization API to calculate the optimal ordering and route to visit a list of locations.
Use cases for this endpoint include determining the best sequence for several pickups or deliveries, or calculating the optimal route to visit multiple stops.
See the route optimization API reference here.
Coverage#
Radar's routing APIs incorporate both open and commercial datasets for maximum coverage at an affordable price relative to alternatives.
The following table describes data coverage for routing APIs, by country, for consumer use cases (e.g., store locators) and logistics use cases (e.g., ride sharing, delivery).
Legend#
| Icon | Description |
|---|---|
| ⬤ | Great data quality and availability |
| ◐ | Good data quality and availability |
| ◯ | Approximate data quality and availability |
Coverage#
| Distance and matrix | |
|---|---|
| 🇺🇸 US (consumer) | ⬤ |
| 🇺🇸 US (logistics) | ⬤ |
| 🇨🇦 CA (consumer) | ⬤ |
| 🇨🇦 CA (logistics) | ⬤ |
| 🇬🇧 UK (consumer) | ⬤ |
| 🇬🇧 UK (logistics) | ⬤ |
| 🌎 Other (consumer) | ◐ |
| 🌎 Other (logistics) | ◐ |
Caching#
You can cache API responses for up to 30 days. For more information, see our terms of use here.
Report an issue#
The Radar team is constantly working to improve data coverage for our geocoding, search, and routing APIs. Bad response? Unexpected error? Report it here, and our team will fix it ASAP.
Support#
Have questions? We're here to help! Contact us at radar.com/support.