This page lists new features and behavior changes in Calendar v3 API. It is intended to help developers identify recent changes in behavior. Major changes to the Calendar API are also announced on the Google Developers Blog.
October 31, 2018
The Calendar API now supports four new OAuth scopes. The scopes allow your application to limit access to only the data you really need. See Authorizing Google Calendar API Requests for more details.
October 2, 2018
A more flexible approach to sending event change notifications is now available
parameter. The new parameter lets you set event change notifications to do one
of the following:
- notify all the event guests.
- notify only the guests who are not using Google Calendar.
- completely suppress the notifications, for example, during a migration.
Now it is possible to always keep in sync guests who use other calendaring systems, without sending too many non-mandatory emails to Google Calendar users.
March 22, 2018
Support for the JSON-RPC protocol and Global HTTP Batch batch endpoints has been deprecated, and will be fully discontinued on March 25, 2019. This change is being made to the Google API infrastucture and as such affects multiple Google APIs, including Calendar v3.
For more information and migration instructions, see the Discontinuing support for JSON-RPC and Global HTTP Batch Endpoints blog post.
July 12, 2017
Hangouts and Hangouts Meet conferences are now supported in Calendar events via
field. You can:
- Read conference data associated with events
- Copy conference data from one event to another
- Request new conference generation for an event
- Clear conference data associated with events
To learn more, see Create Events.