The following changes were introduced on June 11th, 2018. For more details, see the Guide for Existing Users.
API keys are now required
Web Service) now have a
fieldsparameter, allowing your app to return only the specified Place data.
- Find Place (Web Service) is a new Place Search feature that takes a text input, and returns the requested place data.
- FindPlaceFromQuery returns a place based on a text query (for example, the name or address of a place).
- FindPlaceFromPhoneNumber returns a place based on a phone number.
- Updated pricing is now in effect for all products, including the recurring $200 monthly credit per billing account.
- The billing requirement is now being enforced. All projects must be associated with a billing account.
- New Query per Second (QPS) limits are now in effect.
- The new Google Maps Platform Terms of Service is now in effect.
- New users of the Maps Elevation API, must contact sales for access.
Consult the Guide for Existing Users to find out more about changes to product names and billing SKUs.
Maps Embed API requests using Directions, Street View, or Search modes are now billed.
Places services are now billed in a more granular manner. Places Details requests, Places Text Search requests, and Places Nearby Search requests are now reported separately.
Places data SKUs are now reported (Basic Data, Contact Data, Atmosphere Data). For example, a single Place Details request may have multiple SKUs depending on the data that was returned.
QPD limits will be gradually removed in the coming weeks.
From June 11th to July 16th
On June 11th, we launched the new Maps, Routes and Places functionality. To provide you with an additional month of lead time, our new terms and pricing did not go into effect until July 16th. During this transition month, the following was in effect:
- Directions API requests using waypoint optimization and/or traffic models began to be billed as Directions Advanced (until July 16th, the cost of all requests was based on the previous pricing model).
- Distance Matrix API requests using traffic models began to be billed as Distance Matrix Advanced (until July 16th, the cost of all requests was based on the previous pricing model).
Premium Plan Customers
- Find Place requests are charged the same as a Places API server-side and client-side request (2 Maps API credits).
- Requested data fields do not affect the cost of a Places Details or Places Search request.
- Autocomplete session billing is not supported; Autocomplete will only be billed per request.
- Understanding billing for Maps, Routes, and Places
- Pricing Sheet (effective July 16, 2018)
- Pricing Calculator
- Guide for Existing Users