May 22, 2024
The following changes to
events from Gmail
take effect on
May 30, 2024
:
- Events from Gmail use
fromGmail
instead
default
as the value for the
eventType
field. You can filter by this new event type using the
events.list()
and
events.watch()
methods.
- Events from Gmail use the email address of the email recipient as the event organizer instead of
unknownorganizer@calendar.google.com
.
- You can only update the event
properties
, such as reminders, color ID, visibility, status, and extended properties of
Event
resources with the event type
fromGmail
.
For details, see the Calendar API
Events
reference documentation
.
May 17, 2024
The following change takes effect on
June 3, 2024
:
For
batch operations
on
Event
resources, a batched item returns an HTTP
409 Conflict
status code if the batch operation can't successfully execute this item due to conflicts with other requested batched items.
Suggested action:
Exclude all successfully finished and failed batched items and retry remaining items in a different batch operation or by using single event operations.
For more information, see
Handle API errors
.
February 07, 2024
The following changes will take effect on
March 11, 2024
:
- The use of
event type
filters will be considered when reviewing quota increase requests. Before you request a quota increase, make sure you specify the event types you need as a parameter for your application.
- Both
events.list
and
events.watch
will use the same default event type filter.
- To help with error handling, improved error messages will be returned when unsupported operations are attempted on special event types, such as working location, out-of-office, and focus time events.
For more information, refer to the following:
February 06, 2024
Generally available
: The
events.watch()
method now supports the
eventTypes
field as a query parameter so that you can subscribe to changes about specific Calendar events, such as working location, out-of-office, or focus time events. For details, see the
reference documentation
.
December 07, 2023
To fix a bug that prevented events of
eventType != 'default'
from importing, we updated the code sample in
Populate a team vacation calendar
, the popular Apps Script + Calendar API solution. Review the code change in
GitHub
.
August 17, 2023
August 22, 2022
March 23, 2022
The Calendar API now supports custom attachments. See
Calendar add-ons
for more information.
October 20, 2021
The Calendar API now exposes a new
eventType
. The new type is called
focusTime
and allows users of the API to distinguish the special focus time events. For more information, see the
API reference
.
May 18, 2021
Two new quotas now exist for the Calendar API in addition to the general
Calendar usage limits
:
- Per minute per project.
- Per minute per project per user.
See
Manage quotas
for more information.
February 08, 2021
Starting today, all existing and new out of office events will be updated to set the organizer to
unknownorganizer@calendar.google.com
instead of the Calendar owner. It may take 2-3 weeks for this change to fully roll out.
You can use the calendarId from the API endpoint
https://www.googleapis.com/calendar/v3/calendars/calendarId
to identify the owner of the out of office event.
February 01, 2021
The Calendar API now exposes a new field for events. The new field is called
eventType
and allows users of the API to distinguish special event types, such as
outOfOffice
. For more information, see the
API reference
.
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
Meet video conferences should be added explicitly using the following existing parameters:
- Set
conferenceDataVersion
query parameter to
1
.
- 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 as
Events.insert
) to prevent Meet conferences being added unintentionally via 3rd parties.
March 16, 2020
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
October 02, 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
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
.