would it would help to have the apikey linked to an account that also has other Google services for the company associated with it, like Analytics, etc. also does the sensor variable speed up the call as well
If you are using the v2 API, you will need an API key from the Maps API Sign Up site. However note that the v2 API has been officially deprecated as of May 19, 2010, and you are encouraged to use the v3 API instead. The v3 API does not require an API key.
As for the sensor parameter, no, it will not make the map load faster.
Related
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 reading the documentation for the Google Geocoding API, and I noticed that it says that a key is required in a geocoding request, but when I do "https://maps.googleapis.com/maps/api/geocode/json?address=LosAngeles,usa" it gives me the expected result.
Why is this? Is the documentation wrong? Will it start asking for the key after a certain amount of requests? Or is there something I'm not understanding?
Providing a key is not required for most geocoding API requests. When you do not provide a key, Google will use an IP-based quota to determine when you reach the 2,500-queries daily limit.
Some parameters require a key and will not allow IP-based quota. These are explicitly marked in the documentation with:
Note: This parameter is available only for requests that include an API key or a client ID.
Currently, this is only for two parameters in reverse geocoding: result_type and location_type.
source
Beginning on June 11, 2018, you’ll need to enable billing with a
credit card and have a valid API key for all projects. This will give
you the ability to scale easily with less downtime and fewer
performance issues. In addition, we’re simplifying our 18 individual
APIs into three products: Maps, Routes, and Places.
Also, in June 2016 we announced that we would stop supporting keyless
usage, meaning any request that doesn’t include an API key or Client
ID. This will go into effect on June 11th, and keyless access will no
longer be supported. At that time, keyless calls to the Maps
JavaScript API and Street View API will return low-resolution maps
watermarked with “for development purposes only.” Keyless calls to any
of the following APIs will return an error: Maps Static API (including
Static Street View), Directions API, Distance Matrix API, Geocoding
API, Geolocation API, Places API, Roads API, and Time Zone API.
To avoid a service interruption to your projects, please visit our Get
Started page to enable a billing account and generate an API key. Once
you generate and secure an API key, make sure to update your
application with the new API key.
"Static" Street View documentation says that all request should have an API key added. There is also description how to add it. But looking at JavaScript SV documentation there is no mentioning of API keys. Is using API keys with "dynamic" SV required? How do I add them to my requests?
It is not required but you should according to Google:
All Maps API applications* should load the Maps API using an API key. Using an API key enables you to monitor your application's Maps API usage, and ensures that Google can contact you about your application if necessary. If your application's Maps API usage exceeds the Usage Limits, you must load the Maps API using an API key in order to purchase additional quota.
Here is the link on using the API Key
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.
It seems that in between the development of my website and the go-live (now) Google has phased out the Google Maps v2 API. I'm all for progress but to rewrite all my map code seems to be a bit too much for me to handle at this point in time.
Is it sill possible to obtain a Google Maps v2 API key in some hidden corner of the web?
Get a new Console key from https://code.google.com/apis/console as described in the Version 3 docs at https://developers.google.com/maps/documentation/javascript/tutorial#api_key. Console keys work with Version 2 and provide the benefits of statistics reporting.
It's against the Terms to use the API without a key, and in fact this won't work on domains which aren't Google's like http://codethink.no-ip.org/mapHacks.html. The webcache version of that page works because it's on a Google domain.