What is the limit of allowed waypoints in the free plan of Google Maps Directions API? Their site indicates this:
Up to 23 waypoints allowed in each request containing an API key, or up to 8 waypoints when no API key is supplied, or up to 8 waypoints when using the Directions service in the Google Maps JavaScript API
Which is unclear, because first it tells you that you're allowed to use 23 waypoints when you have a key, and lastly it says that you're only allowed to use 8.
See this issue in the issue tracker: Issue 8886: Bug: Directions API description of MAX_WAYPOINTS_EXCEEDED is not clear
from that issue:
Nov 16, 2015
Project Member #8 andr...#google.com
The post refers to Web Services.
The situation is the following:
Web Services (Directions API, Distance Matrix API) both free users (API keys) and Maps for Work users (client ID + signature) have 23 waypoints
JavaScript API (directions service, distance matrix service): free users (API keys) have 8 waypoints, Maps for Work users (client ID) have 23 waypoints.
Jan 22, 2016
Project Member #12 ekelar...#google.com
we're looking into adding this to JavaScript API as well, but there are some blockers on this, so we decided to roll it out for the web services without waiting for JS.
Related
I want to use google maps api for an assignment in my studies.
when entering the official google maps on chrome it seems like there's a destinations number limitation to 10 - so you can't create a route of more then 10 destinations.
Will that same limitation also be if i'll use the google maps API in my own project that I'm creating and not through the official website?
Use a key.
Without a key, the limit is 8 waypoints. With a (free) key, the limit is 23 waypoints (plus origin and destination).
From the documentation (note that keys are now required, some sites are grandfathered with keyless access):
Limits and Restrictions for Waypoints
The following usage limits and restrictions apply:
The maximum number of waypoints allowed when using the Directions service in the Google Maps JavaScript API is 23, plus the origin and destination. The limits are the same for the Google Maps Directions API web service.
For the Google Maps Directions API web service, customers are allowed 23 waypoints, plus the origin, and destination.
Google Maps APIs Premium Plan customers are allowed 23 waypoints, plus the origin, and destination.
Why Google Maps Timezone Web Service works with/without specifying API-KEY but Google Places Web Service needs API-KEY?
Generally why some google web services don't insist on entering API-KEY, do they monitor IP?
As far as I know Google intends to deprecate a keyless access to their APIs. The last one was keyless access deprecation for Maps JavaScript API, Static Maps API and Street View API announced on June 22, 2016.
https://maps-apis.googleblog.com/2016/06/building-for-scale-updates-to-google.html
Probably, keyless access for web services will be deprecated at some point as well.
Currently, if you execute TimeZone API with an API key your quota is applied on per project basis. Otherwise the quota is applied on per IP basis. If you share the IP with somebody else probably you couldn't execute 2500 daily requests. So, an API key is a better option to control your usage.
Update
With migration to Google Maps Platform that was announced on May 2, 2018 the keyless access was deprecated for all APIs. From now on you must use an API key and enable Billing account in your project in order to be able to use Google Maps APIs.
I'm working on a project that uses Google Maps APIs to reverse geocoding locations.
The customer is supposed to buy a licensed API key when rolling out to production.
Now I'm developing the application and I also need to test its functionality when using a valid, whether free or business, API key.
Let's pick a sample reverse geolocation request
https://maps.googleapis.com/maps/api/geocode/json?latlng=40.714224,-73.961452&sensor=true
I have registered a developer account into https://code.google.com/apis/console/ and generated a server API key. Then I enabled Google Geolocation APIs and Google Maps API v3 (I think I need only the second).
When adding &key=XXX parameter to my previous request I get an error that the key is not valid.
Reading documentation with more attention, I discovered that the geolocation service I'm using is actually part of Maps Web Service APIs (Maps V3 APIs run on browser as Javascript). I tried to find those APIs into the Services list of my console but couldn't find anything more.
How do I use Google's reverse geocoding API with a business key for a project that will handle thousands of daily requests?
with no api key, the Google Geocoding API has the following limits in place: 2,500 requests per day.
Google Maps API for Business customers have higher limits: 100,000 requests per day.
to use to API for Business you have to use URL signing, see https://developers.google.com/maps/documentation/business/webservices/auth
NB: If you're switching from the free API services to a Maps API for Business implementation, you must remove the key parameter from your requests. Google Maps API web services will deny requests made with both a client ID and a key.
The Geocoding v2 API stopped unexpectedly.
e.g.
http://maps.google.com/maps/geo?q=27703&output=json&key=AIzaSyBVr3n3IVZzakGvtIWeRaJEXsC63JHZ0w8
I'm not able to get lat,long from the API. The output from server is:
{
"Status": {
"code": 610,
"request": "geocode"
}
}
I searched for status: 610 but could not find any relevant info.
Thanks.
The service has been stopped.
It is the 8th of March.
See the top of this page for information on the death of v2
See The Google Geocoding API for v3
...
Edit.
Actually, there is a page about upgrading to v3 that may be of use.
...
Edit.
As just pointed out, the Geocoding API V2 deprecation timeline was just extended by another 6 months, but be careful of your usage.
From #FrVaBe's link:
"Today we’re also reducing the limit on Geocoding API V2 from 15,000 requests per day to 2,500 requests per day, which is equivalent to the daily limit on the Geocoding API V3."
It seems that you are using Geocoding API V2. You can find the list of status codes here. The status you get is
610 G_GEO_BAD_KEY
The given key is either invalid or does not match the domain for which it was given.
So check to use the right API version (obvious V3 - V2 has been stopped as #Rafe mentions)
I never used this API but request should have this form
http://maps.googleapis.com/maps/api/geocode/output?parameters
The Geocoding v2 API stopped unexpectedly.
e.g.
http://maps.google.com/maps/geo?q=27703&output=json&key=AIzaSyBVr3n3IVZzakGvtIWeRaJEXsC63JHZ0w8
I'm not able to get lat,long from the API. The output from server is:
{
"Status": {
"code": 610,
"request": "geocode"
}
}
I searched for status: 610 but could not find any relevant info.
Thanks.
The service has been stopped.
It is the 8th of March.
See the top of this page for information on the death of v2
See The Google Geocoding API for v3
...
Edit.
Actually, there is a page about upgrading to v3 that may be of use.
...
Edit.
As just pointed out, the Geocoding API V2 deprecation timeline was just extended by another 6 months, but be careful of your usage.
From #FrVaBe's link:
"Today we’re also reducing the limit on Geocoding API V2 from 15,000 requests per day to 2,500 requests per day, which is equivalent to the daily limit on the Geocoding API V3."
It seems that you are using Geocoding API V2. You can find the list of status codes here. The status you get is
610 G_GEO_BAD_KEY
The given key is either invalid or does not match the domain for which it was given.
So check to use the right API version (obvious V3 - V2 has been stopped as #Rafe mentions)
I never used this API but request should have this form
http://maps.googleapis.com/maps/api/geocode/output?parameters