This page is only for customers with a previous Maps APIs for Work or Maps API for Business license. This page is not applicable to customers with the new Google Maps Platform Premium Plan, which became available in January 2016.
Usage limits
Google Maps APIs for Work customers are provided with the following usage limits for the Google Maps Platform web services:
Web service | Limits |
---|---|
Directions | Daily quota starting at 100,000 requests per 24 hours, based on annual contractual purchase. Maximum of 23 waypoints per request. Rate limit of 10 requests per second. |
Elevation | Daily quota starting at 100,000 requests per 24 hours, based on annual contractual purchase. Maximum of 512 points per request. Rate limit of 10 requests per second. |
Geocoding | Daily quota starting at 100,000 requests per 24 hours, based on annual contractual purchase. Rate limit of 10 requests per second. |
Distance Matrix | Daily quota starting at 100,000 elements per 24 hours, based on annual contractual purchase. Maximum of 625 elements per query and a maximum of 1,000 elements per 10 seconds. |
Time Zone | Daily quota starting at 100,000 requests per 24 hours, based on annual contractual purchase . Rate limit of 10 requests per second. |
Roads | Daily quota starting at 100,000 requests per 24 hours, based on annual contractual purchase. Rate limit of 10 requests per second. Each request may contain up to 100 points. |
These limits apply to each Google Maps APIs for Work client ID and are shared across all applications and IP addresses using a given client ID. The daily quotas are reset at midnight, Pacific Time.
If you need higher usage limits, please contact your Google Maps APIs for Work Account Manager for purchase information.
Reporting
Google Maps Platform web service reports are available from the Metrics page on the Google Cloud Console.
Customize your view by using the filters.
Channel reports
To track usage across different applications using the same client ID,
you may provide an optional channel
parameter with your requests. By
specifying different channel
values for different aspects of your
application, you can determine precisely how your application is used.
For example, your externally-facing website may access the API using a
channel
set to customer
while your internal marketing department may
use a channel
set to mkting
. Your reports will break down usage by
those channel
values.
The channel
parameter must use the following format:
- Must be an ASCII alphanumeric string.
- Period (
.
), underscore (_
) and hyphen (-
) characters are allowed. - The
channel
parameter is case-insensitive; upper-case, mixed-case, and lower-casedchannel
parameters will be merged into their lower-case equivalent. For example, usage on theCUSTOMER
channel will be combined with the usage on thecustomer
channel. - The
channel
value must be a static value assigned per application instance, and must not be generated dynamically. You may not usechannel
values to track individual users, for example.
Up to 2,000 distinct channels can be used, per client ID.
The channel
parameter is included in the request URL:
https://maps.googleapis.com/maps/api/geocode/json ?address=101+Main+St &client=gme-yourclientid &channel=your_channel &signature=your_signature