Directions API Usage and Billing

Reminder: To use the Directions API, you must enable billing on each of your projects and include an API key or OAuth token with all API or SDK requests.

Directions API requests generate calls to one of two SKUs depending on the type of request: Essentials or Pro. Click the info info icon to see the table of contents for this page.

Billing and pricing for the Directions API

For information about how Google calculates your billing and pricing, see Google Maps Platform pricing list or Google Maps Platform pricing list - India.

SKU: Directions

This SKU bills for a request to the Directions API unless the request triggers the Directions Advanced billing SKU, in which case it is billed under that SKU.

	Category	Essentials
	Billable event	Query
	Triggers	This SKU bills for a request to the following services, unless the request triggers a higher-rated SKU: Maps JavaScript API Directions Service Directions API (Legacy)
	Pricing	Main pricing table India pricing table

SKU: Directions Advanced

This SKU bills for a request to the Maps JavaScript API’s Directions Service or the Directions API (Legacy) that uses traffic information, more than 10 waypoints, waypoint optimization, or location modifiers.

	Category	Pro
	Billable event	Query
	Triggers	This SKU bills for a Maps JavaScript API’s Directions Service or a Directions API (Legacy) request that returns one or more of the following information: Traffic information.: When you use all of the following request options so that the response returns the duration_in_traffic field: Travel mode is driving: Set travel mode to driving. Driving is the default travel mode. Departure time is set: Specify a valid departure_time. You can set departure_time to the current time or some time in the future. It cannot be in the past. No stopover waypoints: Don't include stopover waypoints. If the request includes waypoints, prefix each waypoint with via: to influence the route but avoid stopovers. For example, &waypoints=via:San Francisco|via:Mountain View|... More than 10 waypoints: When you include between 11 and 25 waypoints. Waypoints optimization.: The request sets the optimize parameter to true for waypoints. For example, &waypoints=optimize:true|San Francisco|Mountain View|... Location modifiers: When you use the following location modifiers to indicate how drivers should approach a particular location: side_of_road heading
	Pricing	Main pricing table India pricing table

Other usage limits

While there is no maximum number of requests per day, the following usage limits are still in place for the Directions API:

• Maximum allowed number of waypoints per request: 25
  • Using 1–10 waypoints is billed at the Directions SKU rate.
  • Using more than 10 waypoints (11–25) is billed at the Directions Advanced SKU rate.
  • 3,000 QPM (requests per minute), calculated as the sum of client-side and server-side queries.

Terms of Use restrictions

For information on terms of use, see policies for the Directions API, and the License Restrictions section of the Google Maps Platform Terms of Service.

---