google-api-python-client 2.134.0__py2.py3-none-any.whl → 2.136.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/beyondcorp.v1alpha.json

@@ -1323,7 +1323,7 @@
 ],
 "parameters": {
 "name": {
-"description": "Required. Unique resource name of the Subscription. The name is ignored when creating a subscription.",
+"description": "Identifier. Unique resource name of the Subscription. The name is ignored when creating a subscription.",
 "location": "path",
 "pattern": "^organizations/[^/]+/locations/[^/]+/subscriptions/[^/]+$",
 "required": true,
@@ -4080,7 +4080,7 @@
 }
 }
 },
-"revision": "20240527",
+"revision": "20240619",
 "rootUrl": "https://beyondcorp.googleapis.com/",
 "schemas": {
 "AllocatedConnection": {
@@ -5693,6 +5693,10 @@
 "readOnly": true,
 "type": "string"
 },
+"proxyProtocolConfig": {
+"$ref": "GoogleCloudBeyondcorpPartnerservicesV1alphaProxyProtocolConfig",
+"description": "Optional. Protocol config data for the Proxy."
+},
 "proxyUri": {
 "description": "Required. The URI of the proxy server.",
 "type": "string"
@@ -5714,6 +5718,20 @@
 },
 "type": "object"
 },
+"GoogleCloudBeyondcorpPartnerservicesV1alphaProxyProtocolConfig": {
+"description": "The protocol data that specifies how to communicate with Partner's Proxy.",
+"id": "GoogleCloudBeyondcorpPartnerservicesV1alphaProxyProtocolConfig",
+"properties": {
+"metadata": {
+"additionalProperties": {
+"type": "string"
+},
+"description": "Optional. Untyped property bag to be sent back to the proxy using client specific mechanism.",
+"type": "object"
+}
+},
+"type": "object"
+},
 "GoogleCloudBeyondcorpPartnerservicesV1alphaRoutingInfo": {
 "description": "Message contains the routing information to direct traffic to the proxy server.",
 "id": "GoogleCloudBeyondcorpPartnerservicesV1alphaRoutingInfo",
@@ -6159,7 +6177,7 @@
 "type": "string"
 },
 "name": {
-"description": "Required. Unique resource name of the Subscription. The name is ignored when creating a subscription.",
+"description": "Identifier. Unique resource name of the Subscription. The name is ignored when creating a subscription.",
 "type": "string"
 },
 "seatCount": {
@@ -6202,6 +6220,21 @@
 "readOnly": true,
 "type": "string"
 },
+"subscriberType": {
+"description": "Output only. Type of subscriber.",
+"enum": [
+"SUBSCRIBER_TYPE_UNSPECIFIED",
+"ONLINE",
+"OFFLINE"
+],
+"enumDescriptions": [
+"Default value. This value is unused.",
+"Represents an online subscription.",
+"Represents an offline subscription."
+],
+"readOnly": true,
+"type": "string"
+},
 "type": {
 "description": "Required. Type of subscription.",
 "enum": [

googleapiclient/discovery_cache/documents/biglake.v1.json

@@ -616,7 +616,7 @@
 }
 }
 },
-"revision": "20240612",
+"revision": "20240626",
 "rootUrl": "https://biglake.googleapis.com/",
 "schemas": {
 "Catalog": {

googleapiclient/discovery_cache/documents/bigquery.v2.json

@@ -36,11 +36,6 @@
 "endpoints": [
 {
 "description": "Regional Endpoint",
-"endpointUrl": "https://bigquery.me-central2.rep.googleapis.com/",
-"location": "me-central2"
-},
-{
-"description": "Regional Endpoint",
 "endpointUrl": "https://bigquery.europe-west3.rep.googleapis.com/",
 "location": "europe-west3"
 },
@@ -51,6 +46,11 @@
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://bigquery.me-central2.rep.googleapis.com/",
+"location": "me-central2"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://bigquery.us-east4.rep.googleapis.com/",
 "location": "us-east4"
 },
@@ -1935,7 +1935,7 @@
 }
 }
 },
