---
title: "POST /v2/{+attributesConfig}:addCatalogAttribute"
method: POST
path: "/v2/{+attributesConfig}:addCatalogAttribute"
tags: ["projects"]
---

# POST /v2/{+attributesConfig}:addCatalogAttribute

`POST /v2/{+attributesConfig}:addCatalogAttribute`

Adds the specified CatalogAttribute to the AttributesConfig. If the CatalogAttribute to add already exists, an ALREADY_EXISTS error is returned.

## Path parameters

- `attributesConfig` string, required

## Request body

- GoogleCloudRetailV2AddCatalogAttributeRequest — Request for CatalogService.AddCatalogAttribute method.
  - `catalogAttribute` GoogleCloudRetailV2CatalogAttribute — Catalog level attribute config for an attribute. For example, if customers want to enable/disable facet for a specific attribute.
    - `dynamicFacetableOption` 'DYNAMIC_FACETABLE_OPTION_UNSPECIFIED' | 'DYNAMIC_FACETABLE_ENABLED' | 'DYNAMIC_FACETABLE_DISABLED' — If DYNAMIC_FACETABLE_ENABLED, attribute values are available for dynamic facet. Could only be DYNAMIC_FACETABLE_DISABLED if CatalogAttribute.indexable_option is INDEXABLE_DISABLED. Otherwise, an INVALID_ARGUMENT error is returned. Must be specified, otherwise throws INVALID_FORMAT error.
    - `facetConfig` GoogleCloudRetailV2CatalogAttributeFacetConfig — Possible options for the facet that corresponds to the current attribute config.
      - `ignoredFacetValues` GoogleCloudRetailV2CatalogAttributeFacetConfigIgnoredFacetValues[] — Each instance represents a list of attribute values to ignore as facet values for a specific time range. The maximum number of instances per CatalogAttribute is 25.
        - `startTime` string, google-datetime — Time range for the current list of facet values to ignore. If multiple time ranges are specified for an facet value for the current attribute, consider all of them. If both are empty, ignore always. If start time and end time are set, then start time must be before end time. If start time is not empty and end time is empty, then will ignore these facet values after the start time.
        - `values` string[] — List of facet values to ignore for the following time range. The facet values are the same as the attribute values. There is a limit of 10 values per instance of IgnoredFacetValues. Each value can have at most 128 characters.
        - `endTime` string, google-datetime — If start time is empty and end time is not empty, then ignore these facet values before end time.
      - `mergedFacet` GoogleCloudRetailV2CatalogAttributeFacetConfigMergedFacet — The current facet key (i.e. attribute config) maps into the merged_facet_key. A facet key can have at most one child. The current facet key and the merged facet key need both to be textual custom attributes or both numerical custom attributes (same type).
        - `mergedFacetKey` string — The merged facet key should be a valid facet key that is different than the facet key of the current catalog attribute. We refer this is merged facet key as the child of the current catalog attribute. This merged facet key can't be a parent of another facet key (i.e. no directed path of length 2). This merged facet key needs to be either a textual custom attribute or a numerical custom attribute.
      - `rerankConfig` GoogleCloudRetailV2CatalogAttributeFacetConfigRerankConfig — Options to rerank based on facet values engaged by the user for the current key. That key needs to be a custom textual key and facetable. To use this control, you also need to pass all the facet keys engaged by the user in the request using the field [SearchRequest.FacetSpec]. In particular, if you don't pass the facet keys engaged that you want to rerank on, this control won't be effective. Moreover, to obtain better results, the facet values that you want to rerank on should be close to English (ideally made of words, underscores, and spaces).
        - `rerankFacet` boolean — If set to true, then we also rerank the dynamic facets based on the facet values engaged by the user for the current attribute key during serving.
        - `facetValues` string[] — If empty, rerank on all facet values for the current key. Otherwise, will rerank on the facet values from this list only.
      - `facetIntervals` GoogleCloudRetailV2Interval[] — If you don't set the facet SearchRequest.FacetSpec.FacetKey.intervals in the request to a numerical attribute, then we use the computed intervals with rounded bounds obtained from all its product numerical attribute values. The computed intervals might not be ideal for some attributes. Therefore, we give you the option to overwrite them with the facet_intervals field. The maximum of facet intervals per CatalogAttribute is 40. Each interval must have a lower bound or an upper bound. If both bounds are provided, then the lower bound must be smaller or equal than the upper bound.
        - `exclusiveMaximum` number, double — Exclusive upper bound.
        - `minimum` number, double — Inclusive lower bound.
        - `maximum` number, double — Inclusive upper bound.
        - `exclusiveMinimum` number, double — Exclusive lower bound.
      - `mergedFacetValues` GoogleCloudRetailV2CatalogAttributeFacetConfigMergedFacetValue[] — Each instance replaces a list of facet values by a merged facet value. If a facet value is not in any list, then it will stay the same. To avoid conflicts, only paths of length 1 are accepted. In other words, if "dark_blue" merged into "BLUE", then the latter can't merge into "blues" because this would create a path of length 2. The maximum number of instances of MergedFacetValue per CatalogAttribute is 100. This feature is available only for textual custom attributes.
        - `values` string[] — All the facet values that are replaces by the same merged_value that follows. The maximum number of values per MergedFacetValue is 25. Each value can have up to 128 characters.
        - `mergedValue` string — All the previous values are replaced by this merged facet value. This merged_value must be non-empty and can have up to 128 characters.
    - `searchableOption` 'SEARCHABLE_OPTION_UNSPECIFIED' | 'SEARCHABLE_ENABLED' | 'SEARCHABLE_DISABLED' — When AttributesConfig.attribute_config_level is CATALOG_LEVEL_ATTRIBUTE_CONFIG, if SEARCHABLE_ENABLED, attribute values are searchable by text queries in SearchService.Search. If SEARCHABLE_ENABLED but attribute type is numerical, attribute values will not be searchable by text queries in SearchService.Search, as there are no text values associated to numerical attributes. Must be specified, when AttributesConfig.attribute_config_level is CATALOG_LEVEL_ATTRIBUTE_CONFIG, otherwise throws INVALID_FORMAT error.
    - `exactSearchableOption` 'EXACT_SEARCHABLE_OPTION_UNSPECIFIED' | 'EXACT_SEARCHABLE_ENABLED' | 'EXACT_SEARCHABLE_DISABLED' — If EXACT_SEARCHABLE_ENABLED, attribute values will be exact searchable. This property only applies to textual custom attributes and requires indexable set to enabled to enable exact-searchable. If unset, the server behavior defaults to EXACT_SEARCHABLE_DISABLED.
    - `type` 'UNKNOWN' | 'TEXTUAL' | 'NUMERICAL' — Output only. The type of this attribute. This is derived from the attribute in Product.attributes.
    - `indexableOption` 'INDEXABLE_OPTION_UNSPECIFIED' | 'INDEXABLE_ENABLED' | 'INDEXABLE_DISABLED' — When AttributesConfig.attribute_config_level is CATALOG_LEVEL_ATTRIBUTE_CONFIG, if INDEXABLE_ENABLED attribute values are indexed so that it can be filtered, faceted, or boosted in SearchService.Search. Must be specified when AttributesConfig.attribute_config_level is CATALOG_LEVEL_ATTRIBUTE_CONFIG, otherwise throws INVALID_FORMAT error.
    - `inUse` boolean — Output only. Indicates whether this attribute has been used by any products. `True` if at least one Product is using this attribute in Product.attributes. Otherwise, this field is `False`. CatalogAttribute can be pre-loaded by using CatalogService.AddCatalogAttribute or CatalogService.UpdateAttributesConfig APIs. This field is `False` for pre-loaded CatalogAttributes. Only pre-loaded catalog attributes that are neither in use by products nor predefined can be deleted. Catalog attributes that are either in use by products or are predefined attributes cannot be deleted; however, their configuration properties will reset to default values upon removal request. After catalog changes, it takes about 10 minutes for this field to update.
    - `key` string — Required. Attribute name. For example: `color`, `brands`, `attributes.custom_attribute`, such as `attributes.xyz`. To be indexable, the attribute name can contain only alpha-numeric characters and underscores. For example, an attribute named `attributes.abc_xyz` can be indexed, but an attribute named `attributes.abc-xyz` cannot be indexed. If the attribute key starts with `attributes.`, then the attribute is a custom attribute. Attributes such as `brands`, `patterns`, and `title` are built-in and called system attributes.
    - `retrievableOption` 'RETRIEVABLE_OPTION_UNSPECIFIED' | 'RETRIEVABLE_ENABLED' | 'RETRIEVABLE_DISABLED' — If RETRIEVABLE_ENABLED, attribute values are retrievable in the search results. If unset, the server behavior defaults to RETRIEVABLE_DISABLED.

## Response `200`

Successful response

---

[API](https://skmtc.net/google/apis/retail.md) · [All operations](https://skmtc.net/google/apis/retail/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/google/retail/versions/146c67e59640/schema)