Skip to main content
There are a number of optional parameters that can be provided when sending queries to Elevate. The following sections provide examples of how to work with some of these parameters.

​
Stores and channels

Retailers can provide online and physical store stock numbers in the catalog imports. For more information, see Stores and channels. If STORE is explicitly declared in the channel parameter, then value(s) for the store parameter must be supplied with the relevant store keys. The following example shows a query to the search-page endpoint to include the stock level from both online and physical stores, particularly for stores with the store keys soho and tribeca.

​
Example

​
Notify

If large scale testing is done to simulate visitor behavior during development and testing, it is recommended to ensure that notify=false is applied. For more information, see the query parameters reference.

​
Example

The following is an example of how to work with the notify parameter.

​
Templates and custom attributes

By default, Elevate returns the predefined product attributes in the query response. To include custom attributes in the query response, one of two methods can be used:
  • The first option is to supply a templateId parameter, corresponding to the ID of an imported template. All attributes defined in the template will be returned in the query response.
  • The second option is to supply all requested custom parameters as pipe-separated values in the presentCustom parameter. Custom attributes on a variant can be requested by prefixing the name with variant., for example variant.grip. Custom typed attributes can be requested by prefixing the name with the type, for example length.diameter or variant.number.package_count.
Note that these options are mutually exclusive: you can only use one of them in each request. In general, we suggest using templates to reduce the size of query requests and, in particular, query responses, as templates let you fine-tune what data you want.

​
Example

Below is an example of how to include custom attributes in a query response.
Multiple custom attributes can be requested by specifying them using URL-encoded pipe separators, for example presentCustom=category%7Cseason.

​
Present prices

Retailers can choose to simultaneously present multiple prices for products on the site, for example member price versus non-member price. To include these custom prices in the query response, they must be specified in the presentPrices parameter.

​
Example

The value(s) supplied in the presentPrices parameter must match price identifiers defined in the catalog import, see Custom prices in the Format specification. Below is an example of how to include custom prices in a query response.
Multiple custom prices can be requested by specifying them using URL-encoded pipe separators, for example presentPrices=VIP%7CNON_VIP.
Last modified on September 11, 2026