-"revision": "20240602",
+"revision": "20240616",
 "rootUrl": "https://bigquery.googleapis.com/",
 "schemas": {
 "AggregateClassificationMetrics": {
@@ -2998,7 +2998,7 @@
 "type": "object"
 },
 "ConnectionProperty": {
-"description": "A connection-level property to customize query behavior. Under JDBC, these correspond directly to connection properties passed to the DriverManager. Under ODBC, these correspond to properties in the connection string. Currently supported connection properties: * **dataset_project_id**: represents the default project for datasets that are used in the query. Setting the system variable `@@dataset_project_id` achieves the same behavior. For more information about system variables, see: https://cloud.google.com/bigquery/docs/reference/system-variables * **time_zone**: represents the default timezone used to run the query. * **session_id**: associates the query with a given session. * **query_label**: associates the query with a given job label. If set, all subsequent queries in a script or session will have this label. For the format in which a you can specify a query label, see labels in the JobConfiguration resource type: https://cloud.google.com/bigquery/docs/reference/rest/v2/Job#jobconfiguration Additional properties are allowed, but ignored. Specifying multiple connection properties with the same key returns an error.",
+"description": "A connection-level property to customize query behavior. Under JDBC, these correspond directly to connection properties passed to the DriverManager. Under ODBC, these correspond to properties in the connection string. Currently supported connection properties: * **dataset_project_id**: represents the default project for datasets that are used in the query. Setting the system variable `@@dataset_project_id` achieves the same behavior. For more information about system variables, see: https://cloud.google.com/bigquery/docs/reference/system-variables * **time_zone**: represents the default timezone used to run the query. * **session_id**: associates the query with a given session. * **query_label**: associates the query with a given job label. If set, all subsequent queries in a script or session will have this label. For the format in which a you can specify a query label, see labels in the JobConfiguration resource type: https://cloud.google.com/bigquery/docs/reference/rest/v2/Job#jobconfiguration * **service_account**: indicates the service account to use to run a continuous query. If set, the query job uses the service account to access Google Cloud resources. Service account access is bounded by the IAM permissions that you have granted to the service account. Additional properties are allowed, but ignored. Specifying multiple connection properties with the same key returns an error.",
 "id": "ConnectionProperty",
 "properties": {
 "key": {
@@ -6747,23 +6747,21 @@
 "id": "PartitionedColumn",
 "properties": {
 "field": {
-"description": "Output only. The name of the partition column.",
-"readOnly": true,
+"description": "Required. The name of the partition column.",
 "type": "string"
 }
 },
 "type": "object"
 },
 "PartitioningDefinition": {
-"description": "The partitioning information, which includes managed table and external table partition information.",
+"description": "The partitioning information, which includes managed table, external table and metastore partitioned table partition information.",
 "id": "PartitioningDefinition",
 "properties": {
 "partitionedColumn": {
-"description": "Output only. Details about each partitioning column. BigQuery native tables only support 1 partitioning column. Other table types may support 0, 1 or more partitioning columns.",
+"description": "Optional. Details about each partitioning column. This field is output only for all partitioning types other than metastore partitioned tables. BigQuery native tables only support 1 partitioning column. Other table types may support 0, 1 or more partitioning columns. For metastore partitioned tables, the order must match the definition order in the Hive Metastore, where it must match the physical layout of the table. For example, CREATE TABLE a_table(id BIGINT, name STRING) PARTITIONED BY (city STRING, state STRING). In this case the values must be ['city', 'state'] in that order.",
 "items": {
 "$ref": "PartitionedColumn"
 },
-"readOnly": true,
 "type": "array"
 }
 },
@@ -8507,8 +8505,7 @@
 },
 "partitionDefinition": {
 "$ref": "PartitioningDefinition",
-"description": "Output only. The partition information for all table formats, including managed partitioned tables, hive partitioned tables, and iceberg partitioned tables.",
-"readOnly": true
+"description": "Optional. The partition information for all table formats, including managed partitioned tables, hive partitioned tables, iceberg partitioned, and metastore partitioned tables. This field is only populated for metastore partitioned tables. For other table formats, this is an output only field."
 },
 "rangePartitioning": {
 "$ref": "RangePartitioning",

googleapiclient/discovery_cache/documents/bigqueryconnection.v1.json

@@ -366,7 +366,7 @@
 }
 }
 },
-"revision": "20240602",
+"revision": "20240616",
 "rootUrl": "https://bigqueryconnection.googleapis.com/",
 "schemas": {
 "AuditConfig": {

googleapiclient/discovery_cache/documents/bigqueryconnection.v1beta1.json

@@ -395,7 +395,7 @@
 }
 }
 },
-"revision": "20240602",
+"revision": "20240616",
 "rootUrl": "https://bigqueryconnection.googleapis.com/",
 "schemas": {
 "AuditConfig": {

googleapiclient/discovery_cache/documents/bigquerydatapolicy.v1.json

@@ -395,7 +395,7 @@
 }
 }
 },
