Get Content

A first-party cookie created by the Bloomreach tracking pixel library (BrTrk). This cookie creates a unique, anonymous identifier for every browser or device.

Use the default value provided, which is already encoded.

The Bloomreach-provided authentication key for the Bloomreach account that's sending the request.

Pass the auth_key with an empty value in client-side calls. The auth_key value is a private authorization key. If you include your valid auth_key value in client-side calls, then you inadvertently expose that private information to everybody.

Indicates whether to return data wrapped in the function for cross-origin requests.

For server-side requests, use the value br_server. For native-app requests, use the value br_app.

Named identifier of the catalog. A catalog is a grouping of items into a broader category such as blogs, videos, etc. A catalog is a representation of a group of items and must have a unique name, that is also unique to a domain (if you have multiple sites).

Catalogs are created in the DataConnect UI by default, you can rename the catalogs when you set up your catalogs initially.

Your site domain's ID, which is provided by Bloomreach. This ID is for the domain that you want to receive your Bloomreach API requests. This parameter identifies the specific site version when the one account ID hosts multiple site versions with unique characteristics, such as language versions. Bloomreach uses your domain_key parameter value to ensure that only the data that pertains to that site version is used for query and analytics features, such as autosuggestions.

Applies a complex boolean filter to search results to include or exclude items that fit your parameter values. Any attribute in your content feed is valid, such as title and description.

Typically, the efq parameter is used for custom attributes that you include in your content feed to support additional business logic that you might need to filter. Read more about using the efq parameter in the "Complex boolean filtering" section in the Faceting and filtering page.

Returns a list of fields to facet on. You must explicitly request all the facets you would like returned.

Return a count of ranged facets, such as price and sale price. Use numeric attributes only.

You need to parse the values that are in the facets_counts section of the response. The facet_queries section has custom range facets for numeric fields that you define in your request. The facet_fields section gives you facets that you can display to your site's users, such as brands and colors.

The attributes that you want returned in your API response, such as item IDs and prices.

All fl parameters for Content Search must include item_id as one of their values. Any attribute from your content feed may be used as a value for fl.

Multiple values should be comma separated, such as fl=item_id,price.

The fq parameter applies a faceted filter to the returned content, searching for content that fits your parameter values.

Any facet that you want to filter must be in your feed. Read more about using the fq parameter in the "Simple Filtering" section in the Faceting and filtering page.

You can configure Attributes from the Catalog Management Tab. Configure which attributes in your content feed you want to apply as filters to search results.

Your site visitor's search query. Search queries are composed of one or more terms.

You can percent encode spaces between terms as %20, or you can leave the spaces unencoded.

If you use q=, the latency of the response will vary depending on your catalog size and it may not adhere to Bloomreach's standard SLA. Additionally, most merchandising operations do not work on query parameters, except for include/exclude operations.

The URL of the page or HTTP referrer where the request is started.

The type of API request. Value should be search for Content Search requests.

The type of search. Value should be keyword for Content Search requests.

Sorts results based on the field value in ascending, descending, or another combination of orders. You can sort any fl field.

Value is a field name, followed by asc/desc for ascending/descending order respectively. For example, sort=sale_price desc sorts in descending order of the sale price

The absolute URL of the page where the request is initiated. Do not use a relative URL.

The universal customer ID of the user. You only need to pass this field if your particular integration tracks customers this way. The parameter captures user IDs from the customer side, and reuses the information when powering apps or enhancing cross-device linking. In this way, Bloomreach recognizes users in a way that's aligned with your system.

Use an anonymous string. Don't use email or other personally identifiable information.

If you do not track users this way, then omit this field.

A unique identifier for a specific view of your content catalog. If you have multiple versions of your site, each with their own content catalog characteristics like content titles and descriptions, then add view_id to your call.

Bloomreach uses your view_id parameter value to display the right content information for your customers based on their individual site views. You can enter any string value to identify the specific site catalog view. This string must be consistent in your pixel, API, and content catalog.

Bloomreach Content Search can support a single view_id, multiple view_ids (separated by commas) or * view_id in a single API parameter for a single content catalog. If no view_ids are passed for a content item in a catalog, Bloomreach will assign a br_default_view value. If an API call is made with no view_id in the request, the br_default_view content items will return.

If a content item contains more than one view_id in the catalog and those view_ids are passed in the API param, we will return those documents without de-duping or grouping.