Release Notes

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.

January 11, 2021

From now we require conferenceData to be consistent with conferenceData.conferenceSolution.key.type; meaning only Google Meet calls can have conferenceData.conferenceSolution.key.type set to hangoutsMeet. All 3P video conference providers are expected to set conferenceData.conferenceSolution.key.type to addOn.

September 07, 2020

Bug fix: Meet video conferences should be added explicitly using the existing parameters (see steps 1 and 2 below):

  1. Set conferenceDataVersion query parameter to 1.
  2. Set conferenceData.createRequest event property as follows:
    • conferenceData.createRequest.conferenceSolutionKey.type to hangoutsMeet,
    • conferenceData.createRequest.requestId to unique request id.

We stopped auto-populating Meet for API calls (such asEvents.insert) to prevent Meet conferences being added unintentionally via 3rd parties.

March 16, 2020

Service accounts created on or after March 2, 2020 are only able to invite guests using domain-wide delegation of authority .

September 27, 2019

The Calendar API allows attaching a conference data of type addOn to a new or existing event using Events.insert or Events.update methods.

November 19, 2018

Starting on January 7, 2019, notifications and reminders using the sms method type will be ignored. The API calls setting such notifications and reminders will still succeed and modify all the other fields.

Since Calendar offers in-app notifications, you can still get notified, regardless of your device or connection. For more information see Google Calendar SMS notifications to be removed.

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 through the sendUpdates 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 infrastructure 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.

2017

July 12, 2017

Hangouts and Google Meet conferences are now supported in Calendar events via the conferenceData 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.