-"revision": "20240610",
+"revision": "20240623",
 "rootUrl": "https://bigquerydatapolicy.googleapis.com/",
 "schemas": {
 "AuditConfig": {

googleapiclient/discovery_cache/documents/bigquerydatatransfer.v1.json

@@ -24,11 +24,6 @@
 "endpoints": [
 {
 "description": "Regional Endpoint",
-"endpointUrl": "https://bigquerydatatransfer.me-central2.rep.googleapis.com/",
-"location": "me-central2"
-},
-{
-"description": "Regional Endpoint",
 "endpointUrl": "https://bigquerydatatransfer.europe-west3.rep.googleapis.com/",
 "location": "europe-west3"
 },
@@ -39,11 +34,21 @@
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://bigquerydatatransfer.me-central2.rep.googleapis.com/",
+"location": "me-central2"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://bigquerydatatransfer.us-east4.rep.googleapis.com/",
 "location": "us-east4"
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://bigquerydatatransfer.us-east7.rep.googleapis.com/",
+"location": "us-east7"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://bigquerydatatransfer.us-west1.rep.googleapis.com/",
 "location": "us-west1"
 }
@@ -1398,7 +1403,7 @@
 }
 }
 },
-"revision": "20240608",
+"revision": "20240623",
 "rootUrl": "https://bigquerydatatransfer.googleapis.com/",
 "schemas": {
 "CheckValidCredsRequest": {

googleapiclient/discovery_cache/documents/bigqueryreservation.v1.json

@@ -21,11 +21,6 @@
 "endpoints": [
 {
 "description": "Regional Endpoint",
-"endpointUrl": "https://bigqueryreservation.me-central2.rep.googleapis.com/",
-"location": "me-central2"
-},
-{
-"description": "Regional Endpoint",
 "endpointUrl": "https://bigqueryreservation.europe-west3.rep.googleapis.com/",
 "location": "europe-west3"
 },
@@ -36,11 +31,21 @@
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://bigqueryreservation.me-central2.rep.googleapis.com/",
+"location": "me-central2"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://bigqueryreservation.us-east4.rep.googleapis.com/",
 "location": "us-east4"
 },
 {
 "description": "Regional Endpoint",
+"endpointUrl": "https://bigqueryreservation.us-east7.rep.googleapis.com/",
+"location": "us-east7"
+},
+{
+"description": "Regional Endpoint",
 "endpointUrl": "https://bigqueryreservation.us-west1.rep.googleapis.com/",
 "location": "us-west1"
 }
@@ -880,7 +885,7 @@
 }
 }
 },
-"revision": "20240604",
+"revision": "20240621",
 "rootUrl": "https://bigqueryreservation.googleapis.com/",
 "schemas": {
 "Assignment": {

googleapiclient/discovery_cache/documents/bigtableadmin.v2.json

@@ -2194,7 +2194,7 @@
 }
 }
 },
