Google Workspace developer release notes

Developer Preview: Chat apps can now create messages containing cards on behalf of users with user authentication. Additionally, apps can asynchronously update the cards in these messages without requiring user interaction. For more information, see Create and update interactive cards.

Generally Available: When sending a message with app authentication, Google Chat API now supports mentioning users who haven't joined a Chat space or are members of a space that is in import mode. Previously, only sending a message with user authentication was supported. To learn how, see Mention users in a text message.

Developer Preview: You can now build Google Chat apps as Google Workspace add-ons that use Cloud Pub/Sub to receive messages. This architecture is useful if your Chat app is behind a firewall. For details, see Build a Chat app that uses Pub/Sub.

Generally Available: The Gmail Postmaster Tools API v2 is now generally available. The API provides access to the full Postmaster Tools dataset—including compliance status data—and includes enhancements like flexible querying with queryDomainStats and support for batch operations. For details on how to use the v2 API, see the updated Postmaster Tools API documentation.

Generally Available: You can now convert your interactive event-driven Chat apps to Google Workspace Add-ons that extends Chat.

By converting, your Google Chat app can use the Google Workspace Add-ons framework, opening up new possibilities for integration and features within Google Chat and across Google Workspace. For example, instead of two distributions — one Google Chat app and one Google Workspace add-on — you can distribute a single Google Workspace add-on through Google Workspace Marketplace that extends Chat apps alongside other Google Workspace host applications, like Gmail, Calendar, and Docs.

To learn more, see Convert an interactive Google Chat app to a Google Workspace add-on.

The Google Chat platform samples gallery now lets you find samples by products, language, and sample type. The gallery also features the following new samples for building Chat apps:

• Agent2Agent agents
• ADK AI agents
• Dialogflow ES
• Dialogflow CX

License Manager API: The SKU name "Gemini Education" has been renamed to "Google AI Pro for Education." For details, see the Google Product and SKU IDs documentation and announcement.

Developer Preview: You can now dynamically populate drop-down menus in Google Chat apps with data from Google Workspace or external data sources, with an autocomplete functionality. To learn more, see Add interactive UI elements to cards.

Developer Preview: You can now call the Chat API to create and manage custom sections and organize conversations in a personalized view:

• Create section (RPC, REST)
• Delete section (RPC, REST)
• List sections (RPC, REST)
• Update section (RPC, REST)
• Position section (RPC, REST)
• List section items (RPC, REST)
• Move section items (RPC, REST)

To learn more, see Section (RPC, REST) and SectionItem (RPC, REST) in the Chat API documentation.

Generally available: The Chat API now supports reading rich links to Gmail threads in Chat messages that appear as chips. To learn more, see RichLinkType in the Chat API reference documentation.

Developer Preview: You can now access data in Gmail Postmaster Tools v2 using the v2beta API. The new API provides access to the full Postmaster Tools dataset, including compliance status data.

The v2beta API also includes enhancements such as the queryDomainStats method for flexible querying, and adds support for batch operations.

To learn how to use the API, see the Postmaster Tools API documentation.

Developer Preview: Chat apps can find existing group conversations with specific members using FindGroupChats.

Generally available: We're enhancing membership roles in Chat spaces by introducing a new membership role type. In the Chat UI, existing space managers are now owners and a new manager role is added.

Previously, there were three membership role types in Chat API. MEMBERSHIP_ROLE_UNSPECIFIED, which meant a user wasn't a member but could be invited. ROLE_MEMBER, which meant a user was a member of the space. And ROLE_MANAGER, which meant a user was a space manager.

Now, in the Chat UI, ROLE_MANAGER users are called owners; this is a cosmetic change so permissions and the API enum remain the same. To help space owners administer spaces, we're introducing ROLE_ASSISTANT_MANAGER which is called manager in the UI. Possible membership roles include:

• MEMBERSHIP_ROLE_UNSPECIFIED: Default value. For users: they aren't a member of the space, but can be invited. For Google Groups: they're always assigned this role.
• ROLE_MEMBER: A member of the space. In the Chat UI, this role is called Member. Members have basic permissions, like reading messages in a space. Managers and Owners can grant them additional permissions, like adding or removing members, editing space details, and turning history on and off.
• ROLE_ASSISTANT_MANAGER: A space manager. In the Chat UI, this role is called Manager. By default, managers have permission to make other members managers, delete messages, and change space permissions.
• ROLE_MANAGER: A space owner. In the Chat UI, this role is called Owner. Owners have the broadest set of permissions, including permission to make other members owners or delete the space.

To learn more, see Update a user's membership in a Google Chat space and MembershipRole in the Chat API reference documentation.

Generally available: When sending private messages, Chat apps can now include interactive accessory widgets.

Generally available: You can now format text with Markdown, including lists and code blocks, in your Chat apps.

Developer Preview: The following Chat API methods support app authentication with administrator approval when called with chat.app.* authorization scopes:

• Get a Chat space event.
• List Chat space events.

Additionally, Chat apps can now call the following methods in the Google Workspace Events API using app authentication with administrator approval with chat.app.* authorization scopes:

• Subscribe to Chat space events
• Update or renew a subscription
• Reactivate a subscription

Generally available: Increased per-space quota limits for writing messages and reactions with the Chat API:

• When importing data to Google Chat, the per-space quota limit for writing messages with spaces.messages.create increases from 60 to 600 per minute.
• When writing reactions with spaces.messages.reactions.create, the per-space quota limit increases from 60 to 300 per minute.

