Important Updates

The following changes were introduced on June 11th, 2018. For more details, see the Guide for Existing Users.

API keys are now required

We began enforcing the use of API keys, effective June 11th 2018. Keyless usage will result in a degraded experience, or an error.

Product changes

  • Place Details requests (JavaScript, Web Service) now have a new fields parameter, 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.
  • The Places Library, Maps JavaScript API now has two new types of Find Place request:
    • 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.

Billing changes

  • 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.

  • Place Autocomplete now supports session-based billing. When a session token is used, autocomplete requests are not billed independently, but are instead billed once after a full autocomplete result is returned. For Autocomplete in the Places Library, Maps JavaScript API, sessions are automatically handled by the API (no code changes are required).

  • 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 11 to July 16, 2018

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:

Premium Plan Customers

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

The new product changes are now available for Premium Plan customers, and are billed similarly to the existing Places API features:

  • 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.


Enviar comentarios sobre...

Google Maps Platform
Google Maps Platform