Navigation SDK for Android Usage and Billing

  • The Navigation SDK for Android is billed on a pay-as-you-go basis, charging per destination requested in route calculations.

  • The cost per destination varies based on monthly usage volume, with the first 1,000 destinations free of charge.

  • Usage is tracked by the "Navigation Request" SKU, and costs can be managed by setting daily quota limits in the Google Cloud Console.

  • While route generation is charged, there are no additional fees for starting guidance, traffic updates, or route deviations.

  • API calls are limited to a rate of 30,000 queries per minute and a maximum of 25 destinations per call.

 Requests to the Navigation SDK are billed to the Navigation Request SKU. You are charged for API calls you make to generate routes to a destination. API calls can include one or more destinations, also referred to as waypoints. You can calculate the cost of a call by multiplying the number of waypoints that it contains by the price for each destination requested.

There are no additional charges to start turn-by-turn guidance for a route. There are also no additional charges for route changes after a destination has already been fetched. For example, there are no charges for route changes due to traffic updates, closed roads, or deviation from the planned route.

SKU details and pricing for the Navigation SDK for Android

The following table shows the pay-as-you-go SKU details and pricing for the Navigation SDK for Android.

CategorySKU DetailsSKU Pricing
Enterprise SKU: Navigation Request Global pricing list
India pricing list

Route status and billing

You're charged for route requests that successfully reach and are processed by Google servers, even if no route can be found (such as NO_ROUTE_FOUND). You aren't charged for requests that fail due to client-side errors, network connectivity issues, or backend timeouts.

When you request a route, the SDK returns a Navigator.RouteStatus. The following table summarizes whether charges apply for each route status code:

Route status Description Billed
OK The SDK successfully calculated a route to the destination. Yes
NO_ROUTE_FOUND The SDK couldn't find a viable route to the destination. Yes
ROUTE_CANCELED The SDK canceled the route calculation in favor of a newer request. Yes
NETWORK_ERROR A network error prevented the SDK from calculating a route. No
QUOTA_CHECK_FAILED Insufficient quota prevented the SDK from calculating a route. No
LOCATION_DISABLED The user turned off GPS location, so the SDK couldn't calculate a route. No
LOCATION_UNKNOWN The SDK couldn't obtain a location fix in time to calculate a route. No
WAYPOINT_ERROR The request contained an invalid waypoint (for example, an unrecognized place ID) or exceeded the 25-waypoint limit. No
DUPLICATE_WAYPOINTS_ERROR The request contained consecutive duplicate waypoints. No
ROUTING_TIMEOUT The routing backend timed out while calculating the route. No

Adjust quota

Quota limits define the maximum number of requests allowed for a specific API or service within a given timeframe. When the number of requests in your project reaches the quota limit, your service stops responding to requests.

To modify a quota value for your API, follow these steps:

  1. In the Cloud console, navigate to Google Maps Platform > Quotas.
  2. Select the API for which you want to modify the quota.
  3. Identify the quota value that you want to change, and select it using the checkbox.
  4. Click Edit, enter a new quota value, and click Submit request.

View quota increase requests

To view all quota increase requests, including past and pending requests:

  1. In the Cloud console, navigate to Google Maps Platform > Quotas.
  2. Select the API for which you want to view the quota increase request.
  3. Click Increase Requests.

Terms of Use restrictions

For information on terms of use, see the License Restrictions section of the Google Maps Platform Terms of Service.