Sorry, you need to enable JavaScript to visit this website.

Deprecation policy

The TomTom Deprecation policy is part of our standard API terms and conditions. The TomTom Deprecation policy refers to the following TomTom Maps APIs products:

  • Map Display API
  • Search API
  • Extended Search API
  • Routing API
  • Extended Routing API
  • Traffic API
  • Location History API
  • Geofencing API
  • Notifications API
  • Maps SDK for Mobile (Android and iOS)
  • Maps SDK for Web

The TomTom Deprecation policy conforms to the following rules:

  1. An element that is to be deprecated will be identified in the documentation on the TomTom Developer Portal.
  2. An element that is to be deprecated will be accompanied by the expected retirement date.
  3. The affected API/SDK documentation will describe an alternative method. If there is no migration path, it should state that there is none.
  4. Deprecated elements are maintained for at least 12 months after the announcement on the TomTom Developer Portal.
  5. After 12 months, the deprecated element will be removed from the documentation on the TomTom Developer Portal.
  6. After 12 months, the deprecated element may be removed from the affected API/SDK.
  7. TomTom will proactively communicate the deprecated elements to all users who are using the affected API/SDK at the time of the deprecation announcement.
  8. Elements previously marked as Public Preview, for example https://developer.tomtom.com/public-preview, can be changed at any time and thus are exempt from the deprecation policy.

Deprecation policy exceptions

A situation may occur where this policy becomes a serious impediment to the development of an API/SDK, or its application becomes undesirable for security reasons. In such cases, TomTom has the right to break the backward compatibility and will proactively communicate the changes to all users using the affected API/SDK.