google-api-python-client 2.153.0__py2.py3-none-any.whl → 2.154.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/healthcare.v1.json

@@ -3342,7 +3342,7 @@
 "fhir": {
 "methods": {
 "Binary-create": {
-"description": "Creates a FHIR Binary resource. This method can be used to create a Binary resource either by using one of the accepted FHIR JSON content types, or as a raw data stream. If a resource is created with this method using the FHIR content type this method's behavior is the same as [`fhir.create`](https://cloud.google.com/healthcare-api/docs/reference/rest/v1/projects.locations.datasets.fhirStores.fhir/create). If a resource type other than Binary is used in the request it's treated in the same way as non-FHIR data (e.g., images, zip archives, pdf files, documents). When a non-FHIR content type is used in the request, a Binary resource will be generated, and the uploaded data will be stored in the `content` field (`DSTU2` and `STU3`), or the `data` field (`R4`). The Binary resource's `contentType` will be filled in using the value of the `Content-Type` header, and the `securityContext` field (not present in `DSTU2`) will be populated from the `X-Security-Context` header if it exists. At this time `securityContext` has no special behavior in the Cloud Healthcare API. Note: the limit on data ingested through this method is 2 GB. For best performance, use a non-FHIR data type instead of wrapping the data in a Binary resource. Some of the Healthcare API features, such as [exporting to BigQuery](https://cloud.google.com/healthcare-api/docs/how-tos/fhir-export-bigquery) or [Pub/Sub notifications](https://cloud.google.com/healthcare-api/docs/fhir-pubsub#behavior_when_a_fhir_resource_is_too_large_or_traffic_is_high) with full resource content, do not support Binary resources that are larger than 10 MB. In these cases the resource's `data` field will be omitted. Instead, the \"http://hl7.org/fhir/StructureDefinition/data-absent-reason\" extension will be present to indicate that including the data is `unsupported`. On success, an empty `201 Created` response is returned. The newly created resource's ID and version are returned in the Location header. Using `Prefer: representation=resource` is not allowed for this method. The definition of the Binary REST API can be found at https://hl7.org/fhir/binary.html#rest.",
+"description": "Creates a FHIR Binary resource. This method can be used to create a Binary resource either by using one of the accepted FHIR JSON content types, or as a raw data stream. If a resource is created with this method using the FHIR content type this method's behavior is the same as [`fhir.create`](https://cloud.google.com/healthcare-api/docs/reference/rest/v1/projects.locations.datasets.fhirStores.fhir/create). If a resource type other than Binary is used in the request it's treated in the same way as non-FHIR data (e.g., images, zip archives, pdf files, documents). When a non-FHIR content type is used in the request, a Binary resource will be generated, and the uploaded data will be stored in the `content` field (`DSTU2` and `STU3`), or the `data` field (`R4`). The Binary resource's `contentType` will be filled in using the value of the `Content-Type` header, and the `securityContext` field (not present in `DSTU2`) will be populated from the `X-Security-Context` header if it exists. At this time `securityContext` has no special behavior in the Cloud Healthcare API. Note: the limit on data ingested through this method is 1 GB. For best performance, use a non-FHIR data type instead of wrapping the data in a Binary resource. Some of the Healthcare API features, such as [exporting to BigQuery](https://cloud.google.com/healthcare-api/docs/how-tos/fhir-export-bigquery) or [Pub/Sub notifications](https://cloud.google.com/healthcare-api/docs/fhir-pubsub#behavior_when_a_fhir_resource_is_too_large_or_traffic_is_high) with full resource content, do not support Binary resources that are larger than 10 MB. In these cases the resource's `data` field will be omitted. Instead, the \"http://hl7.org/fhir/StructureDefinition/data-absent-reason\" extension will be present to indicate that including the data is `unsupported`. On success, an empty `201 Created` response is returned. The newly created resource's ID and version are returned in the Location header. Using `Prefer: representation=resource` is not allowed for this method. The definition of the Binary REST API can be found at https://hl7.org/fhir/binary.html#rest.",
 "flatPath": "v1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/fhirStores/{fhirStoresId}/fhir/Binary",
 "httpMethod": "POST",
 "id": "healthcare.projects.locations.datasets.fhirStores.fhir.Binary-create",
@@ -4783,7 +4783,7 @@
 }
 }
 },
