Better Places is API-based and integrates into any system through standard RESTful requests with JSON payloads. It is also available natively within the Bettermile suite.
| Option | What you get |
|---|---|
| Standalone API | Normalization, geocoding and validation, and driver-verified coordinate correction through the Places API. |
| Within the Bettermile suite | Everything in the standalone API, plus the last-meter layer (parking, entrances, handover locations). It is included when you use other suite products such as Better Route. It is not available through the standalone API. |
When connected via Data Gateway, Better Places can also be used alongside any other Bettermile solution. In that context it can act as a fallback whenever tenant-provided coordinates are faulty or missing. Even while connected to Data Gateway, Places can still return results independently through its dedicated API, just as it does as a standalone module.
Geocoding requests go to the /geocode endpoint over HTTPS, with JSON request and response bodies. See the Places API reference for all endpoints, and API Reference for a worked request and response.
The two API versions differ only by authentication method.
- Version 1 (API key): authenticate with a unique API key in the header.
- Version 2 (Bearer token): authenticate with a Bearer token. Bettermile suite users generate and manage it in the Backoffice.
Call the API with valid credentials from the Bettermile customer team. For initial trials, a sample API key lets you test with real-time data. The address input must include the country.
Request access at customer@bettermile.com.
- Supported Countries: which features are available per country.
- Geocoding Accuracy Levels: how to read the accuracy level and score in a response.