Google Updates Access and Limits of Maps API Standard Plan

Google recently made a number of updates to its Standard Plan for the Google Maps APIs. The updates that took effect June 22nd are discontinued support for keyless access; 25,000 free map load limit for JavaScript API, Static Maps API, and Street View Image API; maximum map load limit reduced to 100,000 from 1,000,000; and client-side service requests now count towards the daily limit. Apps created on or after June 22nd are subject to the updated policies and limits.

Active domains created before June 22, 2016 will continue to have access to Google Maps APIs without an API Key. However, apps created on or after June 22nd require a key for access to the Google Maps JavaScript API, Static Maps API, and Street View Image API. However, Google Maps Geocoding API, Directions API, Distance Matrix API, Elevation API, and Time Zone API now share a global quota. Accordingly, apps that continue to make keyless requests to such APIs may endure service degradation due to keyless applications usage spikes. The use of a key will guarantee quality of service, and Google encourages all developers to move towards the use of a key.

Active domains created before June 22nd will continue to enjoy a 90-day rolling grace period for loads in excess of the free, 25,000 loads per day until October 12, 2016. After October 12th, developers must have billing enabled to avoid an error after the 25,000 limit is exceeded. Those already paying for overages will experience no change.

Active domains created before June 22nd, with more than 80,000 daily map loads, can continue to buy quota up to current maximum daily usage plus 25%. However, once usage grows beyond 25% of the maximum daily usage, users will need to migrate beyond the Standard Plan to a Premium Plan. Further Web services requests, free up to 2,500 requests per day, is now calculated as the sum of client-side JavaScript queries and Web Service API server-side queries. 

The nuances of the Standard Plan updates are a bit confusing, and those who might be impacted are wise to review the updates themselves. Google has provided some FAQs addressing grandfathering, changes to the Places API, billing and billing enablement, loads in excess of the maximum limit, domain changes, keyless entry for grandfathered-in accounts, nonprofit use, and media use. Apps created on June 22nd and after are subject to all the new updates.  

Be sure to read the next Mapping article: eeGeo 3D Maps JavaScript API is Now in Beta