google-api-python-client 2.176.0__py3-none-any.whl → 2.178.0__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (169) hide show
  1. {google_api_python_client-2.176.0.dist-info → google_api_python_client-2.178.0.dist-info}/METADATA +1 -1
  2. {google_api_python_client-2.176.0.dist-info → google_api_python_client-2.178.0.dist-info}/RECORD +169 -167
  3. googleapiclient/discovery_cache/documents/accessapproval.v1.json +7 -1
  4. googleapiclient/discovery_cache/documents/accesscontextmanager.v1.json +2 -2
  5. googleapiclient/discovery_cache/documents/admin.datatransfer_v1.json +4 -4
  6. googleapiclient/discovery_cache/documents/admin.datatransferv1.json +4 -4
  7. googleapiclient/discovery_cache/documents/admin.directory_v1.json +86 -86
  8. googleapiclient/discovery_cache/documents/admin.directoryv1.json +86 -86
  9. googleapiclient/discovery_cache/documents/admin.reports_v1.json +31 -3
  10. googleapiclient/discovery_cache/documents/admin.reportsv1.json +31 -3
  11. googleapiclient/discovery_cache/documents/adsenseplatform.v1alpha.json +4 -4
  12. googleapiclient/discovery_cache/documents/aiplatform.v1.json +379 -31
  13. googleapiclient/discovery_cache/documents/aiplatform.v1beta1.json +717 -47
  14. googleapiclient/discovery_cache/documents/alloydb.v1.json +144 -9
  15. googleapiclient/discovery_cache/documents/alloydb.v1alpha.json +144 -9
  16. googleapiclient/discovery_cache/documents/alloydb.v1beta.json +144 -9
  17. googleapiclient/discovery_cache/documents/analyticsadmin.v1alpha.json +46 -227
  18. googleapiclient/discovery_cache/documents/androidenterprise.v1.json +30 -1
  19. googleapiclient/discovery_cache/documents/androidmanagement.v1.json +3 -3
  20. googleapiclient/discovery_cache/documents/androidpublisher.v3.json +2136 -300
  21. googleapiclient/discovery_cache/documents/apigee.v1.json +6 -6
  22. googleapiclient/discovery_cache/documents/apihub.v1.json +535 -7
  23. googleapiclient/discovery_cache/documents/apphub.v1alpha.json +1 -68
  24. googleapiclient/discovery_cache/documents/artifactregistry.v1.json +7 -7
  25. googleapiclient/discovery_cache/documents/artifactregistry.v1beta1.json +6 -6
  26. googleapiclient/discovery_cache/documents/artifactregistry.v1beta2.json +6 -6
  27. googleapiclient/discovery_cache/documents/backupdr.v1.json +65 -21
  28. googleapiclient/discovery_cache/documents/batch.v1.json +13 -7
  29. googleapiclient/discovery_cache/documents/beyondcorp.v1.json +61 -9
  30. googleapiclient/discovery_cache/documents/beyondcorp.v1alpha.json +61 -9
  31. googleapiclient/discovery_cache/documents/biglake.v1.json +1 -1
  32. googleapiclient/discovery_cache/documents/bigquery.v2.json +73 -7
  33. googleapiclient/discovery_cache/documents/bigtableadmin.v2.json +56 -1
  34. googleapiclient/discovery_cache/documents/chat.v1.json +105 -31
  35. googleapiclient/discovery_cache/documents/chromemanagement.v1.json +325 -6
  36. googleapiclient/discovery_cache/documents/civicinfo.v2.json +7 -1
  37. googleapiclient/discovery_cache/documents/cloudasset.v1.json +31 -1
  38. googleapiclient/discovery_cache/documents/cloudbilling.v1beta.json +9 -1168
  39. googleapiclient/discovery_cache/documents/cloudbuild.v1.json +2 -2
  40. googleapiclient/discovery_cache/documents/cloudbuild.v2.json +1 -26
  41. googleapiclient/discovery_cache/documents/compute.alpha.json +1044 -105
  42. googleapiclient/discovery_cache/documents/compute.beta.json +416 -85
  43. googleapiclient/discovery_cache/documents/compute.v1.json +262 -26
  44. googleapiclient/discovery_cache/documents/connectors.v1.json +29 -1
  45. googleapiclient/discovery_cache/documents/contactcenteraiplatform.v1alpha1.json +6 -1
  46. googleapiclient/discovery_cache/documents/contactcenterinsights.v1.json +73 -9
  47. googleapiclient/discovery_cache/documents/container.v1.json +257 -3
  48. googleapiclient/discovery_cache/documents/container.v1beta1.json +258 -14
  49. googleapiclient/discovery_cache/documents/containeranalysis.v1.json +2 -2
  50. googleapiclient/discovery_cache/documents/containeranalysis.v1alpha1.json +2 -2
  51. googleapiclient/discovery_cache/documents/containeranalysis.v1beta1.json +2 -2
  52. googleapiclient/discovery_cache/documents/content.v2.1.json +2 -2
  53. googleapiclient/discovery_cache/documents/datacatalog.v1.json +1 -2
  54. googleapiclient/discovery_cache/documents/dataflow.v1b3.json +43 -36
  55. googleapiclient/discovery_cache/documents/dataform.v1beta1.json +35 -1
  56. googleapiclient/discovery_cache/documents/datalineage.v1.json +6 -1
  57. googleapiclient/discovery_cache/documents/dataplex.v1.json +214 -30
  58. googleapiclient/discovery_cache/documents/dataportability.v1.json +1 -10
  59. googleapiclient/discovery_cache/documents/dataportability.v1beta.json +1 -10
  60. googleapiclient/discovery_cache/documents/datastream.v1.json +63 -1
  61. googleapiclient/discovery_cache/documents/developerconnect.v1.json +2 -2
  62. googleapiclient/discovery_cache/documents/dfareporting.v4.json +1210 -70
  63. googleapiclient/discovery_cache/documents/dialogflow.v2.json +286 -1
  64. googleapiclient/discovery_cache/documents/discoveryengine.v1.json +1715 -185
  65. googleapiclient/discovery_cache/documents/discoveryengine.v1alpha.json +1488 -62
  66. googleapiclient/discovery_cache/documents/discoveryengine.v1beta.json +1377 -244
  67. googleapiclient/discovery_cache/documents/displayvideo.v2.json +1376 -213
  68. googleapiclient/discovery_cache/documents/displayvideo.v3.json +27 -4
  69. googleapiclient/discovery_cache/documents/displayvideo.v4.json +1377 -202
  70. googleapiclient/discovery_cache/documents/dlp.v2.json +33 -12
  71. googleapiclient/discovery_cache/documents/documentai.v1.json +15 -8
  72. googleapiclient/discovery_cache/documents/documentai.v1beta3.json +15 -8
  73. googleapiclient/discovery_cache/documents/drive.v3.json +3 -109
  74. googleapiclient/discovery_cache/documents/fcm.v1.json +3 -3
  75. googleapiclient/discovery_cache/documents/file.v1.json +7 -1
  76. googleapiclient/discovery_cache/documents/file.v1beta1.json +7 -1
  77. googleapiclient/discovery_cache/documents/firebaseapphosting.v1beta.json +5 -1
  78. googleapiclient/discovery_cache/documents/firebasedataconnect.v1.json +6 -2
  79. googleapiclient/discovery_cache/documents/firebasedataconnect.v1beta.json +6 -2
  80. googleapiclient/discovery_cache/documents/firebaseml.v2beta.json +145 -27
  81. googleapiclient/discovery_cache/documents/gkebackup.v1.json +28 -1
  82. googleapiclient/discovery_cache/documents/gkehub.v1.json +30 -9
  83. googleapiclient/discovery_cache/documents/gkehub.v1alpha.json +30 -9
  84. googleapiclient/discovery_cache/documents/gkehub.v1beta.json +30 -9
  85. googleapiclient/discovery_cache/documents/gkehub.v1beta1.json +14 -1
  86. googleapiclient/discovery_cache/documents/gkehub.v2.json +17 -9
  87. googleapiclient/discovery_cache/documents/gkehub.v2alpha.json +17 -9
  88. googleapiclient/discovery_cache/documents/gkehub.v2beta.json +17 -9
  89. googleapiclient/discovery_cache/documents/healthcare.v1.json +61 -5
  90. googleapiclient/discovery_cache/documents/healthcare.v1beta1.json +24 -6
  91. googleapiclient/discovery_cache/documents/homegraph.v1.json +2 -2
  92. googleapiclient/discovery_cache/documents/iam.v1.json +524 -1
  93. googleapiclient/discovery_cache/documents/iamcredentials.v1.json +21 -1
  94. googleapiclient/discovery_cache/documents/integrations.v1.json +1 -363
  95. googleapiclient/discovery_cache/documents/kmsinventory.v1.json +17 -3
  96. googleapiclient/discovery_cache/documents/logging.v2.json +11 -1
  97. googleapiclient/discovery_cache/documents/looker.v1.json +15 -1
  98. googleapiclient/discovery_cache/documents/managedkafka.v1.json +11 -1
  99. googleapiclient/discovery_cache/documents/merchantapi.accounts_v1beta.json +131 -8
  100. googleapiclient/discovery_cache/documents/merchantapi.datasources_v1beta.json +3 -4
  101. googleapiclient/discovery_cache/documents/merchantapi.inventories_v1beta.json +9 -7
  102. googleapiclient/discovery_cache/documents/merchantapi.ordertracking_v1beta.json +5 -5
  103. googleapiclient/discovery_cache/documents/merchantapi.products_v1beta.json +22 -14
  104. googleapiclient/discovery_cache/documents/merchantapi.promotions_v1beta.json +2 -2
  105. googleapiclient/discovery_cache/documents/merchantapi.reviews_v1beta.json +17 -9
  106. googleapiclient/discovery_cache/documents/migrationcenter.v1alpha1.json +7 -3
  107. googleapiclient/discovery_cache/documents/monitoring.v1.json +4 -4
  108. googleapiclient/discovery_cache/documents/monitoring.v3.json +4 -4
  109. googleapiclient/discovery_cache/documents/mybusinessbusinessinformation.v1.json +6 -1
  110. googleapiclient/discovery_cache/documents/mybusinessverifications.v1.json +76 -1
  111. googleapiclient/discovery_cache/documents/netapp.v1beta1.json +51 -1
  112. googleapiclient/discovery_cache/documents/networkconnectivity.v1.json +4 -4
  113. googleapiclient/discovery_cache/documents/networkmanagement.v1.json +965 -14
  114. googleapiclient/discovery_cache/documents/networkmanagement.v1beta1.json +10 -5
  115. googleapiclient/discovery_cache/documents/networksecurity.v1.json +39 -5
  116. googleapiclient/discovery_cache/documents/networksecurity.v1beta1.json +270 -5
  117. googleapiclient/discovery_cache/documents/networkservices.v1.json +15 -13
  118. googleapiclient/discovery_cache/documents/networkservices.v1beta1.json +15 -13
  119. googleapiclient/discovery_cache/documents/notebooks.v2.json +131 -1
  120. googleapiclient/discovery_cache/documents/oracledatabase.v1.json +478 -1
  121. googleapiclient/discovery_cache/documents/osconfig.v1.json +24 -1
  122. googleapiclient/discovery_cache/documents/osconfig.v1alpha.json +24 -1
  123. googleapiclient/discovery_cache/documents/parametermanager.v1.json +982 -0
  124. googleapiclient/discovery_cache/documents/paymentsresellersubscription.v1.json +5 -5
  125. googleapiclient/discovery_cache/documents/recaptchaenterprise.v1.json +41 -5
  126. googleapiclient/discovery_cache/documents/redis.v1.json +166 -13
  127. googleapiclient/discovery_cache/documents/redis.v1beta1.json +166 -13
  128. googleapiclient/discovery_cache/documents/retail.v2.json +45 -2
  129. googleapiclient/discovery_cache/documents/retail.v2alpha.json +147 -2
  130. googleapiclient/discovery_cache/documents/retail.v2beta.json +45 -2
  131. googleapiclient/discovery_cache/documents/run.v1.json +2 -2
  132. googleapiclient/discovery_cache/documents/run.v2.json +19 -14
  133. googleapiclient/discovery_cache/documents/searchads360.v0.json +38 -4
  134. googleapiclient/discovery_cache/documents/searchconsole.v1.json +20 -1
  135. googleapiclient/discovery_cache/documents/secretmanager.v1.json +16 -1
  136. googleapiclient/discovery_cache/documents/secretmanager.v1beta1.json +16 -1
  137. googleapiclient/discovery_cache/documents/secretmanager.v1beta2.json +16 -1
  138. googleapiclient/discovery_cache/documents/securesourcemanager.v1.json +3568 -0
  139. googleapiclient/discovery_cache/documents/securitycenter.v1.json +290 -12
  140. googleapiclient/discovery_cache/documents/securitycenter.v1beta1.json +287 -9
  141. googleapiclient/discovery_cache/documents/securitycenter.v1beta2.json +287 -9
  142. googleapiclient/discovery_cache/documents/serviceconsumermanagement.v1.json +5 -1
  143. googleapiclient/discovery_cache/documents/serviceconsumermanagement.v1beta1.json +5 -1
  144. googleapiclient/discovery_cache/documents/servicenetworking.v1.json +22 -11
  145. googleapiclient/discovery_cache/documents/servicenetworking.v1beta.json +21 -10
  146. googleapiclient/discovery_cache/documents/serviceusage.v1.json +5 -1
  147. googleapiclient/discovery_cache/documents/serviceusage.v1beta1.json +5 -1
  148. googleapiclient/discovery_cache/documents/spanner.v1.json +4 -4
  149. googleapiclient/discovery_cache/documents/storage.v1.json +71 -2
  150. googleapiclient/discovery_cache/documents/testing.v1.json +21 -5
  151. googleapiclient/discovery_cache/documents/texttospeech.v1.json +2 -2
  152. googleapiclient/discovery_cache/documents/texttospeech.v1beta1.json +2 -2
  153. googleapiclient/discovery_cache/documents/tpu.v2alpha1.json +2 -2
  154. googleapiclient/discovery_cache/documents/transcoder.v1.json +54 -1
  155. googleapiclient/discovery_cache/documents/videointelligence.v1.json +11 -11
  156. googleapiclient/discovery_cache/documents/videointelligence.v1beta2.json +11 -11
  157. googleapiclient/discovery_cache/documents/videointelligence.v1p1beta1.json +11 -11
  158. googleapiclient/discovery_cache/documents/videointelligence.v1p2beta1.json +11 -11
  159. googleapiclient/discovery_cache/documents/videointelligence.v1p3beta1.json +11 -11
  160. googleapiclient/discovery_cache/documents/vmmigration.v1.json +9 -4
  161. googleapiclient/discovery_cache/documents/vmmigration.v1alpha1.json +9 -4
  162. googleapiclient/discovery_cache/documents/workloadmanager.v1.json +45 -225
  163. googleapiclient/discovery_cache/documents/workspaceevents.v1.json +4 -4
  164. googleapiclient/discovery_cache/documents/workstations.v1beta.json +8 -3
  165. googleapiclient/discovery_cache/documents/youtube.v3.json +67 -1
  166. googleapiclient/version.py +1 -1
  167. {google_api_python_client-2.176.0.dist-info → google_api_python_client-2.178.0.dist-info}/WHEEL +0 -0
  168. {google_api_python_client-2.176.0.dist-info → google_api_python_client-2.178.0.dist-info}/licenses/LICENSE +0 -0
  169. {google_api_python_client-2.176.0.dist-info → google_api_python_client-2.178.0.dist-info}/top_level.txt +0 -0
