---
title: Create search configurations (legacy)
slug: o7mc0039
canonical_url: https://docs.coveo.com/en/o7mc0039/
collection: coveo-for-commerce
source_format: adoc
---
# Create search configurations (legacy)

> **Important**
>
> This article covers the legacy Search Configurations API.
> The [Coveo Platform](https://docs.coveo.com/en/186/) no longer uses search configurations to configure [queries](https://docs.coveo.com/en/231/) or define rules.
> 
> This functionality has been replaced as follows:
> 
> * Global query configurations are now managed directly through the dedicated [Query Configurations API](https://docs.coveo.com/en/103/api-reference/commerce-api#tag/Query-Configurations).
> 
> * Rules are managed in the [Coveo Merchandising Hub (CMH)](https://docs.coveo.com/en/o5290573/).
> 
> For now, the global endpoints of the Search Configurations API (`/rest/organizations/<ORGANIZATION_ID>/commerce/v2/configurations/search/global`) are still available.

You don't need to create a _global_ query configuration before querying products from a [search interface](https://docs.coveo.com/en/2741/).
However, you can create a global query configuration to specify the [facets](https://docs.coveo.com/en/198/), sorts, and additional [fields](https://docs.coveo.com/en/200/) that apply when your front end [queries](https://docs.coveo.com/en/231/) the Commerce API.

Previously, you could use [specific search configurations](#specific-search-configurations) to define which rules should apply to [queries](https://docs.coveo.com/en/231/).
However, you can no longer define rules programmatically.

The global query configuration is important in the context of search because, unlike [product listing pages (PLPs)](https://docs.coveo.com/en/m1sf3187/), which are preconfigured based on a known set of products, search is much more responsive.
It's impossible to know what a user will [query](https://docs.coveo.com/en/231/) for, which means the global query configuration will be leveraged for most, if not all, [queries](https://docs.coveo.com/en/231/).

## Use the global search configuration endpoints

A global query configuration is a JSON object that follows a specific format.
You can modify global query configurations by calling the [Search Configurations API endpoints](https://docs.coveo.com/en/103#tag/Search-Configurations) and providing a configuration JSON.

The following is a sample global query configuration JSON:

```json
{
  "trackingId": "<TRACKING ID>", <1>
  "name": "GLOBAL",
  "conditions": [], <2>
  "queryConfiguration": { <3>
      "additionalFields": [
          "color",
          "size"
      ],
      "facets": { <4>
          "enableIndexFacetOrdering": false,
          "freezeFacetOrder": true,
          "facets": [
              {
                  "type": "numericalRange",
                  "facetId": "ec_price",
                  "field": "ec_price",
                  "displayNames": [
                      {
                          "value": "Price",
                          "language": "en"
                      }
                  ]
              },
              {
                  "type": "regular",
                  "facetId": "cf_product_type",
                  "field": "cf_product_type",
                  "displayNames": [
                      {
                          "value": "Product Type",
                          "language": "en"
                      }
                  ]
              },
              {
                  "type": "hierarchical",
                  "facetId": "ec_category",
                  "field": "ec_category",
                  "displayNames": [
                      {
                          "value": "Category",
                          "language": "en"
                      }
                  ],
                  "delimitingCharacter": "|"
              }
          ]
      },
      "perPage": 15,
      "sorts": [
          {
              "sortCriteria": "relevance"
          },
          {
              "sortCriteria": "fields",
              "fields": [
                  {
                      "field": "ec_promo_price",
                      "direction": "desc",
                      "displayNames": [
                          {
                              "value": "Price (High to Low)",
                              "language": "en"
                          }
                      ]
                  }
              ]
          }
      ]
  },
  "scope": "global" <5>
}
```

<1> The [`trackingId`](https://docs.coveo.com/en/n8tg0567/) lets you segregate your configurations.
When you make a request via the Commerce API to retrieve this configuration, you'll need to specify the [tracking ID](https://docs.coveo.com/en/o8rb0139/) to retrieve the configuration.

<2> `conditions` lets you specify the conditions under which this configuration applies.
For the _global_ configuration, these are left empty.

<3> `queryConfiguration` lets you specify which [facets](https://docs.coveo.com/en/198/), sort criteria, and additional fields you want to be returned for this configuration.

<4> Only use the `facets` property if you're managing [facets](https://docs.coveo.com/en/198/) directly via the Commerce API.
If you're using the [Coveo Merchandising Hub (CMH)](https://docs.coveo.com/en/o5290573/), use the [Facet manager](https://docs.coveo.com/en/p5da0252/) instead.

> **Important**
>
> The [Facet manager](https://docs.coveo.com/en/p63f0211/) in the CMH is currently in open beta.
> If you gained access to the CMH before the [Facet manager](https://docs.coveo.com/en/p63f0211/) was available and would like to adopt it, contact your Coveo representative.

<5> The scope of the configuration.
This must be set to `global`.

For more details on all the possible parameters, see the [reference documentation](https://docs.coveo.com/en/103#tag/Search-Configurations/operation/updateGlobal).

## Specific search configurations

The [Coveo Platform](https://docs.coveo.com/en/186/) no longer supports specific search configurations.
When you use any Search Configurations API endpoints (apart from the global ones), you'll get an error.

Instead, create and manage your query rules in the [Coveo Merchandising Hub (CMH)](https://docs.coveo.com/en/o5290573/).