New pricing changes will go into effect starting July 16, 2018. For more information, check out the Guide for Existing Users.

Directions API Policies

This document lists requirements that are specific to applications developed with the Directions API. Note that use of the Directions API is governed by the Google Maps Platform Terms of Service.

Displaying Directions API results

You can display Directions API results on a Google Map, or without a map. If you want to display Directions API results on a map, then these results must be displayed on a Google Map. It is prohibited to use Directions API data on a map that is not a Google map.

Displaying attribution

If your application displays data from the Directions API on a Google Map, then the Google logo will be included and may not be altered. Applications that display Directions API data on the same screen as a Google Map are not required to provide further attribution to Google.

If your application displays data from the Directions API on a page or view that does not also display a Google Map, you must show a Powered by Google logo with that data. For example, if your application displays Directions API data on one tab, and a Google Map with that data on another tab, the first tab must show the Powered by Google logo.

The Powered by Google logo is not translated into different languages or localized. It's just an image.

The following zip file contains the Powered by Google logo in the correct sizes for desktop, Android and iOS applications. You may not resize or modify these logos in any way.


If you're using the Directions API from a device where the attribution display is not practical, please contact our sales team to discuss licenses appropriate to your use case.

Attributions for third-party content

If the response from the Directions API includes transit details, your application must display the names and URLs of the transit agencies that supply the trip results. See the agencies array in the Directions API response for a specification of the relevant fields. We recommend that you place this information below any Directions API data.

Providing terms of use and privacy policy

If you develop a Directions API application, you must make available a Terms of Use and a Privacy Policy with your application which meets the guidelines outlined in section 3.2.3(a) of the Google Maps Platform Terms of Service:

  • Your Terms of Use and Privacy Policy must be publicly available.
  • You must explicitly state in your application's Terms of Use that by using your application, users are bound by Google’s Terms of Service.
  • You must notify users in your Privacy Policy that you are using the Google Maps API(s) and incorporate by reference the Google Privacy Policy.

The recommended place to make available your Terms of Use and Privacy Policy depends upon your application's platform:

Mobile applications

If developing a mobile app it is recommended that you provide a link to your Terms of Use and Privacy Policy on your application's download page in the relevant application store and in an application settings menu.

Web applications

If developing a web application it is recommended that you provide a link to your Terms of Use and Privacy Policy in the footer of your website.

Pre-Fetching, Caching, or Storage of Content

Applications using the Directions API are bound by the Google Maps Platform Terms of Service. Section 3.2.4(a) of the terms states that you must not pre-fetch, cache, index, or store any Content except under the limited conditions stated in the terms.

Since calculating directions is a time and resource intensive task, per section 3.2.4(a) of the terms, you can calculate known addresses ahead of time and store the results for up to 30 days, in a temporary cache of your own design.

Оставить отзыв о...

Текущей странице
Directions API
Directions API
Нужна помощь? Обратитесь в службу поддержки.