Distance Matrix API Usage and Billing

You're all set!

Billing has been enabled for your selected project.

Dismiss

Enabling billing

To enable billing, we'll guide you through the Google Cloud Platform Console to complete a few tasks:

1. Create or choose a project
2. Set up or choose your billing profile
3. Enable billing on your project

Cancel Continue

Reminder: To use the Distance Matrix API, you must include an API key with all API requests and you must enable billing on each of your projects.

Pay-As-You-Go Pricing

The Distance Matrix API uses a pay-as-you-go pricing model.

How usage and billing work under the pay-as-you-go model

• The Google Maps Platform APIs are billed by SKU.
• Usage is tracked for each Product SKU, and an API may have more than one Product SKU.
• Cost is calculated by: SKU Usage x Price per each use.
• For each billing account, for qualifying Google Maps Platform SKUs, a $200 USD Google Maps Platform credit is available each month, and automatically applied to the qualifying SKUs.

See guide to understanding billing for more information.

Pricing for the Distance Matrix API

Under the pay-as-you-go pricing model, Distance Matrix API requests generate one of two SKUs depending on the type of request: basic or advanced.

SKU: Distance Matrix

A request to the Distance Matrix API or the Maps JavaScript API’s Distance Matrix Service (excludes requests triggering the Distance Matrix Advanced billing SKU billing SKU).

MONTHLY VOLUME RANGE (Price per ELEMENT)
0–100,000	100,001–500,000	500,000+
0.005 USD per each (5.00 USD per 1000)	0.004 USD per each (4.00 USD per 1000)	Contact Sales for volume pricing

Each query sent to the Distance Matrix API generates elements, where the number of origins times the number of destinations equals the number of elements.

SKU: Distance Matrix Advanced

A request to the Distance Matrix API or the Maps JavaScript API’s Distance Matrix Service that uses traffic information.

MONTHLY VOLUME RANGE (Price per ELEMENT)
0–100,000	100,001–500,000	500,000+
0.01 USD per each (10.00 USD per 1000)	0.008 USD per each (8.00 USD per 1000)	Contact Sales for volume pricing

Each query sent to the Distance Matrix API generates elements, where the number of origins times the number of destinations equals the number of elements.

A Distance Matrix Advanced SKU is charged for a Distance Matrix API or a Maps JavaScript API’s Distance Matrix Service that uses traffic information. Traffic information is used when all the following apply (these are the conditions required to receive the duration_in_traffic field in the Distance Matrix response):

• The travel mode parameter is driving, or is not specified (driving is the default travel mode).
• The request includes a valid departure_time parameter. The departure_time can be set to the current time or some time in the future. It cannot be in the past.

Other Usage Limits

While you are no longer limited to a maximum number of elements per day (EPD), the following usage limits are still in place for the Distance Matrix API:

• Maximum of 25 origins or 25 destinations per request.
• Maximum 100 elements per server-side request.
• Maximum 100 elements per client-side request.
• 1000 elements per second (EPS), 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 Distance Matrix API, and the License Restrictions section of the Google Maps Platform Terms of Service.

Manage Your Cost of Use

To manage your cost of use of the Google Maps Platform APIs, you can set daily limits to all requests to any billable API.

To view or change daily billable limits for the Distance Matrix API, do the following:

1. Go to the Distance Matrix API Quotas page in the Google Cloud Platform Console.
2. From the projects list, select a project.
3. In the Requests section, on the Requests per day line, click the edit icon, then enter the preferred total billable daily quota, up to the limit (if any) specified by Google.

Note: You can set daily billable limits only on billable APIs. If your project doesn't use any billable APIs, then you can't set daily limits.

If your API usage reaches your billable limit on any given day, your application will not be able to access the API for the remainder of that day.

WARNING: Setting a QPD override of zero on a quota bucket may result in the API being disabled on the account. When this happens, API calls will return an error (for example ApiNotActivatedMapError, or REQUEST_DENIED: You need to enable this API). To fix this, set the consumer override to "1". If you are unable to see or modify your QPD override, take the following steps:

1. Revert the project to the previous billing configuration to see corresponding bucket (billable or non-billable).
2. Remove the 0 quota consumer override, by setting it to 1.
3. Re-apply the desired billing configuration.

Related resources

• Managing your billing accounts
• Modify a project's billing settings
• Viewing your cost trends with billing reports
• Setting budgets and alerts
• Capping API usage
• Optimization Guide for Google Maps Platform
• API Key Best Practices

Premium Plan Customers

As of November 1, 2018, Premium Plan customers can migrate to the Google Maps Platform pay-as- you-go pricing model once their current Premium Plan contract expires. Only contracts whose end date is November 1, 2018, or later, can migrate to Google Maps Platform. Contracts expiring prior to November 1, 2018 must be renewed on the Premium Plan. For more information, see the Maps Platform Migration Guide.

Premium Plan Usage Limits

Google Maps Platform Premium Plan customers: Shared daily free quota of 100,000 elements per 24 hours; additional requests applied against the annual purchase of Maps APIs Credits. Limited to 100 elements per client-side request. Maximum of 25 origins and 25 destinations per server-side request. Server-side requests using mode=transit or using the optional parameter departure_time when mode=driving are limited to 100 elements per request. 1,000 server-side elements per second. Note that the client-side service offers Unlimited elements per second, per project.

Additional benefits of a premium plan: Annual contracts with enterprise terms 24 hour technical support Service level agreement (SLA) Licenses for internal, OEM, and asset tracking use cases See the Premium Plan guide for more info.