@@ -405,7 +405,7 @@
405
405
  ]
406
406
  },
407
407
  "create": {
408
- "description": "Creates a space. Can be used to create a named space, or a group chat in `Import mode`. For an example, see [Create a space](https://developers.google.com/workspace/chat/create-spaces). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) in [Developer Preview](https://developers.google.com/workspace/preview) and one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.app.spaces.create` - `https://www.googleapis.com/auth/chat.app.spaces` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.spaces.create` - `https://www.googleapis.com/auth/chat.spaces` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) When authenticating as an app, the `space.customer` field must be set in the request. When authenticating as an app, the Chat app is added as a member of the space. However, unlike human authentication, the Chat app is not added as a space manager. By default, the Chat app can be removed from the space by all space members. To allow only space managers to remove the app from a space, set `space.permission_settings.manage_apps` to `managers_allowed`. Space membership upon creation depends on whether the space is created in `Import mode`: * **Import mode:** No members are created. * **All other modes:** The calling user is added as a member. This is: * The app itself when using app authentication. * The human user when using user authentication. If you receive the error message `ALREADY_EXISTS` when creating a space, try a different `displayName`. An existing space within the Google Workspace organization might already use this display name.",
408
+ "description": "Creates a space. Can be used to create a named space, or a group chat in `Import mode`. For an example, see [Create a space](https://developers.google.com/workspace/chat/create-spaces). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) and one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.app.spaces.create` - `https://www.googleapis.com/auth/chat.app.spaces` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.spaces.create` - `https://www.googleapis.com/auth/chat.spaces` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) When authenticating as an app, the `space.customer` field must be set in the request. When authenticating as an app, the Chat app is added as a member of the space. However, unlike human authentication, the Chat app is not added as a space manager. By default, the Chat app can be removed from the space by all space members. To allow only space managers to remove the app from a space, set `space.permission_settings.manage_apps` to `managers_allowed`. Space membership upon creation depends on whether the space is created in `Import mode`: * **Import mode:** No members are created. * **All other modes:** The calling user is added as a member. This is: * The app itself when using app authentication. * The human user when using user authentication. If you receive the error message `ALREADY_EXISTS` when creating a space, try a different `displayName`. An existing space within the Google Workspace organization might already use this display name.",
409
409
  "flatPath": "v1/spaces",
410
410
  "httpMethod": "POST",
411
411
  "id": "chat.spaces.create",
@@ -433,7 +433,7 @@
433
433
  ]