-"revision": "20240604",
+"revision": "20240628",
 "rootUrl": "https://bigtableadmin.googleapis.com/",
 "schemas": {
 "AppProfile": {
@@ -3189,7 +3189,7 @@
 "type": "object"
 },
 "GoogleBigtableAdminV2TypeBytesEncodingRaw": {
-"description": "Leaves the value \"as-is\" * Natural sort? Yes * Self-delimiting? No * Compatibility? N/A",
+"description": "Leaves the value \"as-is\" * Order-preserving? Yes * Self-delimiting? No * Compatibility? N/A",
 "id": "GoogleBigtableAdminV2TypeBytesEncodingRaw",
 "properties": {},
 "type": "object"
@@ -3217,12 +3217,12 @@
 "type": "object"
 },
 "GoogleBigtableAdminV2TypeInt64EncodingBigEndianBytes": {
-"description": "Encodes the value as an 8-byte big endian twos complement `Bytes` value. * Natural sort? No (positive values only) * Self-delimiting? Yes * Compatibility? - BigQuery Federation `BINARY` encoding - HBase `Bytes.toBytes` - Java `ByteBuffer.putLong()` with `ByteOrder.BIG_ENDIAN`",
+"description": "Encodes the value as an 8-byte big endian twos complement `Bytes` value. * Order-preserving? No (positive values only) * Self-delimiting? Yes * Compatibility? - BigQuery Federation `BINARY` encoding - HBase `Bytes.toBytes` - Java `ByteBuffer.putLong()` with `ByteOrder.BIG_ENDIAN`",
 "id": "GoogleBigtableAdminV2TypeInt64EncodingBigEndianBytes",
 "properties": {
 "bytesType": {
 "$ref": "GoogleBigtableAdminV2TypeBytes",
-"description": "The underlying `Bytes` type, which may be able to encode further."
+"description": "Deprecated: ignored if set."
 }
 },
 "type": "object"
@@ -4103,7 +4103,7 @@
 "type": "object"
 },
 "Type": {
-"description": "`Type` represents the type of data that is written to, read from, or stored in Bigtable. It is heavily based on the GoogleSQL standard to help maintain familiarity and consistency across products and features. For compatibility with Bigtable's existing untyped APIs, each `Type` includes an `Encoding` which describes how to convert to/from the underlying data. This might involve composing a series of steps into an \"encoding chain,\" for example to convert from INT64 -> STRING -> raw bytes. In most cases, a \"link\" in the encoding chain will be based an on existing GoogleSQL conversion function like `CAST`. Each link in the encoding chain also defines the following properties: * Natural sort: Does the encoded value sort consistently with the original typed value? Note that Bigtable will always sort data based on the raw encoded value, *not* the decoded type. - Example: BYTES values sort in the same order as their raw encodings. - Counterexample: Encoding INT64 to a fixed-width STRING does *not* preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1), but STRING(\"-00001\") > STRING(\"00001). - The overall encoding chain has this property if *every* link does. * Self-delimiting: If we concatenate two encoded values, can we always tell where the first one ends and the second one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell where the first one ends. - The overall encoding chain has this property if *any* link does. * Compatibility: Which other systems have matching encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?",
+"description": "`Type` represents the type of data that is written to, read from, or stored in Bigtable. It is heavily based on the GoogleSQL standard to help maintain familiarity and consistency across products and features. For compatibility with Bigtable's existing untyped APIs, each `Type` includes an `Encoding` which describes how to convert to/from the underlying data. Each encoding also defines the following properties: * Order-preserving: Does the encoded value sort consistently with the original typed value? Note that Bigtable will always sort data based on the raw encoded value, *not* the decoded type. - Example: BYTES values sort in the same order as their raw encodings. - Counterexample: Encoding INT64 as a fixed-width decimal string does *not* preserve sort order when dealing with negative numbers. INT64(1) > INT64(-1), but STRING(\"-00001\") > STRING(\"00001). * Self-delimiting: If we concatenate two encoded values, can we always tell where the first one ends and the second one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell where the first one ends. * Compatibility: Which other systems have matching encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?",
 "id": "Type",
 "properties": {
 "aggregateType": {

googleapiclient/discovery_cache/documents/billingbudgets.v1.json

@@ -275,7 +275,7 @@
 }
 }
 },
-"revision": "20240609",
+"revision": "20240630",
 "rootUrl": "https://billingbudgets.googleapis.com/",
 "schemas": {
 "GoogleCloudBillingBudgetsV1Budget": {

googleapiclient/discovery_cache/documents/billingbudgets.v1beta1.json

@@ -269,7 +269,7 @@
 }
 }
 },
-"revision": "20240609",
+"revision": "20240630",
 "rootUrl": "https://billingbudgets.googleapis.com/",
 "schemas": {
 "GoogleCloudBillingBudgetsV1beta1AllUpdatesRule": {

googleapiclient/discovery_cache/documents/binaryauthorization.v1.json

@@ -510,6 +510,11 @@
 "name"
 ],
 "parameters": {
+"etag": {
+"description": "Optional. Used to prevent deleting the policy when another request has updated it since it was retrieved.",
+"location": "query",
+"type": "string"
+},
 "name": {
 "description": "Required. The name of the platform policy to delete, in the format `projects/*/platforms/*/policies/*`.",
 "location": "path",
@@ -742,7 +747,7 @@
 }
 }
 },
-"revision": "20240607",
+"revision": "20240701",
 "rootUrl": "https://binaryauthorization.googleapis.com/",
 "schemas": {
 "AdmissionRule": {
@@ -1420,6 +1425,10 @@
 "description": "Optional. A description comment about the policy.",
 "type": "string"
 },
+"etag": {
+"description": "Optional. Used to prevent updating the policy when another request has updated it since it was retrieved.",
+"type": "string"
+},
 "gkePolicy": {
 "$ref": "GkePolicy",
 "description": "Optional. GKE platform-specific policy."

googleapiclient/discovery_cache/documents/binaryauthorization.v1beta1.json

@@ -551,7 +551,7 @@
 }
 }
 },
-"revision": "20240607",
+"revision": "20240701",
 "rootUrl": "https://binaryauthorization.googleapis.com/",
 "schemas": {
 "AdmissionRule": {

googleapiclient/discovery_cache/documents/blockchainnodeengine.v1.json

@@ -487,7 +487,7 @@
 }
 }
 },
-"revision": "20240605",
+"revision": "20240626",
 "rootUrl": "https://blockchainnodeengine.googleapis.com/",
 "schemas": {
 "BlockchainNode": {

googleapiclient/discovery_cache/documents/blogger.v2.json

@@ -401,7 +401,7 @@
 }
 }
 },
-"revision": "20240617",
+"revision": "20240630",
 "rootUrl": "https://blogger.googleapis.com/",
 "schemas": {
 "Blog": {

googleapiclient/discovery_cache/documents/blogger.v3.json

@@ -1710,7 +1710,7 @@
 }
 }
 },
