Did Google changed recently "his terms" about the Google Maps APIs ??
My APIs were working fine and I had billing enabled even if I never was billed cause I never reached the free 2 500 requests / day allowed.
Now it seems that we are limited to 100 requests / day + 1 request/second/user... and I believe my app is not working fine anymore because of this (unless the API keys could have changed with Google's changes?!?).
Is there anyone who also has billing enabled and still is limited to 100 requests per day?
Or anyone knows how to get rid of this limits?
Thanks in advance for your help!!
I don't think so.
This is exactly what the Google Developer Console told me three minutes ago.
Related
Like everyone else, I received an email saying that I need to activate billing to continue using the Google Maps API, and so I did. Now I try to understand what the cost my API usage will be – and I’m lost.
On Google Cloud Platform API / API and services I can see that there are 1 635 Maps Elevation API calls and 1157 Maps Java Script API calls at noon today.
At the same time, under IAM and administration / Quotas I see : 123 / 2500 requests per day.
What is the relation between the 1635+1157 API calls and the 123 requests?
I used 63 842 Elevation API calls and 36 023 Maps Java Script calls during the last 30 days – according to the price sheet google cloud price sheet.
This would cost 63842*5/1000+36023/1000*7 $ = 571 $ - yet the price shown is $0 for now.
It’s a free website - if I have to pay this kind of money it will be down next month…
Sorry if this is not the right place to ask, but I do this as a hobby. Thanks.
Just a little summary, now that the new cost scheme is in effect:
The Google Cloud Platform API / API and services section is the reference for computing API usage cost
The IAM and administration / Quotas section ‘may take more time to update’ (according to Google support) and was off by a factor of 10 in my case. I could never figure out the details (maybe something about the time zone ?), but I understand that you are not supposed to use it to check usage on a daily basis (use 1. For that)
Even if the mail from Google says API usage will ‘probably continue to be free’ in your case, now is a good time to check (half way through the first month): in my case, the actual cost would have roughly been 500 $ (-$ 200 free offer).
My solution to the problem on my free website was to remove the google maps from it. :-(
Thanks to all who tried to help.
I've searched extensively, but haven't found anything that matches my problem. We have a site that is hitting our daily 25000 hit javascript API limit. I know, I know, that sounds common enough, but I'm sure it's the daily limit and not the IP or hourly one because the Maps dashboard shows us getting about 1800 hits/hr right now. Google Analytics on the site, however shows the maps page only getting about a 20th of that on the locations page. (~4000 hits/day)
We have the API key HTTP Referrer security set so it's unlikely we are getting maps DOS'd. We've also generated a new account and API key, and confirmed that all of the traffic immediately switched over.
I've confirmed that the site is only making one QuotaService request per locations pageload as well.
Ok, now here's where things get weird. Our analytics traffic shows a pretty standard day/night sine wave of pageloads. Our Maps traffic is all over the place, though. The low point from Oct 22, 5am to Oct 23, 10:30pm shows the hits almost exactly as I would expect. .01 to .02 hits/s in the middle of the night, and .04 to .05 h/s in the middle of the day. The traffic during all other time I can't account for. Any thoughts, or tools to help track this down would be appreciated.
Maps traffic pattern screenshot
My google maps api works for about an hour and returns the correct results. Then, after that hour, it just stops displaying results.
google limits API queries to 1000/day. Is it possible that you have exceeded this limit?
source
That is exactly what I found. The limit is 150,000 per day IF YOU REGISTER A CC number. Registered mine and POOF, it started working.
A console error or warning might be nice, but you get nothing. In chrome dev tools/network I could see traffic going to google on every keystroke, so I knew it was configured.
I am utilizing the Google Maps API to obtain driving directions to several locations on one page. There are JQuery selectors on the page where a user can select a different locations and view the driving directions for that location.
I am loading all of the requests on page load and I seem to be hitting a limit when I load more than 10 where it reports the remaining addresses cannot be found. I'm assuming there's a limit of 10 per second or something like that.
Does anybody have any more information about this, and ways to get around it besides subscribing to the premier service?
Thanks!
The Geocoding service is subject to daily limits per ip address (client) and a maximum request rate, which is probably what's causing the issue for you.
Here is a discussion from this morning on the rates of various services:
Geocoding Services - limits - Google vs Yahoo vs others?
But you will probably find this article/sample from Google more helpful (See the timing Geocoding Requests section):
http://code.google.com/apis/maps/articles/phpsqlgeocode.html
Basically the concept is to add a delay between your requests and to increase that delay each time you receive an error message.
Short answer seems to be:
https://developers.google.com/maps/articles/geocodestrat#quota-limits
I have found that the usage limits are different (lower) when using the javascriptV3 api than when using the web services api directly. I have been getting 'over usage limit' errors from the javascript api at rates as low as 1/s after the first 10 requests or so. The javascript api is determining this on the client side, as the only results showing up in the chrome network panel are successful requests. changing my code to use the web services directly for geocoding (and enabling that specific api in the api console) worked great for me.
We have a Map It feature on a Real Estate Website and its on a Shared Host, the feature basically shows you the location of a property of works fine for a few hours a day but it stops working later in the day because of error Code "620" for the map request from Google maps API KEY.
we need this issue fix immediately.
Sample could be found here http://www.luxuryrentalsmiamibeach.com/The-Setai-Miami-Beach-13
click on the Map It link to see example
The "Map It" link works flawlessly ATM. The Google error Code 620 means G_GEO_TOO_MANY_QUERIES which either means you had too many API requests per IP per day or in an unspecified time frame.
About the too many API requests per day you cannot do much besides load balancing, changing your IP or paying for the Google Maps API. About the too many API requests per time frame (e.g. 2000 requests per minute) you can do something by delaying your requests.
Also think about caching your results serverside to not put too much strain on the Google servers.
There are several tutorials available on the 620 error and how to circumvent it, just google for it. To get you started you can read "Geocoding multiple addresses"