434
434
  },
435
435
  "delete": {
436
- "description": "Deletes a named space. Always performs a cascading delete, which means that the space's child resources\u2014like messages posted in the space and memberships in the space\u2014are also deleted. For an example, see [Delete a space](https://developers.google.com/workspace/chat/delete-spaces). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) in [Developer Preview](https://developers.google.com/workspace/preview) and the authorization scope: - `https://www.googleapis.com/auth/chat.app.delete` (only in spaces the app created) - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.delete` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scope is used: - `https://www.googleapis.com/auth/chat.admin.delete`",
436
+ "description": "Deletes a named space. Always performs a cascading delete, which means that the space's child resources\u2014like messages posted in the space and memberships in the space\u2014are also deleted. For an example, see [Delete a space](https://developers.google.com/workspace/chat/delete-spaces). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) and the authorization scope: - `https://www.googleapis.com/auth/chat.app.delete` (only in spaces the app created) - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.delete` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scope is used: - `https://www.googleapis.com/auth/chat.admin.delete`",
437
437
  "flatPath": "v1/spaces/{spacesId}",
438
438
  "httpMethod": "DELETE",
439
439
  "id": "chat.spaces.delete",
@@ -558,7 +558,7 @@
558
558
  ]
559
559
  },
560
560
  "patch": {
561
- "description": "Updates a space. For an example, see [Update a space](https://developers.google.com/workspace/chat/update-spaces). If you're updating the `displayName` field and receive the error message `ALREADY_EXISTS`, try a different display name.. An existing space within the Google Workspace organization might already use this display name. Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) in [Developer Preview](https://developers.google.com/workspace/preview) and one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.app.spaces` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.spaces` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scopes is used: - `https://www.googleapis.com/auth/chat.admin.spaces` App authentication has the following limitations: - To update either `space.predefined_permission_settings` or `space.permission_settings`, the app must be the space creator. - Updating the `space.access_settings.audience` is not supported for app authentication.",
561
+ "description": "Updates a space. For an example, see [Update a space](https://developers.google.com/workspace/chat/update-spaces). If you're updating the `displayName` field and receive the error message `ALREADY_EXISTS`, try a different display name.. An existing space within the Google Workspace organization might already use this display name. Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) and one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.app.spaces` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.spaces` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scopes is used: - `https://www.googleapis.com/auth/chat.admin.spaces` App authentication has the following limitations: - To update either `space.predefined_permission_settings` or `space.permission_settings`, the app must be the space creator. - Updating the `space.access_settings.audience` is not supported for app authentication.",
562
562
  "flatPath": "v1/spaces/{spacesId}",
563
563
  "httpMethod": "PATCH",
564
564
  "id": "chat.spaces.patch",
@@ -666,7 +666,7 @@
666
666
  "members": {
667
667
  "methods": {
668
668
  "create": {
669
- "description": "Creates a membership for the calling Chat app, a user, or a Google Group. Creating memberships for other Chat apps isn't supported. When creating a membership, if the specified member has their auto-accept policy turned off, then they're invited, and must accept the space invitation before joining. Otherwise, creating a membership adds the member directly to the specified space. Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) in [Developer Preview](https://developers.google.com/workspace/preview) and the authorization scope: - `https://www.googleapis.com/auth/chat.app.memberships` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships` - `https://www.googleapis.com/auth/chat.memberships.app` (to add the calling app to the space) - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scope is used: - `https://www.googleapis.com/auth/chat.admin.memberships` App authentication is not supported for the following use cases: - Inviting users external to the Workspace organization that owns the space. - Adding a Google Group to a space. - Adding a Chat app to a space. For example usage, see: - [Invite or add a user to a space](https://developers.google.com/workspace/chat/create-members#create-user-membership). - [Invite or add a Google Group to a space](https://developers.google.com/workspace/chat/create-members#create-group-membership). - [Add the Chat app to a space](https://developers.google.com/workspace/chat/create-members#create-membership-calling-api).",
669
+ "description": "Creates a membership for the calling Chat app, a user, or a Google Group. Creating memberships for other Chat apps isn't supported. When creating a membership, if the specified member has their auto-accept policy turned off, then they're invited, and must accept the space invitation before joining. Otherwise, creating a membership adds the member directly to the specified space. Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) and the authorization scope: - `https://www.googleapis.com/auth/chat.app.memberships` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships` - `https://www.googleapis.com/auth/chat.memberships.app` (to add the calling app to the space) - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scope is used: - `https://www.googleapis.com/auth/chat.admin.memberships` App authentication is not supported for the following use cases: - Inviting users external to the Workspace organization that owns the space. - Adding a Google Group to a space. - Adding a Chat app to a space. For example usage, see: - [Invite or add a user to a space](https://developers.google.com/workspace/chat/create-members#create-user-membership). - [Invite or add a Google Group to a space](https://developers.google.com/workspace/chat/create-members#create-group-membership). - [Add the Chat app to a space](https://developers.google.com/workspace/chat/create-members#create-membership-calling-api).",
670
670
  "flatPath": "v1/spaces/{spacesId}/members",
671
671
  "httpMethod": "POST",
672
672
  "id": "chat.spaces.members.create",
@@ -703,7 +703,7 @@
703
703
  ]
704
704
  },
705
705
  "delete": {
706
- "description": "Deletes a membership. For an example, see [Remove a user or a Google Chat app from a space](https://developers.google.com/workspace/chat/delete-members). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) in [Developer Preview](https://developers.google.com/workspace/preview) and the authorization scope: - `https://www.googleapis.com/auth/chat.app.memberships` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships` - `https://www.googleapis.com/auth/chat.memberships.app` (to remove the calling app from the space) - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scope is used: - `https://www.googleapis.com/auth/chat.admin.memberships` App authentication is not supported for the following use cases: - Removing a Google Group from a space. - Removing a Chat app from a space. To delete memberships for space managers, the requester must be a space manager. If you're using [app authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) the Chat app must be the space creator.",
706
+ "description": "Deletes a membership. For an example, see [Remove a user or a Google Chat app from a space](https://developers.google.com/workspace/chat/delete-members). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) and the authorization scope: - `https://www.googleapis.com/auth/chat.app.memberships` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships` - `https://www.googleapis.com/auth/chat.memberships.app` (to remove the calling app from the space) - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scope is used: - `https://www.googleapis.com/auth/chat.admin.memberships` App authentication is not supported for the following use cases: - Removing a Google Group from a space. - Removing a Chat app from a space. To delete memberships for space managers, the requester must be a space manager. If you're using [app authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) the Chat app must be the space creator.",
707
707
  "flatPath": "v1/spaces/{spacesId}/members/{membersId}",
708
708
  "httpMethod": "DELETE",
709
709
  "id": "chat.spaces.members.delete",
@@ -737,7 +737,7 @@
737
737
  ]
738
738
  },
739
739
  "get": {
740
- "description": "Returns details about a membership. For an example, see [Get details about a user's or Google Chat app's membership](https://developers.google.com/workspace/chat/get-members). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with the authorization scope: - `https://www.googleapis.com/auth/chat.bot` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships.readonly` - `https://www.googleapis.com/auth/chat.memberships` - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and one of the following authorization scopes is used: - `https://www.googleapis.com/auth/chat.admin.memberships.readonly` - `https://www.googleapis.com/auth/chat.admin.memberships`",
740
+ "description": "Returns details about a membership. For an example, see [Get details about a user's or Google Chat app's membership](https://developers.google.com/workspace/chat/get-members). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.bot` - `https://www.googleapis.com/auth/chat.app.memberships` (requires [administrator approval](https://support.google.com/a?p=chat-app-auth)) - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships.readonly` - `https://www.googleapis.com/auth/chat.memberships` - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and one of the following authorization scopes is used: - `https://www.googleapis.com/auth/chat.admin.memberships.readonly` - `https://www.googleapis.com/auth/chat.admin.memberships`",
741
741
  "flatPath": "v1/spaces/{spacesId}/members/{membersId}",
742
742
  "httpMethod": "GET",
743
743
  "id": "chat.spaces.members.get",
@@ -772,7 +772,7 @@
772
772
  ]
773
773
  },
