title: Do Google API keys work with Google Maps web services, e.g. geocoding?
body: <p>I'm using Google Maps web services to perform server-side (reverse) geocoding.</p>
  <p>I've got a browser-side and server-side Google API key from the Google APIs Console, which permits the Google Maps JS API to use higher request quotas, and enables pay-per-use for overages (successfully tested in-browser via JS).  But the server-side key doesn't seem to work on web services requests.</p>
  <p>For example, this URL works fine:<br>
  <a href="http://maps.googleapis.com/maps/api/geocode/json?sensor=true&amp;latlng=43.477329,-80.548601" rel="nofollow noreferrer">http://maps.googleapis.com/maps/api/geocode/json?sensor=true&amp;latlng=43.477329,-80.548601</a></p>
  <p>But if you add a &quot;key=...&quot; parameter, as in the other APIs, I get a REQUEST_DENIED status.</p>
  <p>Am I doing something wrong, or is this just not supported on the web services APIs (yet)?  Will it be supported in the future?</p>
  <h3>See also</h3>
  <blockquote>
  <p><a href="https://stackoverflow.com/q/9847022/1303981">request_denied when i include key=my_api_key</a></p>
  </blockquote>