-"revision": "20240617",
+"revision": "20240630",
 "rootUrl": "https://blogger.googleapis.com/",
 "schemas": {
 "Blog": {

googleapiclient/discovery_cache/documents/books.v1.json

@@ -2677,7 +2677,7 @@
 }
 }
 },
-"revision": "20240604",
+"revision": "20240625",
 "rootUrl": "https://books.googleapis.com/",
 "schemas": {
 "Annotation": {

googleapiclient/discovery_cache/documents/businessprofileperformance.v1.json

@@ -417,7 +417,7 @@
 }
 }
 },
-"revision": "20240616",
+"revision": "20240630",
 "rootUrl": "https://businessprofileperformance.googleapis.com/",
 "schemas": {
 "DailyMetricTimeSeries": {

googleapiclient/discovery_cache/documents/certificatemanager.v1.json

@@ -1280,7 +1280,7 @@
 }
 }
 },
-"revision": "20240606",
+"revision": "20240624",
 "rootUrl": "https://certificatemanager.googleapis.com/",
 "schemas": {
 "AllowlistedCertificate": {

googleapiclient/discovery_cache/documents/chat.v1.json

@@ -433,7 +433,7 @@
 "type": "string"
 },
 "updateMask": {
-"description": "Required. The updated field paths, comma separated if there are multiple. Currently supported field paths: - `display_name` (Only supports changing the display name of a space with the `SPACE` type, or when also including the `space_type` mask to change a `GROUP_CHAT` space type to `SPACE`. Trying to update the display name of a `GROUP_CHAT` or a `DIRECT_MESSAGE` space results in an invalid argument error. If you receive the error message `ALREADY_EXISTS` when updating the `displayName`, try a different `displayName`. An existing space within the Google Workspace organization might already use this display name.) - `space_type` (Only supports changing a `GROUP_CHAT` space type to `SPACE`. Include `display_name` together with `space_type` in the update mask and ensure that the specified space has a non-empty display name and the `SPACE` space type. Including the `space_type` mask and the `SPACE` type in the specified space when updating the display name is optional if the existing space already has the `SPACE` type. Trying to update the space type in other ways results in an invalid argument error). `space_type` is not supported with admin access. - `space_details` - `space_history_state` (Supports [turning history on or off for the space](https://support.google.com/chat/answer/7664687) if [the organization allows users to change their history setting](https://support.google.com/a/answer/7664184). Warning: mutually exclusive with all other field paths.) `space_history_state` is not supported with admin access. - Developer Preview: `access_settings.audience` (Supports changing the [access setting](https://support.google.com/chat/answer/11971020) of a space. If no audience is specified in the access setting, the space's access setting is updated to restricted. Warning: mutually exclusive with all other field paths.) `access_settings.audience` is not supported with admin access. - Developer Preview: Supports changing the [permission settings](https://support.google.com/chat/answer/13340792) of a space, supported field paths include: `permission_settings.manage_members_and_groups`, `permission_settings.modify_space_details`, `permission_settings.toggle_history`, `permission_settings.use_at_mention_all`, `permission_settings.manage_apps`, `permission_settings.manage_webhooks`, `permission_settings.reply_messages` (Warning: mutually exclusive with all other non-permission settings field paths). `permission_settings` is not supported with admin access.",
+"description": "Required. The updated field paths, comma separated if there are multiple. Currently supported field paths: - `display_name` (Only supports changing the display name of a space with the `SPACE` type, or when also including the `space_type` mask to change a `GROUP_CHAT` space type to `SPACE`. Trying to update the display name of a `GROUP_CHAT` or a `DIRECT_MESSAGE` space results in an invalid argument error. If you receive the error message `ALREADY_EXISTS` when updating the `displayName`, try a different `displayName`. An existing space within the Google Workspace organization might already use this display name.) - `space_type` (Only supports changing a `GROUP_CHAT` space type to `SPACE`. Include `display_name` together with `space_type` in the update mask and ensure that the specified space has a non-empty display name and the `SPACE` space type. Including the `space_type` mask and the `SPACE` type in the specified space when updating the display name is optional if the existing space already has the `SPACE` type. Trying to update the space type in other ways results in an invalid argument error). `space_type` is not supported with admin access. - `space_details` - `space_history_state` (Supports [turning history on or off for the space](https://support.google.com/chat/answer/7664687) if [the organization allows users to change their history setting](https://support.google.com/a/answer/7664184). Warning: mutually exclusive with all other field paths.) `space_history_state` is not supported with admin access. - `access_settings.audience` (Supports changing the [access setting](https://support.google.com/chat/answer/11971020) of who can discover the space, join the space, and preview the messages in space. If no audience is specified in the access setting, the space's access setting is updated to private. Warning: mutually exclusive with all other field paths.) `access_settings.audience` is not supported with admin access. - Developer Preview: Supports changing the [permission settings](https://support.google.com/chat/answer/13340792) of a space, supported field paths include: `permission_settings.manage_members_and_groups`, `permission_settings.modify_space_details`, `permission_settings.toggle_history`, `permission_settings.use_at_mention_all`, `permission_settings.manage_apps`, `permission_settings.manage_webhooks`, `permission_settings.reply_messages` (Warning: mutually exclusive with all other non-permission settings field paths). `permission_settings` is not supported with admin access.",
 "format": "google-fieldmask",
 "location": "query",
 "type": "string"
@@ -453,7 +453,7 @@
 ]
 },
 "setup": {
-"description": "Creates a space and adds specified users to it. The calling user is automatically added to the space, and shouldn't be specified as a membership in the request. For an example, see [Set up a space with initial members](https://developers.google.com/workspace/chat/set-up-spaces). To specify the human members to add, add memberships with the appropriate `membership.member.name`. To add a human user, use `users/{user}`, where `{user}` can be the email address for the user. For users in the same Workspace organization `{user}` can also be the `id` for the person from the People API, or the `id` for the user in the Directory API. For example, if the People API Person profile ID for `user@example.com` is `123456789`, you can add the user to the space by setting the `membership.member.name` to `users/user@example.com` or `users/123456789`. For a named space or group chat, if the caller blocks, or is blocked by some members, or doesn't have permission to add some members, then those members aren't added to the created space. To create a direct message (DM) between the calling user and another human user, specify exactly one membership to represent the human user. If one user blocks the other, the request fails and the DM isn't created. To create a DM between the calling user and the calling app, set `Space.singleUserBotDm` to `true` and don't specify any memberships. You can only use this method to set up a DM with the calling app. To add the calling app as a member of a space or an existing DM between two human users, see [Invite or add a user or app to a space](https://developers.google.com/workspace/chat/create-members). If a DM already exists between two users, even when one user blocks the other at the time a request is made, then the existing DM is returned. Spaces with threaded replies aren't supported. If you receive the error message `ALREADY_EXISTS` when setting up a space, try a different `displayName`. An existing space within the Google Workspace organization might already use this display name. Requires [user authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user).",
+"description": "Creates a space and adds specified users to it. The calling user is automatically added to the space, and shouldn't be specified as a membership in the request. For an example, see [Set up a space with initial members](https://developers.google.com/workspace/chat/set-up-spaces). To specify the human members to add, add memberships with the appropriate `membership.member.name`. To add a human user, use `users/{user}`, where `{user}` can be the email address for the user. For users in the same Workspace organization `{user}` can also be the `id` for the person from the People API, or the `id` for the user in the Directory API. For example, if the People API Person profile ID for `user@example.com` is `123456789`, you can add the user to the space by setting the `membership.member.name` to `users/user@example.com` or `users/123456789`. To specify the Google groups to add, add memberships with the appropriate `membership.group_member.name`. To add or invite a Google group, use `groups/{group}`, where `{group}` is the `id` for the group from the Cloud Identity Groups API. For example, you can use [Cloud Identity Groups lookup API](https://cloud.google.com/identity/docs/reference/rest/v1/groups/lookup) to retrieve the ID `123456789` for group email `group@example.com`, then you can add the group to the space by setting the `membership.group_member.name` to `groups/123456789`. Group email is not supported, and Google groups can only be added as members in named spaces. For a named space or group chat, if the caller blocks, or is blocked by some members, or doesn't have permission to add some members, then those members aren't added to the created space. To create a direct message (DM) between the calling user and another human user, specify exactly one membership to represent the human user. If one user blocks the other, the request fails and the DM isn't created. To create a DM between the calling user and the calling app, set `Space.singleUserBotDm` to `true` and don't specify any memberships. You can only use this method to set up a DM with the calling app. To add the calling app as a member of a space or an existing DM between two human users, see [Invite or add a user or app to a space](https://developers.google.com/workspace/chat/create-members). If a DM already exists between two users, even when one user blocks the other at the time a request is made, then the existing DM is returned. Spaces with threaded replies aren't supported. If you receive the error message `ALREADY_EXISTS` when setting up a space, try a different `displayName`. An existing space within the Google Workspace organization might already use this display name. Requires [user authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user).",
 "flatPath": "v1/spaces:setup",
 "httpMethod": "POST",
 "id": "chat.spaces.setup",
@@ -476,7 +476,7 @@
 "members": {
 "methods": {
 "create": {
-"description": "Creates a human membership or app membership for the calling app. Creating memberships for other apps isn't supported. For an example, see [Invite or add a user or a Google Chat app to a space](https://developers.google.com/workspace/chat/create-members). 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. Requires [user authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user). To specify the member to add, set the `membership.member.name` for the human or app member. - To add the calling app to a space or a direct message between two human users, use `users/app`. Unable to add other apps to the space. - To add a human user, use `users/{user}`, where `{user}` can be the email address for the user. For users in the same Workspace organization `{user}` can also be the `id` for the person from the People API, or the `id` for the user in the Directory API. For example, if the People API Person profile ID for `user@example.com` is `123456789`, you can add the user to the space by setting the `membership.member.name` to `users/user@example.com` or `users/123456789`.",
+"description": "Creates a human membership or app membership for the calling app. Creating memberships for other apps isn't supported. For an example, see [Invite or add a user or a Google Chat app to a space](https://developers.google.com/workspace/chat/create-members). 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. Requires [user authentication](https://developers.google.com/workspace/chat/authenticate-authorize-chat-user). To specify the member to add, set the `membership.member.name` for the human or app member, or set the `membership.group_member.name` for the group member. - To add the calling app to a space or a direct message between two human users, use `users/app`. Unable to add other apps to the space. - To add a human user, use `users/{user}`, where `{user}` can be the email address for the user. For users in the same Workspace organization `{user}` can also be the `id` for the person from the People API, or the `id` for the user in the Directory API. For example, if the People API Person profile ID for `user@example.com` is `123456789`, you can add the user to the space by setting the `membership.member.name` to `users/user@example.com` or `users/123456789`. - To add or invite a Google group in a named space, use `groups/{group}`, where `{group}` is the `id` for the group from the Cloud Identity Groups API. For example, you can use [Cloud Identity Groups lookup API](https://cloud.google.com/identity/docs/reference/rest/v1/groups/lookup) to retrieve the ID `123456789` for group email `group@example.com`, then you can add or invite the group to a named space by setting the `membership.group_member.name` to `groups/123456789`. Group email is not supported, and Google groups can only be added as members in named spaces.",
 "flatPath": "v1/spaces/{spacesId}/members",
 "httpMethod": "POST",
 "id": "chat.spaces.members.create",
@@ -1241,9 +1241,35 @@
 }
 }
 },
-"revision": "20240613",
+"revision": "20240625",
 "rootUrl": "https://chat.googleapis.com/",
 "schemas": {
+"AccessSettings": {
+"description": "Represents the [access setting](https://support.google.com/chat/answer/11971020) of the space.",
+"id": "AccessSettings",
+"properties": {
+"accessState": {
+"description": "Output only. Indicates the access state of the space.",
+"enum": [
+"ACCESS_STATE_UNSPECIFIED",
+"PRIVATE",
+"DISCOVERABLE"
+],
+"enumDescriptions": [
+"Access state is unknown or not supported in this API.",
+"Space is discoverable by added or invited members or groups.",
+"Space is discoverable by the selected [target audience](https://support.google.com/a/answer/9934697), as well as added or invited members or groups."
+],
+"readOnly": true,
+"type": "string"
+},
+"audience": {
+"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. 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`.",
+"type": "string"
+}
+},
+"type": "object"
+},
 "AccessoryWidget": {
 "description": "One or more interactive widgets that appear at the bottom of a message. For details, see [Add interactive widgets at the bottom of a message](https://developers.google.com/workspace/chat/create-messages#add-accessory-widgets).",
 "id": "AccessoryWidget",
@@ -1833,7 +1859,7 @@
 },
 "common": {
 "$ref": "CommonEventObject",
-"description": "Represents information about the user's client, such as locale, host app, and platform. For Chat apps, `CommonEventObject` includes information submitted by users interacting with [dialogs](https://developers.google.com/workspace/chat/dialogs), like data entered on a card."
+"description": "Represents informatmessage_visibilityion about the user's client, such as locale, host app, and platform. For Chat apps, `CommonEventObject` includes information submitted by users interacting with [dialogs](https://developers.google.com/workspace/chat/dialogs), like data entered on a card."
 },
 "configCompleteRedirectUrl": {
 "description": "The URL the Chat app should redirect the user to after they have completed an authorization or configuration flow outside of Google Chat. For more information, see [Connect a Chat app with other services & tools](https://developers.google.com/workspace/chat/connect-web-services-tools).",
@@ -2282,7 +2308,7 @@
 "type": "object"
 },
 "GoogleAppsCardV1Column": {
-"description": "A column. [Google Workspace Add-ons and Chat apps](https://developers.google.com/workspace/extend): Columns for Google Workspace Add-ons are in Developer Preview.",
+"description": "A column. [Google Workspace Add-ons and Chat apps](https://developers.google.com/workspace/extend)",
 "id": "GoogleAppsCardV1Column",
 "properties": {
 "horizontalAlignment": {
@@ -3039,7 +3065,7 @@
 "type": "object"
 },
 "GoogleAppsCardV1Widgets": {
-"description": "The supported widgets that you can include in a column. [Google Workspace Add-ons and Chat apps](https://developers.google.com/workspace/extend): Columns for Google Workspace Add-ons are in Developer Preview.",
+"description": "The supported widgets that you can include in a column. [Google Workspace Add-ons and Chat apps](https://developers.google.com/workspace/extend)",
 "id": "GoogleAppsCardV1Widgets",
 "properties": {
 "buttonList": {
@@ -3461,7 +3487,7 @@
 },
 "groupMember": {
 "$ref": "Group",
-"description": "The Google Group the membership corresponds to. Only supports read operations. Other operations, like creating or updating a membership, aren't currently supported."
+"description": "The Google Group the membership corresponds to."
 },
 "member": {
 "$ref": "User",
@@ -3982,7 +4008,7 @@
 "id": "SetUpSpaceRequest",
 "properties": {
 "memberships": {
-"description": "Optional. The Google Chat users to invite to join the space. Omit the calling user, as they are added automatically. The set currently allows up to 20 memberships (in addition to the caller). For human membership, the `Membership.member` field must contain a `user` with `name` populated (format: `users/{user}`) and `type` set to `User.Type.HUMAN`. You can only add human users when setting up a space (adding Chat apps is only supported for direct message setup with the calling app). You can also add members using the user's email as an alias for {user}. For example, the `user.name` can be `users/example@gmail.com`. To invite Gmail users or users from external Google Workspace domains, user's email must be used for `{user}`. Optional when setting `Space.spaceType` to `SPACE`. Required when setting `Space.spaceType` to `GROUP_CHAT`, along with at least two memberships. Required when setting `Space.spaceType` to `DIRECT_MESSAGE` with a human user, along with exactly one membership. Must be empty when creating a 1:1 conversation between a human and the calling Chat app (when setting `Space.spaceType` to `DIRECT_MESSAGE` and `Space.singleUserBotDm` to `true`).",
+"description": "Optional. The Google Chat users or groups to invite to join the space. Omit the calling user, as they are added automatically. The set currently allows up to 20 memberships (in addition to the caller). For human membership, the `Membership.member` field must contain a `user` with `name` populated (format: `users/{user}`) and `type` set to `User.Type.HUMAN`. You can only add human users when setting up a space (adding Chat apps is only supported for direct message setup with the calling app). You can also add members using the user's email as an alias for {user}. For example, the `user.name` can be `users/example@gmail.com`. To invite Gmail users or users from external Google Workspace domains, user's email must be used for `{user}`. For Google group membership, the `Membership.group_member` field must contain a `group` with `name` populated (format `groups/{group}`). You can only add Google groups when setting `Space.spaceType` to `SPACE`. Optional when setting `Space.spaceType` to `SPACE`. Required when setting `Space.spaceType` to `GROUP_CHAT`, along with at least two memberships. Required when setting `Space.spaceType` to `DIRECT_MESSAGE` with a human user, along with exactly one membership. Must be empty when creating a 1:1 conversation between a human and the calling Chat app (when setting `Space.spaceType` to `DIRECT_MESSAGE` and `Space.singleUserBotDm` to `true`).",
 "items": {
 "$ref": "Membership"
 },
@@ -4053,6 +4079,10 @@
 "description": "A space in Google Chat. Spaces are conversations between two or more users or 1:1 messages between a user and a Chat app.",
 "id": "Space",
 "properties": {
+"accessSettings": {
+"$ref": "AccessSettings",
+"description": "Optional. Specifies the [access setting](https://support.google.com/chat/answer/11971020) of the space. Only populated when the `space_type` is `SPACE`."
+},
 "adminInstalled": {
 "description": "Output only. For direct message (DM) spaces with a Chat app, whether the space was created by a Google Workspace administrator. Administrators can install and set up a direct message with a Chat app on behalf of users in their organization. To support admin install, your Chat app must feature direct messaging.",
 "readOnly": true,
@@ -4134,6 +4164,11 @@
 ],
 "type": "string"
 },
+"spaceUri": {
+"description": "Output only. The URI for a user to access the space.",
+"readOnly": true,
+"type": "string"
+},
 "threaded": {
 "deprecated": true,
 "description": "Output only. Deprecated: Use `spaceThreadingState` instead. Whether messages are threaded in this space.",