774
774
  "list": {
775
- "description": "Lists memberships in a space. For an example, see [List users and Google Chat apps in a space](https://developers.google.com/workspace/chat/list-members). Listing memberships with [app authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) lists memberships in spaces that the Chat app has access to, but excludes Chat app memberships, including its own. Listing memberships with [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) lists memberships in spaces that the authenticated user has access to. Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with the authorization scope: - `https://www.googleapis.com/auth/chat.bot` - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships.readonly` - `https://www.googleapis.com/auth/chat.memberships` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and one of the following authorization scopes is used: - `https://www.googleapis.com/auth/chat.admin.memberships.readonly` - `https://www.googleapis.com/auth/chat.admin.memberships`",
775
+ "description": "Lists memberships in a space. For an example, see [List users and Google Chat apps in a space](https://developers.google.com/workspace/chat/list-members). Listing memberships with [app authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) lists memberships in spaces that the Chat app has access to, but excludes Chat app memberships, including its own. Listing memberships with [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) lists memberships in spaces that the authenticated user has access to. Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.bot` - `https://www.googleapis.com/auth/chat.app.memberships` (requires [administrator approval](https://support.google.com/a?p=chat-app-auth)) - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships.readonly` - `https://www.googleapis.com/auth/chat.memberships` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and one of the following authorization scopes is used: - `https://www.googleapis.com/auth/chat.admin.memberships.readonly` - `https://www.googleapis.com/auth/chat.admin.memberships`",
776
776
  "flatPath": "v1/spaces/{spacesId}/members",
777
777
  "httpMethod": "GET",
778
778
  "id": "chat.spaces.members.list",
@@ -834,7 +834,7 @@
834
834
  ]
