Google Workspace adds API tools for secondary calendar management

Google Workspace has introduced two new features in its Calendar API to help administrators manage secondary calendars more efficiently. The updates, announced on 18 June 2026, provide programmatic alternatives to manual processes in the Admin console and prepare organizations for upcoming changes to secondary calendar data lifecycles.

The first enhancement, a transfer API, allows administrators to change ownership of secondary calendars between users within the same organization without requiring confirmation from the recipient. Unlike the existing Admin console feature, the API enables transfers of individual calendars rather than all data associated with a user. This granularity is intended to reduce administrative overhead for organizations managing large numbers of shared calendars.

The second feature is an organization filter for the CalendarList:list API method. This filter restricts results to secondary calendars owned by the organization, excluding those created by external users. When combined with the users.list method from the Admin SDK API, administrators can generate a complete inventory of organization-owned secondary calendars across all user accounts. The dataOwner field can then be used to verify ownership status, which may be necessary for compliance or migration planning.

Why these changes matter

The updates address two longstanding pain points for Workspace administrators. Manual transfers via the Admin console are time-consuming for organizations with hundreds or thousands of secondary calendars, particularly in scenarios like employee departures or role changes. The new API endpoints allow these processes to be automated, reducing the risk of human error and freeing up administrative resources for other tasks.

The organization filter is tied to an upcoming policy change: secondary calendars will soon follow the lifecycle of their owner. This means that when a user leaves an organization, their secondary calendars may be deleted unless ownership is transferred. The filter provides a way for administrators to proactively identify calendars that may be affected by this change, allowing them to take action before data is lost. While the exact timeline for the lifecycle policy update has not been disclosed, the filter gives organizations a tool to prepare in advance.

Implementation details

Both features are now available to all Google Workspace customers. The transfer API and organization filter are accessible through the existing Calendar API, requiring no additional setup beyond standard API authentication. Administrators can begin using these features immediately, though Google has not provided a specific end date for the rollout process.

The transfer API replicates the functionality of the Admin console’s data transfer tool but with added flexibility. It does not send notification emails to the recipient, which may be useful for bulk operations but could also lead to confusion if users are unaware of the change. Administrators are advised to communicate ownership transfers internally to avoid disruptions.

For organizations using the filter, Google recommends combining it with the Admin SDK’s users.list method to generate a comprehensive report of secondary calendars. This approach ensures that no calendars are overlooked, particularly in large organizations with complex user hierarchies. The dataOwner field can then be used to verify current ownership, which may be necessary for audits or compliance checks.

What to watch

The introduction of these API tools suggests a broader shift in how Google Workspace handles secondary calendar management. The upcoming lifecycle policy change, which will tie secondary calendars to their owners, could have significant implications for organizations that rely on shared calendars for collaboration. Administrators should monitor for further announcements about the timeline for this policy update and consider auditing their current secondary calendar usage to identify potential risks.

Additionally, the new API features may encourage third-party developers to build tools that integrate with Google Workspace for calendar management. Organizations using custom scripts or third-party solutions should test these integrations with the new endpoints to ensure compatibility. Google has not indicated whether additional API enhancements for calendar management are planned, but the current updates align with a trend toward greater automation in administrative tasks.