At the moment, the People API does not retrieve all the contacts that the Contacts API did, but is suggested as a replacement. If I wanted the old list that included Most Contacted and Other Contacts, I believe I would need the Contacts API. How long is this API intended to be supported?
Yes, People API will replace the Contacts API.
The new People API uses the newest protocols and technologies and will eventually replace the Contacts API which uses the GData protocol.
Announcing the People API
The Contacts API has not been deprecated yet so we don't know how long it will be around. Once Google deprecates an API it is typically available for 1-3 years before being fully shut down.
Well, it is still being supported. Based on the Google Contacts v3 documentation, that if you only want for read-only access to users' contacts, then that is the time you need to use the People API. It is not stated here that the Contacts API v3 will be deprecated and will stop the supporting here.
Also based on the Google Contacts API Terms of Service, after April 20, 2015, the Deprecation Policy in Contacts API will not apply.
Related
Is there a way to register Authorized URLs in Google Maps via an API?
Currently, I am manually adding URLs through the Google Maps Support portal, but I would like to be able to make an API call when a customer submits a new domain to my service.
Unfortunately, currently there is no way to manage API key restrictions programatically.
There is a feature request in Google issue tracker to make it possible:
https://issuetracker.google.com/issues/35829646
Please star this feature request to add your vote and subscribe to notifications, at the moment it has only 6 stars, not enough to increase its visibility.
Update from Google
The best way to handle thousands of authorized domains is to use an API to programmatically manage your API Keys and their restrictions, and we have recently launched a new service that allows you to do this.
This API is still in Alpha. If you are interested in becoming a Trusted Tester for this service, you can use the following form to sign up, please read the instructions carefully:
https://forms.gle/qx2SMcarWCAsbWVp7
Please note that this API is not part of the Google Maps Platform. After you fill out the form, you will be contacted by the API Keys API team with instructions on how to get started, and how to receive support.
API Keys API is currently free of charge. However, please note that use of Cloud Endpoints may be subject to charges at high traffic volume. You can check the pricing sheet here:
https://cloud.google.com/endpoints/pricing-and-quotas
One of our customers is using google maps with a "Client ID". We've developed our product using the Google API Key. All of the features of the map are working properly using the API key, but we are unable to confirm that the client will get the same results with the Client ID since we do not have one. Two question, do you believe that the features will work the same using either the API or the Client ID? Second question, how much does it cost to purchase a Client ID?
Client IDs and API Keys are forms of authentication and authorization. There are easy-to-follow guidelines on their proper usage and their limits. Everything you need to know about them can be found in the documentation (also try seeing the docs per product in the 'For more information' section):
https://developers.google.com/maps/premium/overview#authentication_and_authorization
Related SO post and answer about using Client IDs for their Javascript API:
google maps api javascript usage
For pricing, read more about it here:
https://developers.google.com/maps/pricing-and-plans/
EDIT: There has been recent Google Maps Platform pricing and product changes You'll always need an API key and a valid billing account associated to your Project if you want to use the Google Maps Platform APIs. If you've never had a Client ID then you don't need to worry about it, just continue using your API keys.
You may run into some APIs (i.e. Speed Limits API) that seem to need a Premium Plan account. If you really need access to these, simply contact sales using this form.
P.S.
When using API keys, be sure to properly restrict them!
I am starting to develop an extension that I want to sell.
It requires Google Maps Javascript API which requires a APIKEY.
Do I just include Google Maps logic and tell the buyer to get their own api key here https://developers.google.com/maps/documentation/javascript/get-api-key and insert it in the settings. Would rather use Google even if it has its own branding.
Otherwise I was thinking of just using http://leafletjs.com/ because it is open source/free?.
I noticed other people selling plugins with Google Maps included and they don’t seem to have a key. How do they do this, is this allowed.
Thoughts?
What is the Standard with this type of thing?
The API key is now required. Before June 22, 2016 it was optional, but now you have to use it always.
Please have a look at this post for more details:
https://googlegeodevelopers.blogspot.com.es/2016/06/building-for-scale-updates-to-google.html
You can implement the plugin with settings where the customer adds his API key.
However, you should be aware that for several types of applications Google Maps API requires a Premium plan license. For example, asset tracking or intranet solutions may be used only with the Premium plan API key. Otherwise the Standard plan is allowed.
Please have a look at restrictions section of ToS to understand when the customer requires a Premium plan license:
https://developers.google.com/maps/terms#10-license-restrictions
The 22nd of January, I received an email with the subject 'Important: Steps to migrate from discontinued Documents List API' from Google Apps .
Important: Steps to migrate from discontinued Documents List API
Hello administrators,
We recently communicated that Documents List API will be discontinued on April 20, 2015. This change means that service calls for this API will no longer be supported, and any Google Apps features that are implemented using this API will no longer function.
Our records indicate that you may have an application that uses Documents List API, and we recommend that you migrate to Drive API, which has comparable
functionality, as soon as possible.
Here's what you need to do:
Determine if you have an application that makes requests to these
types of URLs:
https://docs.google.com/feeds/
https://docs.googleusercontent.com/
https://spreadsheets.google.com/feeds/
Migrate the applications to Drive
API. If you have questions
about migration, please contact Google Apps for Work Support.
Sincerely, The Google Apps for Work Team
I think it says that applications using https://spreadsheets.google.com/feeds/ should migrate to the new Drive API. But in the new Drive API, this URL is used too:
https://developers.google.com/google-apps/spreadsheets/#sheets_api_urls_visibilities_and_projections
Is there a typo somewhere in the URL either in the email or Drive API documentation?
Or is this email saying that when you determined you used any of these URL's you're OK?
PS: I opened a case at Google but I fear a late response, so I asked here.
Short answer is no.
The Docslist API is being discontinued because it has been replaced by the Drive API. In the case of the Spreadsheet API, there is no replacement API (yet - maybe one day), so it remains supported.
The only gotcha is that at some point, only OAuth 2 will be supported for authentication/authorisation so if you're using OAuth 1 or u/p, you have some work to do.
The official Google response is that the Spreadsheets API will continue to function after the 20 April shutdown:
"Apologies for the confusing email. The sheets API is not yet deprecated and will continue to operate beyond the April shutdowns."
https://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3709
When developing a Google Maps or Recaptcha implementation, you can sign up for a free API key using
However, in a large company, you don't want to tie these keys to a developer's gmail account.
Does anyone have suggestions or best practices how Google API Keys should be managed on an organizational level? Who owns them?
Create a gmail account at the group/organization level and use that for the API key.
You may also want to look at Google Maps Premier API which is more suited for enterprise usage.