835
835
  },
836
836
  "patch": {
837
- "description": "Updates a membership. For an example, see [Update a user's membership in a space](https://developers.google.com/workspace/chat/update-members). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) in [Developer Preview](https://developers.google.com/workspace/preview) and the authorization scope: - `https://www.googleapis.com/auth/chat.app.memberships` (only in spaces the app created) - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scope is used: - `https://www.googleapis.com/auth/chat.admin.memberships`",
837
+ "description": "Updates a membership. For an example, see [Update a user's membership in a space](https://developers.google.com/workspace/chat/update-members). Supports the following types of [authentication](https://developers.google.com/workspace/chat/authenticate-authorize): - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) and the authorization scope: - `https://www.googleapis.com/auth/chat.app.memberships` (only in spaces the app created) - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) with one of the following authorization scopes: - `https://www.googleapis.com/auth/chat.memberships` - `https://www.googleapis.com/auth/chat.import` (import mode spaces only) - User authentication grants administrator privileges when an administrator account authenticates, `use_admin_access` is `true`, and the following authorization scope is used: - `https://www.googleapis.com/auth/chat.admin.memberships`",
838
838
  "flatPath": "v1/spaces/{spacesId}/members/{membersId}",
839
839
  "httpMethod": "PATCH",
840
840
  "id": "chat.spaces.members.patch",
@@ -1528,7 +1528,7 @@
1528
1528
  }
1529
1529
  }
1530
1530
  },
1531
- "revision": "20250619",
1531
+ "revision": "20250727",
1532
1532
  "rootUrl": "https://chat.googleapis.com/",
1533
1533
  "schemas": {
1534
1534
  "AccessSettings": {
@@ -1551,7 +1551,7 @@
1551
1551
  "type": "string"
1552
1552
  },
1553
1553
  "audience": {
1554
- "description": "Optional. The resource name of the [target audience](https://support.google.com/a/answer/9934697) who can discover the space, join the space, and preview the messages in the space. If unset, only users or Google Groups who have been individually invited or added to the space can access it. For details, see [Make a space discoverable to a target audience](https://developers.google.com/workspace/chat/space-target-audience). Format: `audiences/{audience}` To use the default target audience for the Google Workspace organization, set to `audiences/default`. Reading the target audience supports: - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) with the `chat.app.spaces` scope in [Developer Preview](https://developers.google.com/workspace/preview). This field is not populated when using the `chat.bot` scope with [app authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app). Setting the target audience requires [user authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user).",
1554
+ "description": "Optional. The resource name of the [target audience](https://support.google.com/a/answer/9934697) who can discover the space, join the space, and preview the messages in the space. If unset, only users or Google Groups who have been individually invited or added to the space can access it. For details, see [Make a space discoverable to a target audience](https://developers.google.com/workspace/chat/space-target-audience). Format: `audiences/{audience}` To use the default target audience for the Google Workspace organization, set to `audiences/default`. Reading the target audience supports: - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user) - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) with the `chat.app.spaces` scope. This field is not populated when using the `chat.bot` scope with [app authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app). Setting the target audience requires [user authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user).",
1555
1555
  "type": "string"
1556
1556
  }
1557
1557
  },
@@ -1678,7 +1678,7 @@
1678
1678
  "type": "object"
1679
1679
  },
1680
1680
  "Annotation": {
1681
- "description": "Output only. Annotations associated with the plain-text body of the message. To add basic formatting to a text message, see [Format text messages](https://developers.google.com/workspace/chat/format-messages). Example plain-text message body: ``` Hello @FooBot how are you!\" ``` The corresponding annotations metadata: ``` \"annotations\":[{ \"type\":\"USER_MENTION\", \"startIndex\":6, \"length\":7, \"userMention\": { \"user\": { \"name\":\"users/{user}\", \"displayName\":\"FooBot\", \"avatarUrl\":\"https://goo.gl/aeDtrS\", \"type\":\"BOT\" }, \"type\":\"MENTION\" } }] ```",
1681
+ "description": "Output only. Annotations can be associated with the plain-text body of the message or with chips that link to Google Workspace resources like Google Docs or Sheets with `start_index` and `length` of 0. To add basic formatting to a text message, see [Format text messages](https://developers.google.com/workspace/chat/format-messages). Example plain-text message body: ``` Hello @FooBot how are you!\" ``` The corresponding annotations metadata: ``` \"annotations\":[{ \"type\":\"USER_MENTION\", \"startIndex\":6, \"length\":7, \"userMention\": { \"user\": { \"name\":\"users/{user}\", \"displayName\":\"FooBot\", \"avatarUrl\":\"https://goo.gl/aeDtrS\", \"type\":\"BOT\" }, \"type\":\"MENTION\" } }] ```",
1682
1682
  "id": "Annotation",
1683
1683
  "properties": {
1684
1684
  "customEmojiMetadata": {
@@ -1686,7 +1686,7 @@
1686
1686
  "description": "The metadata for a custom emoji."
1687
1687
  },
1688
1688
  "length": {
1689
- "description": "Length of the substring in the plain-text message body this annotation corresponds to.",
1689
+ "description": "Length of the substring in the plain-text message body this annotation corresponds to. If not present, indicates a length of 0.",
1690
1690
  "format": "int32",
1691
1691
  "type": "integer"
1692
1692
  },
@@ -1851,6 +1851,21 @@
1851
1851
  },
1852
1852
  "type": "object"
1853
1853
  },
