Migrate from the Google Geocoding API in one line
Addrova offers a Google-compatible endpoint. In most cases you change the base URL and the key, and keep the rest of your code.
Before and after
Production base URL https://api.addrova.eu is not live yet; the path below comes from the API specification.
https://maps.googleapis.com/maps/api/geocode/json
?address=10+rue+de+Rivoli+Paris
&key=GOOGLE_KEYhttps://api.addrova.eu/compat/google/maps/api/geocode/json
?address=10+rue+de+Rivoli+Paris
&key=ADDROVA_KEYOnly the request and response format is emulated. No Google data is used.
What is supported
| Element | Support |
|---|---|
| address | Forward geocoding |
| latlng | Reverse geocoding (`lat,lng`) |
| components | Only `country:XX` is honoured |
| language, region | Accepted |
| Response | status, results with formatted_address, place_id, types, partial_match, address_components and geometry (location, location_type, viewport) |
| Errors | Google-shaped: a `status` field with HTTP 200, so existing clients keep working |
| Addrova extension | An `attribution` array, ignored by existing clients; display it next to the results |
The place_id value is an Addrova identifier, not a Google place ID: do not mix the two.
Migration checklist
- Replace the base URL, the path prefix and the API key.
- Run a sample of your own addresses through both services and compare the results.
- Show the attribution next to the results, as the data licences require.
- Once validated, store the coordinates in your own database. No expiry applies.
Why storage matters
Google's terms limit how long latitude and longitude may be cached, and only place IDs can be kept indefinitely (see the Google Maps Platform terms and the Geocoding API policies). If you need to keep coordinates, check the current terms for your case. Addrova allows permanent storage.