To learn more, see the Chat API's per-space quotas.

Generally available: You can now design your Chat app to include a carousel, which is a layout that rotates and displays a list of cards in a slideshow format, with buttons navigating to the previous or next carousel card. For details, see Carousel.

You can now use annotations to create Deal Cards in the Promotions tab. To get started, see the overview of Deal Cards.

Developer Preview: The following Chat API methods support app authentication with administrator approval:

• Get a message as a Chat app with administrator approval using chat.app.messages.readonly scope.
• List messages with a Chat app with administrator approval using chat.app.messages.readonly scope.

Generally available: You can now call the Chat API to create messages that quote other messages, or to update messages to remove quotes. To learn more, see Quote a message.

Generally Available: Chat apps can now create (RPC, REST), update (RPC, REST), and get details about (RPC, REST) Chat space permission settings by calling the corresponding method in Chat API using app authentication with the https://www.googleapis.com/auth/chat.app.spaces or https://www.googleapis.com/auth/chat.app.spaces.create authentication scope, including creating announcement spaces.

Generally Available: The following Chat API methods support app authentication using a new type of authentication scope, https://www.googleapis.com/auth/chat.app.*:

• Create a named space as a Chat app with https://www.googleapis.com/auth/chat.app.spaces or https://www.googleapis.com/auth/chat.app.spaces.create.
• Update a space as a Chat app with https://www.googleapis.com/auth/chat.app.spaces.
• Delete a named space as a Chat app with https://www.googleapis.com/auth/chat.app.delete.
• Get details about a space as a Chat app with https://www.googleapis.com/auth/chat.app.spaces.
• Invite or add a user to a space as a Chat app with https://www.googleapis.com/auth/chat.app.memberships.
• Update a membership as a Chat app with https://www.googleapis.com/auth/chat.app.memberships.
• Remove a member from a space with https://www.googleapis.com/auth/chat.app.memberships.

To learn more, see Types of required authentication and Authenticate as a Chat app.

You can now read the metadata for Meet, Huddle, and Calendar chips using message annotations. Use the RichLinkMetadata object to read information about the chip.

Generally available: You can now build Google Chat apps as Google Workspace add-ons. For details, see Extend Google Chat.

Generally available: Create, update, and read Google Drive and People chips in Google Sheets API. To learn more, see Smart chips in the Sheets API documentation.

Developer Preview: Chat apps can now format text with markdown, including lists and code blocks.

For Google Workspace organizations that use hardware key encryption, the Gmail API supports using smart cards for client-side encryption (CSE). For details, see the reference documentation for CseIdentity and CseKeyPair resources.

Generally available: You can now call the Chat API to create, delete, and view custom emoji in organizations where creating custom emoji is enabled. You can now include or react with custom emoji in messages.

• Learn about including custom emoji in Chat messages
• Learn more about enabling custom emoji

You can now create and modify tables, and take basic actions on tables using the Sheets API.

• Learn more about creating tables using the Sheets API
• Learn about the Table object in the Sheets API

Reports API: User Logs Events now have logs for additional challenge types, such as Passkey, Device Prompt, SAML and more.

Learn more about Login Audit Activity Events. You can get these events using the activities.list method.

The Google Workspace Events API v1beta endpoint will be decommissioned for Google Chat and Google Meet events on April 30, 2025. To subscribe to Chat or Meet events, use the generally available v1 endpoint.

Generally Available: You can now call the Chat API to get or update a user's notification settings for a Chat space. For details, see the following guides:

• Get a user's space notification settings
• Update a user's space notification settings

Generally available: Chat apps can respond to quick commands. To use quick commands, users select the command from the message reply area in a Chat space. To learn more, see Respond to Google Chat app commands.

Google Chat API now supports mentioning users who haven't joined a Chat space or are members of a space that is in import mode when sending a message with user authentication. To learn how, see Mention users in a text message.

Generally available: When a user deletes a message sent by a Chat app, the DeletionType of the Chat API Message resource is set to SPACE_MEMBER. Previously, the DeletionType was set to CREATOR.

Reports API: Google Chat now supports the customerUsageReports.get() and userUsageReports.get() methods. Forty eight new metrics have been added to customerUsageReports and four new metrics have been added to userUsageReports.

Reports API: A new event type conversation_read has been added to Google Chat along with four new event parameters to activities.list, and activities.watch:

• conversation_ownership
• conversation_type
• message_type
• attachment_status

The full list of events and parameters supported in Chat audit activities can be found on the Chat Audit Activity Events page.

Developer Preview: Quick commands are a new way for users to invoke and interact with a Chat app directly without typing a slash command. For details, see Respond to quick commands as a Google Chat app.

Developer Preview: You can now design your Chat app to include a carousel, which is a layout that rotates and displays a list of cards in a slideshow format, with buttons navigating to the previous or next carousel card. For details, see Carousel.

Developer Preview: Chat apps can now create (RPC, REST), update (RPC, REST), and get details about (RPC, REST) Chat space permission settings by calling the corresponding method in Chat API using app authentication with the https://www.googleapis.com/auth/chat.app.spaces or https://www.googleapis.com/auth/chat.app.spaces.create authentication scope, including creating announcement spaces.

To learn more about Chat app authentication, see Types of required authentication and Authenticate as a Chat app.

Developer Preview: You can now build Google Chat apps as Google Workspace Add-ons. For details, see Extend Google Chat.

Chat apps now have 90 days to complete the import of data. Previously, Chat apps had 30 days. To learn more, see Import data to Google Chat.

