Now for create, edit, delete contacts you need to use the Google Contacts Api.
Google suggests:
For read-only access to users' contacts, use the People API, which
provides both contact and profile information, and does not use the
older GData protocol.
They say also that eventually People Api will replace Contacts Api.
Do you think that in future the Google People Api allow to create, edit, delete contacts?
Update
As Amos Yuen said, Google updated the People Api thus you can use it also for create, edit, delete contancts.
Yes! Google plans on adding support for mutating contacts, as well as reading and mutating contact groups. Those features are under development, stay tuned for their release.
Related
We've discovered that old token with the Google Contacts scope https://www.google.com/m8/feeds/ can be used to access Google People API to access user' contacts. Migration guide provided by Google explains what new scopes Google People API needs, but doesn't explain whether the old token can be kept (https://developers.google.com/people/contacts-api-migration).
Keeping the old token is the preferred option because it doesn't require user interaction (user doesn't have to re-authorize his/her Google account on our system).
According to Google - on December 15th - 100% of Contacts API requests will return an error, but what will happen if requests are made to Google People API, but with the Google Contacts access scope?
It will work for reading and writing contacts and contact groups, but not "Other contacts" or directory data. See https://developers.google.com/people/contacts-api-migration#scope_migration
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'm having a problem with the 2 APIs above. Given the next scenario: I have 2 different google accounts. One that doesn't use Google+ and a second account that uses Google+
When using Contacts API on the first account that doesn't use Google+ I can see all my contacts:
GET /m8/feeds/contacts/<email>/full
Same for the second account that uses Google+.
When I'm using People API for the first account that doesn't use Google+, I'm getting an empty response (actually I'm getting just the next sync token:
GET https://people.googleapis.com/v1/people/me/connections
With the next scope:
https://www.googleapis.com/auth/contacts
Returns:
{
"nextSyncToken": "CMe6...."
}
The same call for the second account (with Google+) works like a charm
The only difference between the 2 accounts is Google+, is it possible that People API only works for accounts with Google+? Or is it something else that I'm missing
I found the difference between the 2 APIs and it has nothing to do with the fact that one of the accounts is connected to Google+ or not
People API will only fetch the contacts that are under the account "My contacts" contacts, while Contacts API will also fetch the other contacts lists ("Other contacts", "Most contacts", ...)
The People API is the newer version.
From Google APIs related to People API page:
The Google Contacts API will be deprecated in the future. The People API is the recommended replacement for apps that read contact data.
It is also important to note that the People API does in fact allow the developer to use "other contacts" just like Contacts API did. In addition, when migrating you should not have to re-ask for user consent to the following:
https://www.google.com/m8/feeds
https://www.googleapis.com/auth/contacts
https://www.googleapis.com/auth/contacts.readonly
Please see these links for further reading:
https://developers.google.com/people/related-apis (Contacts API vs People API)
https://developers.google.com/people (Intro to People API)
I basically just copy/pasted most of this stuff but hopefully, some people find this helpful as I too was curious to find these answers :)
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.