1854
+ "CalendarEventLinkData": {
1855
+ "description": "Data for Calendar event links.",
1856
+ "id": "CalendarEventLinkData",
1857
+ "properties": {
1858
+ "calendarId": {
1859
+ "description": "The [Calendar identifier](https://developers.google.com/workspace/calendar/api/v3/reference/calendars) of the linked Calendar.",
1860
+ "type": "string"
1861
+ },
1862
+ "eventId": {
1863
+ "description": "The [Event identifier](https://developers.google.com/workspace/calendar/api/v3/reference/events) of the linked Calendar event.",
1864
+ "type": "string"
1865
+ }
1866
+ },
1867
+ "type": "object"
1868
+ },
1854
1869
  "Card": {
1855
1870
  "description": "A card is a UI element that can contain UI widgets such as text and images.",
1856
1871
  "id": "Card",
@@ -2019,18 +2034,18 @@
2019
2034
  "type": "object"
2020
2035
  },
2021
2036
  "CommonEventObject": {
2022
- "description": "Represents information about the user's client, such as locale, host app, and platform. For Chat apps, `CommonEventObject` includes data submitted by users interacting with cards, like data entered in [dialogs](https://developers.google.com/chat/how-tos/dialogs).",
2037
+ "description": "The common event object is the portion of the overall event object that carries general, host-independent information to the add-on from the user's client. This information includes details such as the user's locale, host app, and platform. In addition to homepage and contextual triggers, add-ons construct and pass event objects to [action callback functions](https://developers.google.com/workspace/add-ons/concepts/actions#callback_functions) when the user interacts with widgets. Your add-on's callback function can query the common event object to determine the contents of open widgets in the user's client. For example, your add-on can locate the text a user has entered into a [TextInput](https://developers.google.com/apps-script/reference/card-service/text-input) widget in the `eventObject.commentEventObject.formInputs` object. For Chat apps, the name of the function that the user invoked when interacting with a widget.",
2023
2038
  "id": "CommonEventObject",
2024
2039
  "properties": {
2025
2040
  "formInputs": {
2026
2041
  "additionalProperties": {
2027
2042
  "$ref": "Inputs"
2028
2043
  },
2029
- "description": "A map containing the values that a user inputs in a widget from a card or dialog. The map keys are the string IDs assigned to each widget, and the values represent inputs to the widget. For details, see [Process information inputted by users](https://developers.google.com/chat/ui/read-form-data).",
2044
+ "description": "A map containing the current values of the widgets in the displayed card. The map keys are the string IDs assigned with each widget. The structure of the map value object is dependent on the widget type: **Note**: The following examples are formatted for Apps Script's V8 runtime. If you're using Rhino runtime, you must add `[\"\"]` after the value. For example, instead of `e.commonEventObject.formInputs.employeeName.stringInputs.value[0]`, format the event object as `e.commonEventObject.formInputs.employeeName[\"\"].stringInputs.value[0]`. To learn more about runtimes in Apps Script, see the [V8 Runtime Overview](https://developers.google.com/apps-script/guides/v8-runtime). * Single-valued widgets (for example, a text box): a list of strings (only one element). **Example**: for a text input widget with `employeeName` as its ID, access the text input value with: `e.commonEventObject.formInputs.employeeName.stringInputs.value[0]`. * Multi-valued widgets (for example, checkbox groups): a list of strings. **Example**: for a multi-value widget with `participants` as its ID, access the value array with: `e.commonEventObject.formInputs.participants.stringInputs.value`. * **A date-time picker**: a [`DateTimeInput object`](https://developers.google.com/workspace/add-ons/concepts/event-objects#date-time-input). **Example**: For a picker with an ID of `myDTPicker`, access the [`DateTimeInput`](https://developers.google.com/workspace/add-ons/concepts/event-objects#date-time-input) object using `e.commonEventObject.formInputs.myDTPicker.dateTimeInput`. * **A date-only picker**: a [`DateInput object`](https://developers.google.com/workspace/add-ons/concepts/event-objects#date-input). **Example**: For a picker with an ID of `myDatePicker`, access the [`DateInput`](https://developers.google.com/workspace/add-ons/concepts/event-objects#date-input) object using `e.commonEventObject.formInputs.myDatePicker.dateInput`. * **A time-only picker**: a [`TimeInput object`](https://developers.google.com/workspace/add-ons/concepts/event-objects#time-input). **Example**: For a picker with an ID of `myTimePicker`, access the [`TimeInput`](https://developers.google.com/workspace/add-ons/concepts/event-objects#time-input) object using `e.commonEventObject.formInputs.myTimePicker.timeInput`.",
2030
2045
  "type": "object"
2031
2046
  },
2032
2047
  "hostApp": {
2033
- "description": "The hostApp enum which indicates the app the add-on is invoked from. Always `CHAT` for Chat apps.",
2048
+ "description": "Indicates the host app the add-on is active in when the event object is generated. Possible values include the following: * `GMAIL` * `CALENDAR` * `DRIVE` * `DOCS` * `SHEETS` * `SLIDES` * `CHAT`",
2034
2049
  "enum": [
2035
2050
  "UNSPECIFIED_HOST_APP",
2036
2051
  "GMAIL",
@@ -2067,7 +2082,7 @@
2067
2082
  "additionalProperties": {
2068
2083
  "type": "string"
2069
2084
  },
2070
- "description": "Custom [parameters](/chat/api/reference/rest/v1/cards#ActionParameter) passed to the invoked function. Both keys and values must be strings.",
2085
+ "description": "Any additional parameters you supply to an action using [`actionParameters`](https://developers.google.com/workspace/add-ons/reference/rpc/google.apps.card.v1#google.apps.card.v1.Action.ActionParameter) or [`Action.setParameters()`](https://developers.google.com/apps-script/reference/card-service/action#setparametersparameters). **Developer Preview:** For [add-ons that extend Google Chat](https://developers.google.com/workspace/add-ons/chat), to suggest items based on what the users type in multiselect menus, use the value of the `\"autocomplete_widget_query\"` key (`event.commonEventObject.parameters[\"autocomplete_widget_query\"]`). You can use this value to query a database and suggest selectable items to users as they type. For details, see [Collect and process information from Google Chat users](https://developers.google.com/workspace/add-ons/chat/collect-information).",
2071
2086
  "type": "object"
2072
2087
  },
2073
2088
  "platform": {
@@ -2088,10 +2103,10 @@
2088
2103
  },
2089
2104
  "timeZone": {
2090
2105
  "$ref": "TimeZone",
2091
- "description": "The timezone ID and offset from Coordinated Universal Time (UTC). Only supported for the event types [`CARD_CLICKED`](https://developers.google.com/chat/api/reference/rest/v1/EventType#ENUM_VALUES.CARD_CLICKED) and [`SUBMIT_DIALOG`](https://developers.google.com/chat/api/reference/rest/v1/DialogEventType#ENUM_VALUES.SUBMIT_DIALOG)."
2106
+ "description": "**Disabled by default.** The timezone ID and offset from Coordinated Universal Time (UTC). To turn on this field, you must set `addOns.common.useLocaleFromApp` to `true` in your add-on's manifest. Your add-on's scope list must also include `https://www.googleapis.com/auth/script.locale`. See [Accessing user locale and timezone](https://developers.google.com/workspace/add-ons/how-tos/access-user-locale) for more details. Only supported for the event types [`CARD_CLICKED`](https://developers.google.com/chat/api/reference/rest/v1/EventType#ENUM_VALUES.CARD_CLICKED) and [`SUBMIT_DIALOG`](https://developers.google.com/chat/api/reference/rest/v1/DialogEventType#ENUM_VALUES.SUBMIT_DIALOG)."
2092
2107
  },
2093
2108
  "userLocale": {
2094
- "description": "The full `locale.displayName` in the format of [ISO 639 language code]-[ISO 3166 country/region code] such as \"en-US\".",
2109
+ "description": "**Disabled by default.** The user's language and country/region identifier in the format of [ISO 639](https://wikipedia.org/wiki/ISO_639_macrolanguage) language code-[ISO 3166](https://wikipedia.org/wiki/ISO_3166) country/region code. For example, `en-US`. To turn on this field, you must set `addOns.common.useLocaleFromApp` to `true` in your add-on's manifest. Your add-on's scope list must also include `https://www.googleapis.com/auth/script.locale`. See [Accessing user locale and timezone](https://developers.google.com/workspace/add-ons/how-tos/access-user-locale) for more details.",
2095
2110
  "type": "string"
2096
2111
  }
2097
2112
  },
@@ -2234,7 +2249,7 @@
2234
2249
  "type": "object"
2235
2250
  },
2236
2251
  "DeprecatedEvent": {
2237
- "description": "A Google Chat app interaction event that represents and contains data about a user's interaction with a Chat app. To configure your Chat app to receive interaction events, see [Receive and respond to user interactions](https://developers.google.com/workspace/chat/receive-respond-interactions). In addition to receiving events from user interactions, Chat apps can receive events about changes to spaces, such as when a new member is added to a space. To learn about space events, see [Work with events from Google Chat](https://developers.google.com/workspace/chat/events-overview).",
2252
+ "description": " A Google Chat app interaction event that represents and contains data about a user's interaction with a Chat app. To configure your Chat app to receive interaction events, see [Receive and respond to user interactions](https://developers.google.com/workspace/chat/receive-respond-interactions). In addition to receiving events from user interactions, Chat apps can receive events about changes to spaces, such as when a new member is added to a space. To learn about space events, see [Work with events from Google Chat](https://developers.google.com/workspace/chat/events-overview). Note: This event is only used for [Chat interaction events](https://developers.google.com/workspace/chat/receive-respond-interactions). If your Chat app is built as a [Google Workspace add-on](https://developers.google.com/workspace/add-ons/chat/build), see [Chat event objects](https://developers.google.com/workspace/add-ons/concepts/event-objects#chat-event-object) in the add-ons documentation.",
2238
2253
  "id": "DeprecatedEvent",
2239
2254
  "properties": {
2240
2255
  "action": {
@@ -3408,6 +3423,10 @@
3408
3423
  "$ref": "GoogleAppsCardV1Action",
3409
3424
  "description": "An external data source, such as a relational database."
3410
3425
  },
3426
+ "hintText": {
3427
+ "description": "Optional. Text that appears below the selection input field meant to assist users by prompting them to enter a certain value. This text is always visible. Only supported by Google Workspace Workflows, but not Google Chat API or Google Workspace Add-ons.",
3428
+ "type": "string"
3429
+ },
3411
3430
  "items": {
3412
3431
  "description": "An array of selectable items. For example, an array of radio buttons or checkboxes. Supports up to 100 items.",
3413
3432
  "items": {
@@ -4153,6 +4172,48 @@
4153
4172
  },
4154
4173
  "type": "object"
4155
4174
  },
4175
+ "MeetSpaceLinkData": {
4176
+ "description": "Data for Meet space links.",
4177
+ "id": "MeetSpaceLinkData",
4178
+ "properties": {
4179
+ "huddleStatus": {
4180
+ "description": "Optional. Output only. If the Meet is a Huddle, indicates the status of the huddle. Otherwise, this is unset.",
4181
+ "enum": [
4182
+ "HUDDLE_STATUS_UNSPECIFIED",
4183
+ "STARTED",
4184
+ "ENDED",
4185
+ "MISSED"
4186
+ ],
4187
+ "enumDescriptions": [
4188
+ "Default value for the enum. Don't use.",
4189
+ "The huddle has started.",
4190
+ "The huddle has ended. In this case the Meet space URI and identifiers will no longer be valid.",
4191
+ "The huddle has been missed. In this case the Meet space URI and identifiers will no longer be valid."
4192
+ ],
4193
+ "readOnly": true,
4194
+ "type": "string"
4195
+ },
4196
+ "meetingCode": {
4197
+ "description": "Meeting code of the linked Meet space.",
4198
+ "type": "string"
4199
+ },
4200
+ "type": {
4201
+ "description": "Indicates the type of the Meet space.",
4202
+ "enum": [
4203
+ "TYPE_UNSPECIFIED",
4204
+ "MEETING",
4205
+ "HUDDLE"
4206
+ ],
4207
+ "enumDescriptions": [
4208
+ "Default value for the enum. Don't use.",
4209
+ "The Meet space is a meeting.",
4210
+ "The Meet space is a huddle."
4211
+ ],
4212
+ "type": "string"
4213
+ }
4214
+ },
4215
+ "type": "object"
4216
+ },
4156
4217
  "Membership": {
4157
4218
  "description": "Represents a membership relation in Google Chat, such as whether a user or Chat app is invited to, part of, or absent from a space.",
4158
4219
  "id": "Membership",
@@ -4323,7 +4384,7 @@
4323
4384
  "description": "Input only. Parameters that a Chat app can use to configure how its response is posted."
4324
4385
  },
4325
4386
  "annotations": {
4326
- "description": "Output only. Annotations associated with the `text` in this message.",
4387
+ "description": "Output only. Annotations can be associated with the plain-text body of the message or with chips that link to Google Workspace resources like Google Docs or Sheets with `start_index` and `length` of 0.",
4327
4388
  "items": {
4328
4389
  "$ref": "Annotation"
4329
4390
  },
@@ -4423,8 +4484,7 @@
4423
4484
  },
4424
4485
  "quotedMessageMetadata": {
4425
4486
  "$ref": "QuotedMessageMetadata",
4426
- "description": "Output only. Information about a message that's quoted by a Google Chat user in a space. Google Chat users can quote a message to reply to it.",
4427
- "readOnly": true
4487
+ "description": "Optional. Information about a message that's quoted by a Google Chat user in a space. Google Chat users can quote a message to reply to it."
4428
4488
  },
4429
4489
  "sender": {
4430
4490
  "$ref": "User",
@@ -4618,14 +4678,12 @@
4618
4678
  "id": "QuotedMessageMetadata",
4619
4679
  "properties": {
4620
4680
  "lastUpdateTime": {
4621
- "description": "Output only. The timestamp when the quoted message was created or when the quoted message was last updated.",
4681
+ "description": "Required. The timestamp when the quoted message was created or when the quoted message was last updated.",
4622
4682
  "format": "google-datetime",
4623
- "readOnly": true,
4624
4683
  "type": "string"
4625
4684
  },
4626
4685
  "name": {
4627
- "description": "Output only. Resource name of the quoted message. Format: `spaces/{space}/messages/{message}`",
4628
- "readOnly": true,
4686
+ "description": "Required. Resource name of the message that is quoted. Format: `spaces/{space}/messages/{message}`",
4629
4687
  "type": "string"
4630
4688
  }
4631
4689
  },
@@ -4702,9 +4760,13 @@
4702
4760
  "type": "object"
4703
4761
  },
4704
4762
  "RichLinkMetadata": {
4705
- "description": "A rich link to a resource.",
4763
+ "description": "A rich link to a resource. Rich links can be associated with the plain-text body of the message or represent chips that link to Google Workspace resources like Google Docs or Sheets with `start_index` and `length` of 0.",
4706
4764
  "id": "RichLinkMetadata",
4707
4765
  "properties": {
4766
+ "calendarEventLinkData": {
4767
+ "$ref": "CalendarEventLinkData",
4768
+ "description": "Data for a Calendar event link."
4769
+ },
4708
4770
  "chatSpaceLinkData": {
4709
4771
  "$ref": "ChatSpaceLinkData",
4710
4772
  "description": "Data for a chat space link."
@@ -4713,17 +4775,25 @@
4713
4775
  "$ref": "DriveLinkData",
4714
4776
  "description": "Data for a drive link."
4715
4777
  },
4778
+ "meetSpaceLinkData": {
4779
+ "$ref": "MeetSpaceLinkData",
4780
+ "description": "Data for a Meet space link."
4781
+ },
4716
4782
  "richLinkType": {
4717
4783
  "description": "The rich link type.",
4718
4784
  "enum": [
4719
4785
  "RICH_LINK_TYPE_UNSPECIFIED",
4720
4786
  "DRIVE_FILE",
4721
- "CHAT_SPACE"
4787
+ "CHAT_SPACE",
4788
+ "MEET_SPACE",
4789
+ "CALENDAR_EVENT"
4722
4790
  ],
4723
4791
  "enumDescriptions": [
4724
4792
  "Default value for the enum. Don't use.",
4725
4793
  "A Google Drive rich link type.",
4726
- "A Chat space rich link type. For example, a space smart chip."
4794
+ "A Chat space rich link type. For example, a space smart chip.",
4795
+ "A Meet message rich link type. For example, a Meet chip.",
4796
+ "A Calendar message rich link type. For example, a Calendar chip."
4727
4797
  ],
4728
4798
  "type": "string"
4729
4799
  },
@@ -4879,6 +4949,10 @@
4879
4949
  "format": "google-datetime",
4880
4950
  "type": "string"
4881
4951
  },
4952
+ "customer": {
4953
+ "description": "Optional. Immutable. The customer id of the domain of the space. Required only when creating a space with [app authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) and `SpaceType` is `SPACE`, otherwise should not be set. In the format `customers/{customer}`, where `customer` is the `id` from the [Admin SDK customer resource]( https://developers.google.com/admin-sdk/directory/reference/rest/v1/customers). Private apps can also use the `customers/my_customer` alias to create the space in the same Google Workspace organization as the app. For DMs, this field isn't populated.",
4954
+ "type": "string"
4955
+ },
4882
4956
  "displayName": {
4883
4957
  "description": "Optional. The space's display name. Required when [creating a space](https://developers.google.com/workspace/chat/api/reference/rest/v1/spaces/create) with a `spaceType` of `SPACE`. If you receive the error message `ALREADY_EXISTS` when creating a space or updating the `displayName`, try a different `displayName`. An existing space within the Google Workspace organization might already use this display name. For direct messages, this field might be empty. Supports up to 128 characters.",
4884
4958
  "type": "string"
@@ -4914,10 +4988,10 @@
4914
4988
  },
4915
4989
  "permissionSettings": {
4916
4990
  "$ref": "PermissionSettings",
4917
- "description": "Optional. Space permission settings for existing spaces. Input for updating exact space permission settings, where existing permission settings are replaced. Output lists current permission settings. Reading and updating permission settings supports: - In [Developer Preview](https://developers.google.com/workspace/preview), [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) with the `chat.app.spaces` scope. Only populated and settable when the Chat app created the space. - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user)"
4991
+ "description": "Optional. Space permission settings for existing spaces. Input for updating exact space permission settings, where existing permission settings are replaced. Output lists current permission settings. Reading and updating permission settings supports: - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) with the `chat.app.spaces` scope. Only populated and settable when the Chat app created the space. - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user)"
4918
4992
  },
4919
4993
  "predefinedPermissionSettings": {
4920
- "description": "Optional. Input only. Predefined space permission settings, input only when creating a space. If the field is not set, a collaboration space is created. After you create the space, settings are populated in the `PermissionSettings` field. Setting predefined permission settings supports: - In [Developer Preview](https://developers.google.com/workspace/preview), [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) with the `chat.app.spaces` or `chat.app.spaces.create` scopes. - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user)",
4994
+ "description": "Optional. Input only. Predefined space permission settings, input only when creating a space. If the field is not set, a collaboration space is created. After you create the space, settings are populated in the `PermissionSettings` field. Setting predefined permission settings supports: - [App authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-app) with [administrator approval](https://support.google.com/a?p=chat-app-auth) with the `chat.app.spaces` or `chat.app.spaces.create` scopes. - [User authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user)",
4921
4995
  "enum": [
4922
4996
  "PREDEFINED_PERMISSION_SETTINGS_UNSPECIFIED",
4923
4997
  "COLLABORATION_SPACE",