Generally Available: If you're migrating to Google Chat from other messaging platforms, you can now create a group chat in import mode using the spaces.create method.

Developer Preview: You can now use a read-only scope (https://www.googleapis.com/auth/chat.customemojis.readonly) to get or list custom emoji.

Developer Preview: You can now call the Chat API to get or update a user's space notification settings. To learn more, see the spaceNotificationSetting reference documentation.

Generally Available: The following widgets are now available for building card-based user interfaces:

• Chip
• Overflow Menu
• Material Buttons
• Collapsible Text paragraph
• Customizable control button of collapsible Section

Chat apps can use these widgets in card messages, homepages, and dialogs. For examples, see Design an interactive card or dialog.

Developer Preview: When creating custom emoji is turned on for a Workspace organization, you can now call Chat API to manage custom emoji:

• Create custom emoji (RPC, REST)
• Delete custom emoji (RPC, REST)
• Get custom emoji (RPC, REST)
• List custom emoji (RPC, REST)

To learn more, see CustomEmoji (RPC, REST) in the Chat API documentation.

Generally available: You can now call the Chat API to create announcement spaces, and read and update the permission settings of a space. For more information, see the following reference documentation:

• PredefinedPermmissionSettings field for the Spaces resource
• PermissionSettings field for the Spaces resource

Developer Preview: The following Chat API methods support app authentication using a new type of authentication scope, https://www.googleapis.com/auth/chat.app.*:

• Create a named space as a Chat app with https://www.googleapis.com/auth/chat.app.spaces or https://www.googleapis.com/auth/chat.app.spaces.create.
• Update a space as a Chat app with https://www.googleapis.com/auth/chat.app.spaces.
• Delete a named space as a Chat app with https://www.googleapis.com/auth/chat.app.delete.
• Get details about a space as a Chat app with https://www.googleapis.com/auth/chat.app.spaces.
• Invite or add a user to a space as a Chat app with https://www.googleapis.com/auth/chat.app.memberships.
• Update a membership as a Chat app with https://www.googleapis.com/auth/chat.app.memberships.
• Remove a member from a space with https://www.googleapis.com/auth/chat.app.memberships.

To learn more, see Types of required authentication and Authenticate as a Chat app.

Generally Available: The chatSpaceLinkData object has been added to the RichLinkMetaData field of the spaces.messages resource. This lets you add a smart chip to your message that points to a Chat space in any field that supports formatted text.

Generally Available: Google Workspace administrators can now call the Google Chat API to manage and search Google Chat spaces across their organization. This functionality lets them manage spaces at scale and automate common or repeatable tasks, such as the following:

• Search spaces based on specified criteria
• List members of a space
• Add members to and remove members from a space
• Get details about a member and a space
• Update or delete a space
• Update a user's membership

For more information about managing spaces, read the documentation at Manage Google Chat spaces as a Google Workspace administrator.

For more information about searching spaces, read the documentation at Search for and manage Google Chat spaces for your Google Workspace organization.

Developer Preview: If you're migrating to Google Chat from other messaging platforms, you can now create a group chat in import mode using the spaces.create method.

Generally Available: You can now call Chat API using Cloud Client Libraries in addition to the already available Google API Client Libraries.

Benefits of Cloud Client Libraries include:

• Idiomatic code that follows your preferred language's natural conventions and styles.
• Consistent style across client libraries.
• Handling the low-level details of server communication, including authentication, pagination, long-running operations, streams, and retries.
• Installable using package management tools like npm and pip.
• Improved performance in some cases, thanks to gRPC.

Additionally, our Chat API reference documentation now features a RPC reference arranged by services and their methods in addition to our existing REST reference arranged by resource hierarchies and their methods.

To learn more, see Install client libraries.

Developer Preview: The following widgets are now available for building card-based user interfaces:

• Chip
• Overflow Menu
• Material Buttons
• Collapsible Text paragraph
• Customizable control button of collapsible Section

Chat apps can use these widgets in card messages, homepages, and dialogs. For examples, see Design an interactive card or dialog.

Generally Available: You can now import a space from other messaging platforms, and allow external users to join that Chat space. For more information, see the externalUserAllowed option.

Generally Available: When building Chat apps using Google Cloud Functions, Cloud Run, or any system that supports authentication via ID tokens, you can now Authenticate requests using Cloud Functions or Cloud Run or Authenticate requests with an App URL ID Token to verify that the requests to your app came from Google Chat.

Generally Available: You can now call the Chat API to Make a Google Chat space discoverable to specific users in a Google Workspace organization using the accessSettings field on the Space resource. You can read the URI of the space using the spaceUri field.

(Generally Available): Dialogflow CX Chat apps can open dialogs and receive data inputted by users in card messages and dialogs.

(Developer Preview): You can now use the Chat API to create announcement spaces, plus read and update the permission settings of a space. For more information, see the PredefinedPermissionSettings and PermissionSettings fields.

(Generally Available): You can now add a Google Group to a Chat space using the spaces.members.create method or the spaces.setup method. You can remove a Google Group from a space using the spaces.members.delete method.

Google Chat apps can now create a subscription to receive events for all Chat spaces where the user is a member. To target all spaces for a user, set the subscription's targetResource field to //chat.googleapis.com/spaces/-. To learn more, see Subscribe to Google Chat events.

(Developer Preview): If you're a domain administrator or a delegated administrator, you can now include the useAdminAccess parameter when you call the Chat API with your administrator privileges with the following methods to manage Chat spaces and memberships in your Workspace organization:

• Get a space
• Update a space
• Get a member
• Update a member

To learn more, see Authenticate and authorize using administrator privileges.

(Developer Preview): If you're a domain administrator or a delegated administrator, you can now include the useAdminAccess parameter when you call the Chat API with your administrator privileges to manage Chat spaces and memberships in your organization. The following API methods are supported:

• Search spaces
• Delete spaces
• List memberships
• Create memberships
• Delete memberships

To learn more, see Authenticate and authorize using administrator privileges.

(Developer Preview): Dialogflow CX Chat apps can open dialogs and receive data inputted by users in card messages and dialogs.

(Generally available): You can now get and update a user's read state in a space, and get a user's read state in a message thread. User read states are singleton resources that represent details about a specified user's last read message.

The users.spaces resource represents a user's read state in a space. The users.spaces.threads resource represents a user's read state in a message thread.

User read states support the following methods:

• Get space read state to return details about a user's read state within a space.

• Update space read state to update a user's read state within a space.

• Get thread read state to return details about a user's read state within a thread.

(Generally Available): Build a Chat app that understands and responds with natural language using a direct integration between Dialogflow CX and Google Chat API. To learn how, see Build a Dialogflow CX Google Chat app.

(Generally available): Your Chat app can now send an app home card message to a user. This message is a customizable card message that a Chat app sends to a user when they open a direct message with the Chat app.

For details, see Send an app home card message for a Google Chat app.

(Generally Available): Google Chat apps now support Google Apps Script's Card Service. If you've built your Chat app using Apps Script, you can use Card Service to build user interfaces such as card messages and dialogs. For more information, see the Card Service reference documentation.

(Generally available): You can now update a human user's membership in a Chat space to change their role between regular member and space manager using the spaces.members.patch method. To learn more, see Update a user's membership in a Google Chat space.

(Developer Preview): You can now import a space from other messaging platforms, and allow external users to join that space. For more information, see the externalUserAllowed option.

(Generally available): Google Chat apps can get, list, and subscribe to events. To receive events, you can do the following:

• Use the get() and list() methods on the spaces.spaceEvents resource of the Google Chat API.
• Create subscriptions to events about users and spaces using Google Workspace Events API.

To learn more, see Work with events from Google Chat.

Events about deleted messages are now supported (Event type: google.workspace.chat.message.v1.deleted).

(Generally available): Google Chat apps can now use accessory widgets, which are interactive widgets that appear at the bottom of a message. For details, see Send a message.

(Developer Preview): You can now get or list events about a Google Chat space. For example, you can track periodic resource changes, such as monthly reports of new or changed members in a space, or fetch events that are missing from subscriptions using the Google Workspace Events API.

The following types of space events are supported:

• A message is created or updated.
• A member is added, updated, or removed.
• The space is updated.

For more information, see the following:

• Work with events from Google Chat.
• Get details about an event in a space.
• List events from a space.

(Developer Preview): Build a Chat app that understands and responds with natural language using a direct integration between Dialogflow CX and Google Chat API. To learn how, see Build a Dialogflow CX Google Chat app.

(Generally available): The formattedText field on the Message resource includes the markup syntax for bulleted list text formatting. For more information, see Format a text message.

(Developer Preview): Google Chat apps now support Google Apps Script's Card Service. If you've built your Chat app using Apps Script, you can use Card Service to build user interfaces such as card messages and dialogs. For more information, see the Card Service reference documentation.

Reports API: The event returned in the activities.watch method payload is now filtered to the event name set in the filter. Before this change, multiple events were returned in the payload even if the customer filtered to a specific event.

(Developer Preview): You can make a Chat space discoverable to a target audience instead of inviting users individually.

(Developer Preview): Chat apps can now subscribe to events about users. The following event types are supported:

• New memberships
• Updated memberships
• Deleted memberships
• Multiple memberships have changed

For details, see Subscribe to Google Chat events in the Google Workspace Events API documentation.

(Generally available): You can now migrate historical memberships when you import data into Google Chat.

(Generally available): Import data from your other messaging platforms into Google Chat. You can import existing messages, attachments, reactions, memberships, and space entities from your other messaging platforms to corresponding Chat API resources. You can import this data by creating Chat spaces in import mode and importing data into those spaces.

(Developer Preview): Chat apps can now add interactive buttons to the bottom of messages. For details, see the reference documentation.

Chat apps can now send messages privately in spaces with multiple people. For details, see Send private messages to Google Chat users.

Directory API

(Generally available): You can now change the device status of ChromeOS devices in batch. For more information, refer to Deprovisioning or disabling Chrome devices.

Directory API: The action method of the chromeosdevices resource is deprecated. Instead, use the batchChangeStatus method in the customer.devices.chromeos resource.

We've published a comprehensive tutorial and code sample showing how to build a Chat app using generative AI and a database, Manage projects with Google Chat, Vertex AI, and Firestore.

(Generally available): The Card Builder Tool is now available to help you design and preview card messages in Google Chat apps.

The Google Chat API spaces.list() method now supports app authentication for query filters.

Developer Preview: You can now get and update a user's read state in a space, and get a user's read state in a message thread. User read states are singleton resources that represent details about a specified user's last read message.

The users.spaces resource represents a user's read state in a space. The users.spaces.threads resource represents a user's read state in a message thread.

User read states support the following methods:

• Get space read state to return details about a user's read state within a space.

• Update space read state to update a user's read state within a space.

• Get thread read state to return details about a user's read state within a thread.

(Generally available): You can now retrieve Google Groups that are members of a Google Chat space using ListMemberships (with the showGroups option) and GetMembership. If you try to add a member to a Chat space while this member is already part of a Google Group in the same space, it triggers an already exists error (HTTP status code 409).

(Developer Preview): Your Chat app can now send an app home card message to a user. This message is a customizable card message that a Chat app sends to a user when they open a direct message with the Chat app.

(Generally available): Google Material Design 3 styles, including icons, are available for cards in Chat apps.

(Generally available): You can now call the Chat API from Apps Script with the Advanced Chat Service. To learn how, see Advanced Chat Service in the Apps Script reference documentation.

We've also updated the Apps Script code samples to use the Advanced Chat Service in the following Chat API developer guides:

• Authenticate as an app
• Authenticate as a user
• Try it - Respond to Incidents

Users can now install Google Chat apps from app listing pages on the Google Workspace Marketplace. For details, see Publish Google Chat apps.

(Developer Preview): Google Chat apps can now subscribe to the following types of events about message reactions:

• New reactions
• Removed reactions
• Multiple reactions have changed.

For details, see Subscribe to Google Chat events.

(Developer Preview): You can now migrate historical memberships when you import data into Google Chat.

(Generally available): Multiselect menus for cards and dialogs are now generally available. Multiselect menus let users select Google Workspace users and spaces, or select items from external data sources. For details, see Selection input.

(Developer Preview): Google Chat apps can now monitor and receive events about Google Chat spaces. The following event types are supported:

• New messages
• Updated messages
• New members
• Updated members
• Removed members
• Updated space
• Deleted space

To receive events, Chat apps create subscriptions using the Google Workspace Events API. To learn more, see the Google Workspace Events API overview.

You can now use the formattedText field to view the text formatting sent in a message.

Developer Preview: You can now update a human user's membership in a Chat space. For example, you can use the spaces.members.patch method to update membership roles from member to manager and from manager to member.

Google Chat users outside of Google Workspace organizations can now install and use public Google Chat apps. To learn about how users discover and use Chat apps, see Publish Google Chat apps.

Google Chat apps that authenticate as a user can now reference users with their email address. The following Chat API methods support using email addresses to reference users:

• Set up a space
• Find a direct message
• Create a membership
• Get a membership
• Delete a membership

Chat apps can also use email addresses to @mention users. To learn more, see Mention users in a message.

You can now specify no divider between card sections.

Multiselect menus are now available in Developer Preview. Multiselect menus help users input static and dynamic data for Google Chat apps. To learn more, see the Selection input widget documentation.

Developer Preview: Available as part of the Google Workspace Developer Preview Program, which grants early access to certain features.

Import data from your other messaging platforms into Google Chat. You can import existing messages, attachments, reactions, memberships, and space entities from your other messaging platforms to corresponding Chat API resources. You can import this data by creating Chat spaces in import mode and importing data into those spaces.

You can authenticate and authorize users' credentials to access the Chat API by using OAuth 2.0. Authenticating and authorizing with user credentials lets Chat apps access user data and perform operations on the authenticated user's behalf. When an app performs an action with user authentication (such as creating a space), Google Chat might display an attribution message that tells users the name of the app that performed the action for the user who authorized it.

Oauth 2.0 scopes are available for you to request and your users to consent to.

Quotas and limits are applied to the Chat API.

The following methods are available:

• Create a message
• Delete a message
• Get a message
• Update a message
• List messages
• Create a reaction
• Delete a reaction
• List reactions
• Create a membership
• Delete a membership
• Get a membership
• List memberships
• Create a space
• Delete a space
• Get a space
• Find a direct message
• List spaces
• Update a space
• Set up a space (create and populate)
• Download media
• Upload media

You can now design your Chat app to include checkboxes, radio buttons, switches, or a dropdown menu in your Chat app. For more information, see SelectionInput widget.

Chat apps can now receive and respond to user-submitted information in cards and dialogs. For more information, see Process information inputted by users.

Buttons can now include text and an icon. Previously, only an icon or only text was allowed in buttons.

Reseller API: The maximum queries per day (QPD) of 10,000 no longer applies.

Cards v1 is deprecated. Instead, use Cards v2.

On the web, Google Chat cards now match Google Material Design. The Material Design cards feature aesthetic enhancements that improve usability and render faster.

Developer Preview: Available as part of the Google Workspace Developer Preview Program, which grants early access to certain features.

On mobile devices, Google Chat cards now match Google Material Design. The Material Design cards feature aesthetic enhancements that improve usability and render faster.

Announcement The Google Keep API is now available for enterprise administrators.

Google Sheets API v3 is turned down. For more information, see Migrate from Sheets API v3.

All Team Drive-related fields are removed from the Vault API. Although these fields are marked as deprecated and will continue to be available until then, we strongly recommend that you update your apps and your API configuration to reference the new fields as soon as possible. If you do not migrate your apps by June 1, 2020, they might stop functioning.

If you have additional questions or need assistance, please visit our support page.

Reports API: A new parameter member_type has been added to the Enterprise Groups activity report. Valid member types include user, group, service account, and other.

The messages.import method uses a more performant backend implementation. The new version is API-compatible with the previous implementation and all clients automatically started using the new behavior as of a few weeks ago. The new backend supports parallel message.import calls efficiently and clients can now import messages in parallel for a user to achieve higher migration throughput. The quota cost of the message.import method has been decreased to reflect the new performance.

Reports API: The customer usage reports for App Maker and Apps Script are deprecated and will eventually be removed from the API.

The "Team Drive" feature of Google Drive has been renamed to "shared drive". Consequently, the Vault API is changing as follows:

• Shared drive-related request and response fields have replaced Team Drive in:

  • DriveOptions
  • HeldDriveQuery
  • SearchMethod

• SharedDriveInfo has replaced TeamDriveInfo.

Hangouts Chat and Google Meet together are the next generation of Hangouts. Later this year they will replace the original version (classic Hangouts) in Google Workspace.

Vault admins must take action to prepare for this migration. Learn More.

Reports API: The community_name parameter for the Google+ communities report is now available only for communities inside your organization.

Alert Center API: V1beta1 is now available.

Reports API: The availability of past data for the Entities Usage Report has been changed to 30 days.

Reports API: Fixed an issue where some Entities Usage Parameters were under-reported for some Google+ communities. This has been corrected as of May 25, 2018.

Reports API: We have created the Entities Usage Report to generate reports on entities used by your account's users. The API currently supports reporting for Google+ communities.

Reports API: Nine new parameters have been added to the Google+ customer usage report. The new parameters are:

• num_communities
• num_communities_public
• num_communities_private
• num_communuties_organization_wide
• num_communities_organization_private
• num_collections
• num_collections_public
• num_collections_organization_wide
• num_collections_organization_private

In addition, the Google+ user usage report was created with seven metrics:

• num_shares
• num_plusones
• num_plusones_received
• num_replies
• num_replies_received
• num_reshares
• num_reshares_received

Reports API: We have added the App Maker and Apps Script customer usage reports to the customerUsageReports.get method. These new reports allow you to view information about App Maker and Apps Script usage in your domains.

Deprecated Review Action, which sunsets on July 15th, 2017.

Reports API: Google Docs customer and usage reports are being replaced by Google Drive customer and usage metrics. See details in Update your Drive and Docs Metrics.

Reports API: Six new parameters have been added to the Google+ customer usage report. The new parameters are:

• num_new_users
• num_shares
• num_reshares
• num_plusones
• num_replies
• num_stream_items_read

The history.list method supports filtering history records by type.

The messages.batchModify method lets you modify labels on multiple messages by message IDs, in a single batch operation.

The Gmail API supports a gmail.metadata scope. This scope gives developers access to a user's mailbox including history records, labels, and email headers, but not email body's or attachments.

New endpoints for managing mail settings:

• Send-as aliases and Signatures
• Forwarding
• Filters
• Vacation Responder
• POP and IMAP

The q request parameter for the drafts.list method restricts results to the messages matching the specified query.

Google Sheets API v4 is now available. For more information, see Introducing the Google Sheets API v4.

The Google Cloud Search API is now available for enterprise administrators.

The Google Slides API is now generally available.

The messages.batchDelete method lets you delete multiple messages, by message IDs, in a single batch operation.

The drafts.list method has an includeSpamTrash option, which determines if the response should include drafts with the SPAM or TRASHlabel applied. The default is currently set to true for this option.

To determine the full state of an email before and after a change, the history.list method returns all current Message.labelIds as part of the response in messagesAdded, messagesDeleted, labelsAdded, and labelsRemoved.

Added a Message.internalDate field that exposes the message's creation timestamp in the mailbox.

You can now send push notifications on mailbox updates, providing real-time server notification without the need for constant polling. With Cloud Pub/Sub, you can now use webhooks—for example, to receive callbacks when updates happen. Additionally, you can filter these notifications to specific Gmail labels.

New scopes for labels and inserting messages to better protect users and accommodate apps that don't need full mailbox data access:

• https://www.googleapis.com/auth/gmail.insert: Allows the messages.insert and messages.import methods only.
• https://www.googleapis.com/auth/gmail.labels: Allows all label operations.

The messages.insert method now supports the deleted request parameter and lets you set SENT and DRAFT labels.

The history.list method now provides details of the change type in each history record. For example, using the messagesAdded, messagesDeleted, labelsAdded, or labelsDeleted enums, it's possible to easily tell how a message was changed and typically avoids the need for additional calls to synchronize your client.

The messages.import method now supports the following parameters to better support Email Migration use cases:

• neverMarkSpam
• processForCalendar
• deleted

Reports API: We have added the Mobile Device customer usage report to the customerUsageReports.get method. This new report allows you to view information about mobile device usage in your domains.

The default behavior no longer automatically adds INBOX and UNREAD labels to messages.import emails. When message.labelIds isn't specified, imported mail is only visible in All Mail. If you want INBOX or UNREAD labels applied, specify them in the message.labelIds field.

You can now specify message.labelIds on messages.import requests to automatically apply the given labels to the message.

Increased the default per-user quotas from 25 units/user/second to 250 units/user/second and adjusted some method costs slightly.

Reports API: We have added the Google Calendar audit report to the activities.list method. This new report allows you to view information about changes to calendars and calendar events for users in your domain.

Reports API: We have added the Google Sites customer usage report to the customerUsageReports.get method. This new report allows you to view information about Google Sites usage in your domains.

Reports API: We have added the OAuth Token Audit reporting application to the activities.list method. This new report allows you to view information about third party websites and applications that users in your domains have granted access to.

Reseller API: New transferToDirect deletionType.

Reseller API: New billingMethod field.

Reports API: Added the following parameters to the Gmail customer usage report:

• num_inbound_delivered_emails
• num_inbound_rerouted_emails
• num_inbound_rejected_emails
• num_inbound_spam_emails
• num_inbound_non_spam_emails
• num_inbound_encrypted_emails
• num_inbound_unencrypted_emails
• num_outbound_delivered_emails
• num_outbound_rerouted_emails
• num_outbound_rejected_emails
• num_outbound_encrypted_emails
• num_outbound_unencrypted_emails

Reports API: We have added the ChromeOS Devices customer usage report to the customerUsageReports.get method. This new report allows you to view information about ChromeOS device usage in your domains.

You can now specify the return format for the threads.get method. The available formats are full, metadata, and minimal, similar to the messages.get method. The raw format isn't allowed for the threads.get to avoid unexpectedly large amounts of data being returned.

The getProfile method provides mailbox-wide information like current history ID and total message and thread counts.

Added a new IMPORTANT label to match functionality with the Gmail UI.

Added new fields to the Labels resource to simplify counting how many messages have a given label applied:

• messagesTotal
• messagesUnread
• threadsTotal
• threadsUnread

The messages.insert method defaults to using receivedTime and the messages.import method defaults to using dateHeader.

When you use the messages.get method, you can request the metadata return format to return only the email headers and metadata such as identifiers and labels.

You can specify the internalDateSource for both the messages.insert and messages.import methods.

Reports API: The maximum time limit for usage reports has been increased from 180 days to 450 days. Because this change will take time to populate in our data, the full 450 day history will be available on May 30, 2015 with an earliest available record date of March 6, 2014.

Reports API: A new view event has been added to the Drive activity report.

Directory API: The Chromeosdevices resource has the following fields:

• recentUsers
• Device's ethernetMacAddress

Directory API: The following fields have been added to the Mobiledevices resource:

• serialNumber
• imei
• meid
• wifiMacAddress
• networkOperator
• defaultLanguage
• managedAccountIsOnOwnerProfile
• deviceCompromisedStatus
• buildNumber
• kernelVersion
• basebandVersion

Reseller API: Deprecated readonly scope.

Reseller API: new licensedNumberOfSeats field in the Subscriptions resource.

Quota costs for all methods in the API have been reduced by a factor of 10. For example, if a method previously cost 150 quota units, it now costs 15. For a complete list of API method costs, see the per-method quota usage chart.

The Gmail API is publicly available!

Reports API: The Drive activity report is now available. This new report provides insight about Drive activity and how your account's users manage, modify, and share their Google Drive documents. This report is available only for G Suite Business customers and replaces the Google Docs activity report. The Google Docs activity report is now deprecated and will cease functioning on January 31, 2015.

Reports API: Both customer and user Gmail reports now include default values. For example, if a user sends no email, the num_emails_sent parameter is returned as 0. Previously, if there was no data for a field, that field was omitted from the report.

Reports API: Includes usage statistics from suspended users in Customers Usage reports.

Reports API: A change has been made to how parameters with no data are returned by the API. Previously, if there was no data for a parameter, it would be absent from the report. For example, the Gmail user usage report would not include the num_emails_sent field in the response if a user didn't send any emails on the report date. The API now returns these parameters with a default of 0 for integers and false for boolean values.

Reports API: A new num_users_2sv_not_enrolled_but_enforced parameter has been added to the customer accounts usage report. This new parameter indicates the number of domain users that have 2-step verification enforced but have not enrolled.

Reports API: Added two new login_failure_type values to the Login Audit events: login_failure_account_disabled and login_failure_unknown.

Reports API: Fixed an issue that caused filters to use case-sensitive comparisons. All filters are now case-insensitive.

Reports API: Fixed an issue that caused filters to be ignored on queries for single users and always return a single record. After the fix, queries for single users that also include filters will return no result if the user does not match the filter criteria.

Reports API: Added the following fields to the Customer Account Usage and Users Account Usage reports:

• Customer Accounts
  • num_authorized_apps
  • authorized_apps
  • drive_used_quota_in_mb
  • gmail_used_quota_in_mb
  • gplus_photos_used_quota_in_mb
  • total_quota_in_mb
  • used_quota_in_mb
  • apps_total_licenses
  • apps_used_licenses
  • vault_total_licenses
  • coordinate_total_licenses
• User Accounts
  • num_authorized_apps
  • drive_used_quota_in_mb
  • gmail_used_quota_in_mb
  • gplus_photos_used_quota_in_mb
  • total_quota_in_mb
  • used_quota_in_mb
  • used_quota_in_percentage

Reports API: Fixed an issue that caused certain statistics on numbers of active users to include one extra day. Some domains might notice a decrease in the number of reported active users for reports after February 24, 2014. The affected fields are:

• Accounts
  • num_1day_logins
  • num_7day_logins
  • num_30day_logins
• Google Calendar
  • num_1day_active_users
  • num_7day_active_users
• Google Docs
  • num_1day_active_users
  • num_7day_active_users
  • num_30day_active_users
• Gmail
  • num_1day_active_users
  • num_7day_active_users
  • num_30day_active_users
• Google+
  • num_1day_active_users
  • num_7day_active_users

Directory API: The users.update method behavior has been slightly changed to accommodate delegated administrator access to the Directory API. Only fields the authenticated user has access to can be specified in the request and only fields that have been updated are included in the response.

Reports API: Suspended users are now included in the statistics for Google Docs reports. Some domains might notice an increase in the number of reported documents. The following parameters have been added to the User's usage report:

• Accounts: used_quota_in_percentage
• Docs
  • num_docs_externally_visible
  • num_docs_internally_visible
• Gmail: num_emails_exchanged

Directory API: Structured search queries for users are available by using the users.list method.

Reports API: Added push notifications for changes to the Activities resource. This is exposed in the API as two new methods, activities.watch and channels.stop, to start and stop receiving notifications.

Directory API: Supports push notifications for changes to users and aliases. You no longer need to poll resources to detect changes. You can create a notification channel using the users.watch and users.aliases.watch methods. You can stop receiving notifications with the channels.stop method.

Reports API: Added support for resellers to retrieve usage reports and audit information for a specific customer. This is exposed in the API as a new customerId parameter for the activities.list, customerUsageReports.get, and userUsageReport.get methods.

The Review Action is out of preview, and now available to all users.

The Schema Validator tool in Testing Your Schemas has been replaced with the new Email Markup Tester.

Reseller API: To retrieve all transferable subscriptions for a customer, use the customer's customerId and the customerAuthToken. For more information, see Retrieve all transferable subscriptions for a customer.

Reseller API: The API can retrieve the full account settings of one of your resold customers or the customerId and customerName of a standalone Google customer or a customer managed by another reseller.

Reseller API: To retrieve all of a customer's subscriptions, use the customer's customerId parameter. For more information, see Retrieve & update a subscription.

Reseller API: When retrieving all transferable subscriptions for a customer, the response contains a subscription's transferInfo property with the tranferabilityExpirationTime and minimumTransferSeats attributes.`

Reseller API: The customer resource's resourceUiUrl URL to customer's Admin console dashboard. The read-only URL is generated by the API service. This is used if your client application requires the customer to complete a task in the Admin console.

It is now possible to use schemas to define Orders, Parcel Deliveries, and the TrackAction to let users track packages being delivered.

The RSVP Action is now enabled for all emails sent by Google Calendar.

Reseller API: A subscription's optional status property can be ACTIVE, CANCELLED, PENDING, or SUSPENDED. For more information, see the subscriptions resource.

Reseller API: The customerId parameter is either the primary domain name or the unique identifier of a customer. We recommend using the unique identifier or the customer value.

Reseller API: The maximum queries per day (QPD) has been increased to 10,000. For more information, see Usage limits.

Reseller API: A Vault subscription is no longer limited to accounts created after August 1.

Directory API: The differences between the Directory API and the deprecated Provisioning API (v2):

• Account's domain name
  • The Directory API user's primaryEmail property holds the account's primary domain name.
  • The Provisioning API request URL's domain property holds the account's primary domain name.
• Administrator
  • The Directory API isAdmin property has a boolean true, false value. The isAdmin property can only be edited in the Make a user an administrator operation. If edited in the Create a user account or Update a user account operations, the edit is ignored.
  • The Provisioning API isAdmin property has a boolean true, false value. The property can be edited when the user is created or updated.
• A customerId unique identifier
  • The Directory API returns a customerId unique identifier property when a user is retrieved for an account with a single or multiple organizational units.
  • The Provisioning API returns a customerId for accounts with an organizational unit hierarchy.
• Deleted user list
  • The Directory API returns a list of users deleted from the account or a subdomain within the span of the last 20 days.
  • The Provisioning API doesn't support this feature.
• Disk space
  • Not applicable in this version of the Directory API.
  • The Provisioning API apps:quota that sets the user's disk space quota is no longer available. Setting a customer quota, different than 25600MB, has no effect.
• Devices
  • The Directory API's Google Chrome devices and mobile devices support the management of retrieving, adding, updating, and deleting your account's various devices.
  • The Provisioning API doesn't support these features.
• Email aliases outside of an account
  • The Directory API users and groups support listing non-editable alias email addresses that are outside of the account. These are functioning email addresses used by a user or a group on a regular basis.
  • The Provisioning API doesn't support this feature.
• Group alias
  • The Directory API creates, lists, and deletes a group's aliases.
  • The Provisioning API supports managing groups but doesn't include group aliases.
• Hash function
  • The Directory API hashFunction property holds the hash format of the password property. The values can be set to either SHA-1, MD5, or CRYPT hash formats.
  • The Provisioning API hashFunctionName attribute is a part of the password tag. The values can be either SHA-1, MD5, or CRYPT hash formats.
• Organizational units
  • The Directory API uses the orgUnitPath property when setting a new user.
  • The Provisioning API has two steps for creating a user in an organizational unit. First the user account is created and then the user is assigned to an organizational unit.
• Suspend a user
  • The Directory API suspends a user's account either when creating or updating the user's account using the suspended property. The reason for the suspension is also retained by the API in the suspensionReason property.
  • The Provisioning API uses the operation that suspends a user's account.
• Undelete a user
  • The Directory API undeletes a previously deleted user account within 20 days of the deletion.
  • The Provisioning API restores a suspended user account to an active state within the suspension period.
• User aliases
  • The Directory API supports user alias for a single or multiple domain account. A user alias is an alternate email address that uses the same mailbox used by the user's primary email address. A user's alias can be associated with a different account domain than that domain used by the user's primary email address. The account can have single or multiple domains. The Directory API doesn't use the concept of a 'nickname' for a single domain.
  • The Provisioning API manages a single domain account's nicknames, and, in the case of an account with multiple domains, the Provisioning API supports user aliases.
• User list's search, sorting, and list order
  • The Directory API can search for users by primary email address, given name, or family name. In addition, the Directory API can return lists of a domain's users sorted by the user's primary email address, given name, or family name. And, you have the option to list these results in ascending or descending order.
  • The Provisioning API doesn't support these features.