Tweet
Migrate your Google Contacts API to People API before June 15, 2021
will be there any updates on time based on google notification: "Migrate your Google Contacts API to People API before June 15, 2021, to ensure error-free API calls; API calls will otherwise return 100% errors by December 15, 2021."
Hello Google Cloud Developer,
We are writing to remind you of, as per our initial announcement in August 2020, the deprecation of the Google Contacts API, effective June 15, 2021. All Contacts API clients should migrate to Google People API before that date.
What do I need to know?
Starting June 15, 2021, API calls will begin returning errors at a steadily increasing rate, until the error rate reaches 100% on December 15, 2021, as outlined below:
The new People API has the same functionality as the legacy Contacts API for all features, but with a new scope, resulting in the following exceptions for “Other Contacts”:
Additionally, the old Contacts scope (https://www.google.com/m8/feeds) provided access to both personal contacts and directory information.
You can learn more in the People API documentation.
Please note that the Domain Shared Contacts API is not affected by these changes.
What do I need to do?
To maintain access to Contact data, you need to migrate all Contacts API calls to People API before June 15, 2021.
With the People API, you will also need to implement new scopes, to ensure error-free API connections. In doing so, you will need to use the appropriate scope, depending on which API feature you wish to access:
Your projects listed below are Contacts API clients and will begin to receive API call errors unless you migrate to People API before June 15, 2021:
Hello Google Cloud Developer,
We are writing to remind you of, as per our initial announcement in August 2020, the deprecation of the Google Contacts API, effective June 15, 2021. All Contacts API clients should migrate to Google People API before that date.
What do I need to know?
Starting June 15, 2021, API calls will begin returning errors at a steadily increasing rate, until the error rate reaches 100% on December 15, 2021, as outlined below:
- June 15, 2021 - September 15, 2021: 1% of Google Contacts API calls will return errors
- September 15, 2021 - December 15, 2021: 10% of Google Contacts API calls will return errors
- December 15, 2021, and onward: 100% of Google Contacts API calls will return errors
The new People API has the same functionality as the legacy Contacts API for all features, but with a new scope, resulting in the following exceptions for “Other Contacts”:
- Clients have read-only permissions for “Other Contacts.” Since sending mutate or write signals back to “Other Contacts” is not supported, your users will have to add the Other Contact as a My Contact if they wish to update its data fields.
- Only basic contact information for “Other Contacts” can be read through the API (for example, full name, email address, and phone number).
Additionally, the old Contacts scope (https://www.google.com/m8/feeds) provided access to both personal contacts and directory information.
You can learn more in the People API documentation.
Please note that the Domain Shared Contacts API is not affected by these changes.
What do I need to do?
To maintain access to Contact data, you need to migrate all Contacts API calls to People API before June 15, 2021.
With the People API, you will also need to implement new scopes, to ensure error-free API connections. In doing so, you will need to use the appropriate scope, depending on which API feature you wish to access:
- To access personal contacts - https://www.googleapis.com/auth/contacts
- To access other contacts - https://www.googleapis.com/auth/contacts.other.readonly
- To access directory information - https://www.googleapis.com/auth/directory.readonly
Your projects listed below are Contacts API clients and will begin to receive API call errors unless you migrate to People API before June 15, 2021: