Google Says Goodbye to API Keys with New Geocoding API

Google has released a new geocoding web service that is sure to bring a smile to map mashup developers working with the Google Maps API. Announced this week on the Google Geo Developers Blog, version 3 of the popular geocoding web service has been released, with several improvements and new features that will make it easier geolocate addresses. The new geocoding web service shares many of the geocoding improvements included with v3 of the Google Maps API:

  • A flatter response format for address components that is easier to parse
  • The ability to tag an address component with multiple types
  • Both full names and abbreviations for countries and states
  • Differentiation between rooftop and interpolated geocoder results
  • Both the bounding box and recommended viewport for each result

As with the previous version (which is now deprecated), the new version of the geocoding web service supports reverse geocoding and it provides a RESTful API that returns results in either JSON or XML. The latest set of documentation includes additional discussion of the address component types and feature geometries returned with each result. Note that in contrast to the v2 service, the new geocoding service does not provide an accuracy "score" attribute, but rather results with a set of address components (e.g., intersection, postal code, etc.) and a location type for the feature geometry that indicates the accuracy and precision (e.g., rooftop, range interpolated, geometric center, etc.).

Perhaps one of the most exciting new features is the elimination of the need to use an API key to issue requests to the geocoding service (although URL signing is required for Maps API Premiere customers). In lieu of the API key requirement, new geocoding request limits are also in effect, with a 2,500 daily request limit per IP address. If you're unsure about the best approach to using client-side versus server-side geocoding Mano Marks has a recent post that outlines some good strategies.

This is a nice and worthwhile improvement to a valuable web service that map mashup developers have come to rely on for a variety of needs. We're looking forward to seeing how developers leverage the new service for the thousands of map mashups out there that use the Google Maps API.

Andres Ferrate



As a developer using Google maps API V3 beta for quite some time, I can testify that V3 is much faster compared to V2, although it does not support the full feature set of V2 as yet.


matt cutts twittered about this post 1 min ago.

here I am. :)


Is it likely to increase my success rate?

2500 is a generous limit, but if you have someone who sits behind the firewall with a bunch of devices that could be a problem. Do you know if the limit can be increased for special IPs?

I'm convinced that Google doesn't know what they're doing when it comes to APIs. They seem to enjoy making major changes or just cut people off completely. At least the maps API seems more stable and built better than their search API :(

2500 queries a day is well not a good limit for productive purposes . If you have a site that has around 3-5 thousands visitors a day & each one uses google maps to pinpoint their address, you can easily exhaust your geocoding limit . The better option would be to use your own geocoding address database, you can refer this link where there is a

detailed description of how you can setup your free geocoding address