Reverse Geocoding API

Migration Guide

Public Preview Notice

A newer version of this API is available here.
For new integration, we recommend using the latest Orbis version.
To review changes or to migrate, please find the migration guide here.

Important notes:

Where do I find the new endpoint

This TomTom Orbis Maps endpoint is supported: Reverse Geocode.

Important note: The TomTom Maps Reverse Geocode API endpoint CrossStreet Lookup is not supported.

The new Orbis Reverse Geocode API endpoint has the following prefix:

get
URL request example
https://api.tomtom.com/maps/orbis/places/reverseGeocode/...

instead of:

get
URL request example
https://api.tomtom.com/search/{versionNumber}/reverseGeocode/...

Please check the respective endpoint documentation page for details.

Changes in the parameters or responses

Important note:

  • Either the apiVersion URL parameter or the TomTom-Api-Version header needs to be present.
  • Currently supported geopolitical views: Unified, AR, MA, and IL.
  • Parameters returnRoadUse and roadUse are no longer supported. We recommend using the newer parameter returnRoadClass, which returns a market standard road classification.