-"revision": "20241017",
+"revision": "20241107",
 "rootUrl": "https://healthcare.googleapis.com/",
 "schemas": {
 "ActivateConsentRequest": {
@@ -5097,7 +5097,7 @@
 "id": "CharacterMaskConfig",
 "properties": {
 "maskingCharacter": {
-"description": "Character to mask the sensitive values. If not supplied, defaults to \"*\".",
+"description": "Optional. Character to mask the sensitive values. If not supplied, defaults to \"*\".",
 "type": "string"
 }
 },
@@ -5410,7 +5410,7 @@
 "properties": {
 "config": {
 "$ref": "DeidentifyConfig",
-"description": "The configuration to use when de-identifying resources that are added to this store."
+"description": "Optional. The configuration to use when de-identifying resources that are added to this store."
 },
 "store": {
 "description": "Optional. The full resource name of a Cloud Healthcare FHIR store, for example, `projects/{project_id}/locations/{location_id}/datasets/{dataset_id}/fhirStores/{fhir_store_id}`.",
@@ -5425,22 +5425,22 @@
 "properties": {
 "dicom": {
 "$ref": "DicomConfig",
-"description": "Configures de-id of application/DICOM content."
+"description": "Optional. Configures de-id of application/DICOM content."
 },
 "fhir": {
 "$ref": "FhirConfig",
-"description": "Configures de-id of application/FHIR content."
+"description": "Optional. Configures de-id of application/FHIR content."
 },
 "image": {
 "$ref": "ImageConfig",
-"description": "Configures de-identification of image pixels wherever they are found in the source_dataset."
+"description": "Optional. Configures de-identification of image pixels wherever they are found in the source_dataset."
 },
 "text": {
 "$ref": "TextConfig",
-"description": "Configures de-identification of text wherever it is found in the source_dataset."
+"description": "Optional. Configures de-identification of text wherever it is found in the source_dataset."
 },
 "useRegionalDataProcessing": {
-"description": "Ensures in-flight data remains in the region of origin during de-identification. The default value is false. Using this option results in a significant reduction of throughput, and is not compatible with `LOCATION` or `ORGANIZATION_NAME` infoTypes. `LOCATION` must be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.",
+"description": "Optional. Ensures in-flight data remains in the region of origin during de-identification. The default value is false. Using this option results in a significant reduction of throughput, and is not compatible with `LOCATION` or `ORGANIZATION_NAME` infoTypes. `LOCATION` must be excluded within TextConfig, and must also be excluded within ImageConfig if image redaction is required.",
 "type": "boolean"
 }
 },
@@ -5552,7 +5552,7 @@
 "description": "List of tags to remove. Keep all other tags."
 },
 "skipIdRedaction": {
-"description": "If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: \"Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity.\" http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html",
+"description": "Optional. If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: \"Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity.\" http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html",
 "type": "boolean"
 }
 },
@@ -5934,11 +5934,11 @@
 "id": "FhirConfig",
 "properties": {
 "defaultKeepExtensions": {
-"description": "The behaviour for handling FHIR extensions that aren't otherwise specified for de-identification. If true, all extensions are preserved during de-identification by default. If false or unspecified, all extensions are removed during de-identification by default.",
+"description": "Optional. The behaviour for handling FHIR extensions that aren't otherwise specified for de-identification. If true, all extensions are preserved during de-identification by default. If false or unspecified, all extensions are removed during de-identification by default.",
 "type": "boolean"
 },
 "fieldMetadataList": {
-"description": "Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata is passed through to the output dataset unmodified. All extensions will be processed according to `default_keep_extensions`.",
+"description": "Optional. Specifies FHIR paths to match and how to transform them. Any field that is not matched by a FieldMetadata is passed through to the output dataset unmodified. All extensions will be processed according to `default_keep_extensions`.",
 "items": {
 "$ref": "FieldMetadata"
 },
@@ -6137,7 +6137,7 @@
 "id": "FieldMetadata",
 "properties": {
 "action": {
-"description": "Deidentify action for one field.",
+"description": "Optional. Deidentify action for one field.",
 "enum": [
 "ACTION_UNSPECIFIED",
 "TRANSFORM",
@@ -6145,7 +6145,7 @@
 "DO_NOT_TRANSFORM"
 ],
 "enumDescriptions": [
-"No action specified.",
+"No action specified. Defaults to DO_NOT_TRANSFORM.",
 "Transform the entire field.",
 "Inspect and transform any found PHI.",
 "Do not transform."
@@ -6153,7 +6153,7 @@
 "type": "string"
 },
 "paths": {
-"description": "List of paths to FHIR fields to be redacted. Each path is a period-separated list where each component is either a field name or FHIR type name, for example: Patient, HumanName. For \"choice\" types (those defined in the FHIR spec with the form: field[x]) we use two separate components. For example, \"deceasedAge.unit\" is matched by \"Deceased.Age.unit\". Supported types are: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml.",
+"description": "Optional. List of paths to FHIR fields to be redacted. Each path is a period-separated list where each component is either a field name or FHIR type name, for example: Patient, HumanName. For \"choice\" types (those defined in the FHIR spec with the form: field[x]) we use two separate components. For example, \"deceasedAge.unit\" is matched by \"Deceased.Age.unit\". Supported types are: AdministrativeGenderCode, Base64Binary, Boolean, Code, Date, DateTime, Decimal, HumanName, Id, Instant, Integer, LanguageCode, Markdown, Oid, PositiveInt, String, UnsignedInt, Uri, Uuid, Xhtml.",
 "items": {
 "type": "string"
 },
@@ -6572,7 +6572,7 @@
 "id": "ImageConfig",
 "properties": {
 "textRedactionMode": {
-"description": "Determines how to redact text from image.",
+"description": "Optional. Determines how to redact text from image.",
 "enum": [
 "TEXT_REDACTION_MODE_UNSPECIFIED",
 "REDACT_ALL_TEXT",
@@ -6680,7 +6680,7 @@
 "description": "Config for date shift."
 },
 "infoTypes": {
-"description": "InfoTypes to apply this transformation to. If this is not specified, the transformation applies to any info_type.",
+"description": "Optional. InfoTypes to apply this transformation to. If this is not specified, the transformation applies to any info_type.",
 "items": {
 "type": "string"
 },
@@ -7949,7 +7949,7 @@
 "id": "TagFilterList",
 "properties": {
 "tags": {
-"description": "Tags to be filtered. Tags must be DICOM Data Elements, File Meta Elements, or Directory Structuring Elements, as defined at: http://dicom.nema.org/medical/dicom/current/output/html/part06.html#table_6-1,. They may be provided by \"Keyword\" or \"Tag\". For example \"PatientID\", \"00100010\".",
+"description": "Optional. Tags to be filtered. Tags must be DICOM Data Elements, File Meta Elements, or Directory Structuring Elements, as defined at: http://dicom.nema.org/medical/dicom/current/output/html/part06.html#table_6-1,. They may be provided by \"Keyword\" or \"Tag\". For example \"PatientID\", \"00100010\".",
 "items": {
 "type": "string"
 },
@@ -7990,21 +7990,21 @@
 "id": "TextConfig",
 "properties": {
 "additionalTransformations": {
-"description": "Transformations to apply to the detected data, overridden by `exclude_info_types`.",
+"description": "Optional. Transformations to apply to the detected data, overridden by `exclude_info_types`.",
 "items": {
 "$ref": "InfoTypeTransformation"
 },
 "type": "array"
 },
 "excludeInfoTypes": {
-"description": "InfoTypes to skip transforming, overriding `additional_transformations`.",
+"description": "Optional. InfoTypes to skip transforming, overriding `additional_transformations`.",
 "items": {
 "type": "string"
 },
 "type": "array"
 },
 "transformations": {
-"description": "The transformations to apply to the detected data. Deprecated. Use `additional_transformations` instead.",
+"description": "Optional. The transformations to apply to the detected data. Deprecated. Use `additional_transformations` instead.",
 "items": {
 "$ref": "InfoTypeTransformation"
 },

googleapiclient/discovery_cache/documents/healthcare.v1beta1.json

@@ -4079,7 +4079,7 @@
 "fhir": {
 "methods": {
 "Binary-create": {
-"description": "Creates a FHIR Binary resource. This method can be used to create a Binary resource either by using one of the accepted FHIR JSON content types, or as a raw data stream. If a resource is created with this method using the FHIR content type this method's behavior is the same as [`fhir.create`](https://cloud.google.com/healthcare-api/docs/reference/rest/v1/projects.locations.datasets.fhirStores.fhir/create). If a resource type other than Binary is used in the request it's treated in the same way as non-FHIR data (e.g., images, zip archives, pdf files, documents). When a non-FHIR content type is used in the request, a Binary resource will be generated, and the uploaded data will be stored in the `content` field (`DSTU2` and `STU3`), or the `data` field (`R4`). The Binary resource's `contentType` will be filled in using the value of the `Content-Type` header, and the `securityContext` field (not present in `DSTU2`) will be populated from the `X-Security-Context` header if it exists. At this time `securityContext` has no special behavior in the Cloud Healthcare API. Note: the limit on data ingested through this method is 2 GB. For best performance, use a non-FHIR data type instead of wrapping the data in a Binary resource. Some of the Healthcare API features, such as [exporting to BigQuery](https://cloud.google.com/healthcare-api/docs/how-tos/fhir-export-bigquery) or [Pub/Sub notifications](https://cloud.google.com/healthcare-api/docs/fhir-pubsub#behavior_when_a_fhir_resource_is_too_large_or_traffic_is_high) with full resource content, do not support Binary resources that are larger than 10 MB. In these cases the resource's `data` field will be omitted. Instead, the \"http://hl7.org/fhir/StructureDefinition/data-absent-reason\" extension will be present to indicate that including the data is `unsupported`. On success, an empty `201 Created` response is returned. The newly created resource's ID and version are returned in the Location header. Using `Prefer: representation=resource` is not allowed for this method. The definition of the Binary REST API can be found at https://hl7.org/fhir/binary.html#rest.",
+"description": "Creates a FHIR Binary resource. This method can be used to create a Binary resource either by using one of the accepted FHIR JSON content types, or as a raw data stream. If a resource is created with this method using the FHIR content type this method's behavior is the same as [`fhir.create`](https://cloud.google.com/healthcare-api/docs/reference/rest/v1/projects.locations.datasets.fhirStores.fhir/create). If a resource type other than Binary is used in the request it's treated in the same way as non-FHIR data (e.g., images, zip archives, pdf files, documents). When a non-FHIR content type is used in the request, a Binary resource will be generated, and the uploaded data will be stored in the `content` field (`DSTU2` and `STU3`), or the `data` field (`R4`). The Binary resource's `contentType` will be filled in using the value of the `Content-Type` header, and the `securityContext` field (not present in `DSTU2`) will be populated from the `X-Security-Context` header if it exists. At this time `securityContext` has no special behavior in the Cloud Healthcare API. Note: the limit on data ingested through this method is 1 GB. For best performance, use a non-FHIR data type instead of wrapping the data in a Binary resource. Some of the Healthcare API features, such as [exporting to BigQuery](https://cloud.google.com/healthcare-api/docs/how-tos/fhir-export-bigquery) or [Pub/Sub notifications](https://cloud.google.com/healthcare-api/docs/fhir-pubsub#behavior_when_a_fhir_resource_is_too_large_or_traffic_is_high) with full resource content, do not support Binary resources that are larger than 10 MB. In these cases the resource's `data` field will be omitted. Instead, the \"http://hl7.org/fhir/StructureDefinition/data-absent-reason\" extension will be present to indicate that including the data is `unsupported`. On success, an empty `201 Created` response is returned. The newly created resource's ID and version are returned in the Location header. Using `Prefer: representation=resource` is not allowed for this method. The definition of the Binary REST API can be found at https://hl7.org/fhir/binary.html#rest.",
 "flatPath": "v1beta1/projects/{projectsId}/locations/{locationsId}/datasets/{datasetsId}/fhirStores/{fhirStoresId}/fhir/Binary",
 "httpMethod": "POST",
 "id": "healthcare.projects.locations.datasets.fhirStores.fhir.Binary-create",
@@ -5858,7 +5858,7 @@
 }
 }
 },
-"revision": "20241009",
+"revision": "20241107",
 "rootUrl": "https://healthcare.googleapis.com/",
 "schemas": {
 "AccessDeterminationLogConfig": {

googleapiclient/discovery_cache/documents/integrations.v1.json

@@ -4497,7 +4497,7 @@
 }
 }
 },
-"revision": "20241028",
+"revision": "20241111",
 "rootUrl": "https://integrations.googleapis.com/",
 "schemas": {
 "CrmlogErrorCode": {
@@ -9444,6 +9444,7 @@ false
 "PREVIEW",
 "GA",
 "DEPRECATED",
+"TEST",
 "PRIVATE_PREVIEW"
 ],
 "enumDescriptions": [
@@ -9451,6 +9452,7 @@ false
 "PREVIEW.",
 "GA.",
 "DEPRECATED.",
+"TEST.",
 "PRIVATE_PREVIEW."
 ],
 "readOnly": true,

googleapiclient/discovery_cache/documents/language.v1beta2.json

@@ -246,7 +246,7 @@
 }
 }
 },
-"revision": "20241103",
+"revision": "20241110",
 "rootUrl": "https://language.googleapis.com/",
 "schemas": {
 "AnalyzeEntitiesRequest": {
@@ -1361,7 +1361,7 @@
 },
 "sentiment": {
 "$ref": "Sentiment",
-"description": "For calls to AnalyzeEntitySentimentRequest or if AnnotateTextRequest.Features.extract_entity_sentiment is set to true, this field will contain the aggregate sentiment expressed for this entity in the provided document."
+"description": "For calls to AnalyzeEntitySentiment or if AnnotateTextRequest.Features.extract_entity_sentiment is set to true, this field will contain the aggregate sentiment expressed for this entity in the provided document."
 },
 "type": {
 "description": "The entity type.",
@@ -1406,7 +1406,7 @@
 "properties": {
 "sentiment": {
 "$ref": "Sentiment",
-"description": "For calls to AnalyzeEntitySentimentRequest or if AnnotateTextRequest.Features.extract_entity_sentiment is set to true, this field will contain the sentiment expressed for this mention of the entity in the provided document."
+"description": "For calls to AnalyzeEntitySentiment or if AnnotateTextRequest.Features.extract_entity_sentiment is set to true, this field will contain the sentiment expressed for this mention of the entity in the provided document."
 },
 "text": {
 "$ref": "TextSpan",
@@ -2540,7 +2540,7 @@
 "properties": {
 "sentiment": {
 "$ref": "Sentiment",
-"description": "For calls to AnalyzeSentimentRequest or if AnnotateTextRequest.Features.extract_document_sentiment is set to true, this field will contain the sentiment for the sentence."
+"description": "For calls to AnalyzeSentiment or if AnnotateTextRequest.Features.extract_document_sentiment is set to true, this field will contain the sentiment for the sentence."
 },
 "text": {
 "$ref": "TextSpan",

googleapiclient/discovery_cache/documents/language.v2.json

@@ -208,7 +208,7 @@
 }
 }
 },
-"revision": "20241103",
+"revision": "20241110",
 "rootUrl": "https://language.googleapis.com/",
 "schemas": {
 "AnalyzeEntitiesRequest": {
@@ -250,7 +250,7 @@
 "type": "array"
 },
 "languageCode": {
-"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language field for more details.",
+"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language_code field for more details.",
 "type": "string"
 },
 "languageSupported": {
@@ -296,7 +296,7 @@
 "description": "The overall sentiment of the input document."
 },
 "languageCode": {
-"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language field for more details.",
+"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language_code field for more details.",
 "type": "string"
 },
 "languageSupported": {
@@ -383,14 +383,14 @@
 "description": "The overall sentiment for the document. Populated if the user enables AnnotateTextRequest.Features.extract_document_sentiment."
 },
 "entities": {
-"description": "Entities, along with their semantic information, in the input document. Populated if the user enables AnnotateTextRequest.Features.extract_entities or AnnotateTextRequest.Features.extract_entity_sentiment.",
+"description": "Entities, along with their semantic information, in the input document. Populated if the user enables AnnotateTextRequest.Features.extract_entities .",
 "items": {
 "$ref": "Entity"
 },
 "type": "array"
 },
 "languageCode": {
-"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language field for more details.",
+"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language_code field for more details.",
 "type": "string"
 },
 "languageSupported": {
@@ -458,7 +458,7 @@
 "type": "array"
 },
 "languageCode": {
-"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language field for more details.",
+"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language_code field for more details.",
 "type": "string"
 },
 "languageSupported": {
@@ -977,7 +977,7 @@
 },
 "sentiment": {
 "$ref": "Sentiment",
-"description": "For calls to AnalyzeEntitySentimentRequest or if AnnotateTextRequest.Features.extract_entity_sentiment is set to true, this field will contain the aggregate sentiment expressed for this entity in the provided document."
+"description": "For calls to AnalyzeEntitySentiment this field will contain the aggregate sentiment expressed for this entity in the provided document."
 },
 "type": {
 "description": "The entity type.",
@@ -1027,7 +1027,7 @@
 },
 "sentiment": {
 "$ref": "Sentiment",
-"description": "For calls to AnalyzeEntitySentimentRequest or if AnnotateTextRequest.Features.extract_entity_sentiment is set to true, this field will contain the sentiment expressed for this mention of the entity in the provided document."
+"description": "For calls to AnalyzeEntitySentiment this field will contain the sentiment expressed for this mention of the entity in the provided document."
 },
 "text": {
 "$ref": "TextSpan",
@@ -1500,7 +1500,7 @@
 "id": "ModerateTextResponse",
 "properties": {
 "languageCode": {
-"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language field for more details.",
+"description": "The language of the text, which will be the same as the language specified in the request or, if not specified, the automatically-detected language. See Document.language_code field for more details.",
 "type": "string"
 },
 "languageSupported": {
@@ -1916,7 +1916,7 @@
 "properties": {
 "sentiment": {
 "$ref": "Sentiment",
-"description": "For calls to AnalyzeSentimentRequest or if AnnotateTextRequest.Features.extract_document_sentiment is set to true, this field will contain the sentiment for the sentence."
+"description": "For calls to AnalyzeSentiment or if AnnotateTextRequest.Features.extract_document_sentiment is set to true, this field will contain the sentiment for the sentence."
 },
 "text": {
 "$ref": "TextSpan",

googleapiclient/discovery_cache/documents/looker.v1.json

@@ -731,7 +731,7 @@
 }
 }
 },
-"revision": "20241016",
+"revision": "20241106",
 "rootUrl": "https://looker.googleapis.com/",
 "schemas": {
 "AdminSettings": {
@@ -1222,7 +1222,7 @@
 },
 "userMetadata": {
 "$ref": "UserMetadata",
-"description": "User metadata."
+"description": "Optional. User metadata."
 }
 },
 "type": "object"

googleapiclient/discovery_cache/documents/merchantapi.accounts_v1beta.json

@@ -708,7 +708,7 @@
 "onlineReturnPolicies": {
 "methods": {
 "get": {
-"description": "Gets an existing return policy.",
+"description": "Gets an existing return policy for a given merchant.",
 "flatPath": "accounts/v1beta/accounts/{accountsId}/onlineReturnPolicies/{onlineReturnPoliciesId}",
 "httpMethod": "GET",
 "id": "merchantapi.accounts.onlineReturnPolicies.get",
@@ -733,7 +733,7 @@
 ]
 },
 "list": {
-"description": "Lists all existing return policies.",
+"description": "Lists all existing return policies for a given merchant.",
 "flatPath": "accounts/v1beta/accounts/{accountsId}/onlineReturnPolicies",
 "httpMethod": "GET",
 "id": "merchantapi.accounts.onlineReturnPolicies.list",
@@ -1417,7 +1417,7 @@
 }
 }
 },
-"revision": "20241104",
+"revision": "20241115",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "Accepted": {
@@ -1671,7 +1671,7 @@
 "type": "object"
 },
 "BusinessInfo": {
-"description": "Collection of information related to a business.",
+"description": "The `BusinessInfo` message contains essential information about a merchant's business. This message captures key business details such as physical address, customer service contacts, and region-specific identifiers.",
 "id": "BusinessInfo",
 "properties": {
 "address": {
@@ -2060,7 +2060,7 @@
 "type": "object"
 },
 "Homepage": {
-"description": "A store's homepage.",
+"description": "The `Homepage` message represents a merchant's store homepage within the system. A merchant's homepage is the primary domain where customers interact with their store. The homepage can be claimed and verified as a proof of ownership and allows the merchant to unlock features that require a verified website. For more information, see [Understanding online store URL verification](//support.google.com/merchants/answer/176793).",
 "id": "Homepage",
 "properties": {
 "claimed": {
@@ -2418,7 +2418,7 @@ false
 "type": "boolean"
 },
 "countries": {
-"description": "The countries of sale where the return policy applies. The values must be a valid 2 letter ISO 3166 code.",
+"description": "Required. The countries of sale where the return policy applies. The values must be a valid 2 letter ISO 3166 code.",
 "items": {
 "type": "string"
 },
@@ -2442,7 +2442,7 @@ false
 "type": "array"
 },
 "label": {
-"description": "This field represents the unique user-defined label of the return policy. It is important to note that the same label cannot be used in different return policies for the same country. Unless a product specifies a specific label attribute, policies will be automatically labeled as 'default'. To assign a custom return policy to certain product groups, follow the instructions provided in the [Return policy label] (https://support.google.com/merchants/answer/9445425). The label can contain up to 50 characters.",
+"description": "Required. This field represents the unique user-defined label of the return policy. It is important to note that the same label cannot be used in different return policies for the same country. Unless a product specifies a specific label attribute, policies will be automatically labeled as 'default'. To assign a custom return policy to certain product groups, follow the instructions provided in the [Return policy label] (https://support.google.com/merchants/answer/9445425). The label can contain up to 50 characters.",
 "type": "string"
 },
 "name": {
@@ -2487,7 +2487,7 @@ false
 "type": "string"
 },
 "returnPolicyUri": {
-"description": "The return policy uri. This can used by Google to do a sanity check for the policy. It must be a valid URL.",
+"description": "Required. The return policy uri. This can used by Google to do a sanity check for the policy. It must be a valid URL.",
 "type": "string"
 },
 "returnShippingFee": {
@@ -2980,7 +2980,7 @@ false
 "description": "Fixed return shipping fee amount. This value is only applicable when type is `FIXED`. We will treat the return shipping fee as free if type is `FIXED` and this value is not set."
 },
 "type": {
-"description": "Type of return shipping fee.",
+"description": "Required. Type of return shipping fee.",
 "enum": [
 "TYPE_UNSPECIFIED",
 "FIXED",
@@ -3429,7 +3429,7 @@ false
 "type": "object"
 },
 "Warehouse": {
-"description": "A fulfillment warehouse, which stores and handles inventory. Next tag: 7",
+"description": "A fulfillment warehouse, which stores and handles inventory.",
 "id": "Warehouse",
 "properties": {
 "businessDayConfig": {

googleapiclient/discovery_cache/documents/merchantapi.datasources_v1beta.json

@@ -321,7 +321,7 @@
 }
 }
 },
-"revision": "20241101",
+"revision": "20241112",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "DataSource": {
@@ -499,7 +499,7 @@
 "type": "string"
 },
 "password": {
-"description": "Optional. An optional password for fetch url. Used for [submitting data sources through SFTP](https://support.google.com/merchants/answer/13813117).",
+"description": "Optional. An optional password for fetch_uri. Used for [submitting data sources through SFTP](https://support.google.com/merchants/answer/13813117).",
 "type": "string"
 },
 "timeOfDay": {
@@ -511,7 +511,7 @@
 "type": "string"
 },
 "username": {
-"description": "Optional. An optional user name for fetch url. Used for [submitting data sources through SFTP](https://support.google.com/merchants/answer/13813117).",
+"description": "Optional. An optional user name for fetch_uri. Used for [submitting data sources through SFTP](https://support.google.com/merchants/answer/13813117).",
 "type": "string"
 }
 },

googleapiclient/discovery_cache/documents/merchantapi.inventories_v1beta.json

@@ -300,7 +300,7 @@
 }
 }
 },
-"revision": "20241109",
+"revision": "20241115",
 "rootUrl": "https://merchantapi.googleapis.com/",
 "schemas": {
 "CustomAttribute": {
@@ -605,7 +605,7 @@ false
 "type": "object"
 },
 "RegionalInventory": {
-"description": "Regional inventory information for the product. Represents specific information like price and availability for a given product in a specific `region`.For a list of all accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/9698880).",
+"description": "Regional inventory information for the product. Represents specific information like price and availability for a given product in a specific `region`. For a list of all accepted attribute values, see the [regional product inventory data specification](https://support.google.com/merchants/answer/9698880).",
 "id": "RegionalInventory",
 "properties": {
 "account": {