algoliasearch 5.6.1 → 5.8.0

package/dist/lite/browser.d.ts

@@ -18,7 +18,7 @@ type Range = {
 /**
  * Precision of a coordinate-based search in meters to group results with similar distances.  The Geo ranking criterion considers all matches within the same range of distances to be equal.
  */
-type AroundPrecision = Range[] | number;
+type AroundPrecision = number | Array<Range>;
 
 /**
  * Return all records with a valid `_geoloc` attribute. Don\'t filter by distance.
@@ -28,32 +28,32 @@ type AroundRadiusAll = 'all';
 /**
  * Maximum radius for a search around a central location.  This parameter works in combination with the `aroundLatLng` and `aroundLatLngViaIP` parameters. By default, the search radius is determined automatically from the density of hits around the central location. The search radius is small if there are many hits close to the central coordinates.
  */
-type AroundRadius = AroundRadiusAll | number;
+type AroundRadius = number | AroundRadiusAll;
 
 /**
  * Filter the search by facet values, so that only records with the same facet values are retrieved.  **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.**  - `[filter1, filter2]` is interpreted as `filter1 AND filter2`. - `[[filter1, filter2], filter3]` is interpreted as `filter1 OR filter2 AND filter3`. - `facet:-value` is interpreted as `NOT facet:value`.  While it\'s best to avoid attributes that start with a `-`, you can still filter them by escaping with a backslash: `facet:\\-value`.
  */
-type FacetFilters = FacetFilters[] | string;
+type FacetFilters = Array<FacetFilters> | string;
 
 /**
- * Filter by numeric facets.  **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.**  You can use numeric comparison operators: `<`, `<=`, `=`, `!=`, `>`, `>=`. Comparsions are precise up to 3 decimals. You can also provide ranges: `facet:<lower> TO <upper>`. The range includes the lower and upper boundaries. The same combination rules apply as for `facetFilters`.
+ * Filter by numeric facets.  **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.**  You can use numeric comparison operators: `<`, `<=`, `=`, `!=`, `>`, `>=`. Comparisons are precise up to 3 decimals. You can also provide ranges: `facet:<lower> TO <upper>`. The range includes the lower and upper boundaries. The same combination rules apply as for `facetFilters`.
  */
-type NumericFilters = NumericFilters[] | string;
+type NumericFilters = Array<NumericFilters> | string;
 
 /**
  * Filters to promote or demote records in the search results.  Optional filters work like facet filters, but they don\'t exclude records from the search results. Records that match the optional filter rank before records that don\'t match. If you\'re using a negative filter `facet:-value`, matching records rank after records that don\'t match.  - Optional filters don\'t work on virtual replicas. - Optional filters are applied _after_ sort-by attributes. - Optional filters don\'t work with numeric attributes.
  */
-type OptionalFilters = OptionalFilters[] | string;
+type OptionalFilters = Array<OptionalFilters> | string;
 
 /**
  * ISO code for a supported language.
  */
-type SupportedLanguage = 'af' | 'ar' | 'az' | 'bg' | 'bn' | 'ca' | 'cs' | 'cy' | 'da' | 'de' | 'el' | 'en' | 'eo' | 'es' | 'et' | 'eu' | 'fa' | 'fi' | 'fo' | 'fr' | 'ga' | 'gl' | 'he' | 'hi' | 'hu' | 'hy' | 'id' | 'is' | 'it' | 'ja' | 'ka' | 'kk' | 'ko' | 'ku' | 'ky' | 'lt' | 'lv' | 'mi' | 'mn' | 'mr' | 'ms' | 'mt' | 'nb' | 'nl' | 'no' | 'ns' | 'pl' | 'ps' | 'pt-br' | 'pt' | 'qu' | 'ro' | 'ru' | 'sk' | 'sq' | 'sv' | 'sw' | 'ta' | 'te' | 'th' | 'tl' | 'tn' | 'tr' | 'tt' | 'uk' | 'ur' | 'uz' | 'zh';
+type SupportedLanguage = 'af' | 'ar' | 'az' | 'bg' | 'bn' | 'ca' | 'cs' | 'cy' | 'da' | 'de' | 'el' | 'en' | 'eo' | 'es' | 'et' | 'eu' | 'fa' | 'fi' | 'fo' | 'fr' | 'ga' | 'gl' | 'he' | 'hi' | 'hu' | 'hy' | 'id' | 'is' | 'it' | 'ja' | 'ka' | 'kk' | 'ko' | 'ku' | 'ky' | 'lt' | 'lv' | 'mi' | 'mn' | 'mr' | 'ms' | 'mt' | 'nb' | 'nl' | 'no' | 'ns' | 'pl' | 'ps' | 'pt' | 'pt-br' | 'qu' | 'ro' | 'ru' | 'sk' | 'sq' | 'sv' | 'sw' | 'ta' | 'te' | 'th' | 'tl' | 'tn' | 'tr' | 'tt' | 'uk' | 'ur' | 'uz' | 'zh';
 
 /**
  * Filter the search by values of the special `_tags` attribute.  **Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.**  Different from regular facets, `_tags` can only be used for filtering (including or excluding records). You won\'t get a facet count. The same combination and escaping rules apply as for `facetFilters`.
  */
-type TagFilters = TagFilters[] | string;
+type TagFilters = Array<TagFilters> | string;
 
 type BaseRecommendSearchParams = {
     /**
@@ -75,17 +75,17 @@ type BaseRecommendSearchParams = {
     /**
      * Restricts a search to a subset of your searchable attributes. Attribute names are case-sensitive.
      */
-    restrictSearchableAttributes?: string[];
+    restrictSearchableAttributes?: Array<string>;
     /**
      * Facets for which to retrieve facet values that match the search criteria and the number of matching facet values.  To retrieve all facets, use the wildcard character `*`. For more information, see [facets](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#contextual-facet-values-and-counts).
      */
-    facets?: string[];
+    facets?: Array<string>;
     /**
      * Whether faceting should be applied after deduplication with `distinct`.  This leads to accurate facet counts when using faceting in combination with `distinct`. It\'s usually better to use `afterDistinct` modifiers in the `attributesForFaceting` setting, as `facetingAfterDistinct` only computes correct facet counts if all records have the same facet values for the `attributeForDistinct`.
      */
     facetingAfterDistinct?: boolean;
     /**
-     * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude.  Only records included within circle around this central location are included in the results. The radius of the circle is determined by the `aroundRadius` and `minimumAroundRadius` settings. This parameter is ignored if you also specify `insidePolygon` or `insideBoundingBox`.
+     * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude.  Only records included within a circle around this central location are included in the results. The radius of the circle is determined by the `aroundRadius` and `minimumAroundRadius` settings. This parameter is ignored if you also specify `insidePolygon` or `insideBoundingBox`.
      */
     aroundLatLng?: string;
     /**
@@ -101,19 +101,19 @@ type BaseRecommendSearchParams = {
     /**
      * Coordinates for a rectangular area in which to search.  Each bounding box is defined by the two opposite points of its diagonal, and expressed as latitude and longitude pair: `[p1 lat, p1 long, p2 lat, p2 long]`. Provide multiple bounding boxes as nested arrays. For more information, see [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas).
      */
-    insideBoundingBox?: number[][];
+    insideBoundingBox?: Array<Array<number>>;
     /**
      * Coordinates of a polygon in which to search.  Polygons are defined by 3 to 10,000 points. Each point is represented by its latitude and longitude. Provide multiple polygons as nested arrays. For more information, see [filtering inside polygons](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas). This parameter is ignored if you also specify `insideBoundingBox`.
      */
-    insidePolygon?: number[][];
+    insidePolygon?: Array<Array<number>>;
     /**
      * ISO language codes that adjust settings that are useful for processing natural language queries (as opposed to keyword searches):  - Sets `removeStopWords` and `ignorePlurals` to the list of provided languages. - Sets `removeWordsIfNoResults` to `allOptional`. - Adds a `natural_language` attribute to `ruleContexts` and `analyticsTags`.
      */
-    naturalLanguages?: SupportedLanguage[];
+    naturalLanguages?: Array<SupportedLanguage>;
     /**
      * Assigns a rule context to the search query.  [Rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) are strings that you can use to trigger matching rules.
      */
-    ruleContexts?: string[];
+    ruleContexts?: Array<string>;
     /**
      * Impact that Personalization should have on this search.  The higher this value is, the more Personalization determines the ranking compared to other factors. For more information, see [Understanding Personalization impact](https://www.algolia.com/doc/guides/personalization/personalizing-results/in-depth/configuring-personalization/#understanding-personalization-impact).
      */
@@ -141,7 +141,7 @@ type BaseRecommendSearchParams = {
     /**
      * Tags to apply to the query for [segmenting analytics data](https://www.algolia.com/doc/guides/search-analytics/guides/segments/).
      */
-    analyticsTags?: string[];
+    analyticsTags?: Array<string>;
     /**
      * Whether to include this search when calculating processing-time percentiles.
      */
@@ -154,13 +154,13 @@ type BaseRecommendSearchParams = {
 
 type BaseIndexSettings = {
     /**
-     * Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/).  Facets are attributes that let you categorize search results. They can be used for filtering search results. By default, no attribute is used for faceting. Attribute names are case-sensitive.  **Modifiers**  - `filterOnly(\"ATTRIBUTE\")`.   Allows using this attribute as a filter, but doesn\'t evalue the facet values.  - `searchable(\"ATTRIBUTE\")`.   Allows searching for facet values.  - `afterDistinct(\"ATTRIBUTE\")`.   Evaluates the facet count _after_ deduplication with `distinct`.   This ensures accurate facet counts.   You can apply this modifier to searchable facets: `afterDistinct(searchable(ATTRIBUTE))`.
+     * Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/).  Facets are attributes that let you categorize search results. They can be used for filtering search results. By default, no attribute is used for faceting. Attribute names are case-sensitive.  **Modifiers**  - `filterOnly(\"ATTRIBUTE\")`.   Allows the attribute to be used as a filter but doesn\'t evaluate the facet values.  - `searchable(\"ATTRIBUTE\")`.   Allows searching for facet values.  - `afterDistinct(\"ATTRIBUTE\")`.   Evaluates the facet count _after_ deduplication with `distinct`.   This ensures accurate facet counts.   You can apply this modifier to searchable facets: `afterDistinct(searchable(ATTRIBUTE))`.
      */
-    attributesForFaceting?: string[];
+    attributesForFaceting?: Array<string>;
     /**
-     * Creates [replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/).  Replicas are copies of a primary index with the same records but different settings, synonyms, or rules. If you want to offer a different ranking or sorting of your search results, you\'ll use replica indices. All index operations on a primary index are automatically forwarded to its replicas. To add a replica index, you must provide the complete set of replicas to this parameter. If you omit a replica from this list, the replica turns into a regular, standalone index that will no longer by synced with the primary index.  **Modifier**  - `virtual(\"REPLICA\")`.   Create a virtual replica,   Virtual replicas don\'t increase the number of records and are optimized for [Relevant sorting](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/relevant-sort/).
+     * Creates [replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/).  Replicas are copies of a primary index with the same records but different settings, synonyms, or rules. If you want to offer a different ranking or sorting of your search results, you\'ll use replica indices. All index operations on a primary index are automatically forwarded to its replicas. To add a replica index, you must provide the complete set of replicas to this parameter. If you omit a replica from this list, the replica turns into a regular, standalone index that will no longer be synced with the primary index.  **Modifier**  - `virtual(\"REPLICA\")`.   Create a virtual replica,   Virtual replicas don\'t increase the number of records and are optimized for [Relevant sorting](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/relevant-sort/).
      */
-    replicas?: string[];
+    replicas?: Array<string>;
     /**
      * Maximum number of search results that can be obtained through pagination.  Higher pagination limits might slow down your search. For pagination limits above 1,000, the sorting of results beyond the 1,000th hit can\'t be guaranteed.
      */
@@ -168,19 +168,19 @@ type BaseIndexSettings = {
     /**
      * Attributes that can\'t be retrieved at query time.  This can be useful if you want to use an attribute for ranking or to [restrict access](https://www.algolia.com/doc/guides/security/api-keys/how-to/user-restricted-access-to-data/), but don\'t want to include it in the search results. Attribute names are case-sensitive.
      */
-    unretrievableAttributes?: string[];
+    unretrievableAttributes?: Array<string>;
     /**
      * Words for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). This also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) for the specified words.
      */
-    disableTypoToleranceOnWords?: string[];
+    disableTypoToleranceOnWords?: Array<string>;
     /**
      * Attributes, for which you want to support [Japanese transliteration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#japanese-transliteration-and-type-ahead).  Transliteration supports searching in any of the Japanese writing systems. To support transliteration, you must set the indexing language to Japanese. Attribute names are case-sensitive.
      */
-    attributesToTransliterate?: string[];
+    attributesToTransliterate?: Array<string>;
     /**
      * Attributes for which to split [camel case](https://wikipedia.org/wiki/Camel_case) words. Attribute names are case-sensitive.
      */
-    camelCaseAttributes?: string[];
+    camelCaseAttributes?: Array<string>;
     /**
      * Searchable attributes to which Algolia should apply [word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation/) (decompounding). Attribute names are case-sensitive.  Compound words are formed by combining two or more individual words, and are particularly prevalent in Germanic languages—for example, \"firefighter\". With decompounding, the individual components are indexed separately.  You can specify different lists for different languages. Decompounding is supported for these languages: Dutch (`nl`), German (`de`), Finnish (`fi`), Danish (`da`), Swedish (`sv`), and Norwegian (`no`). Decompounding doesn\'t work for words with [non-spacing mark Unicode characters](https://www.charactercodes.net/category/non-spacing_mark). For example, `Gartenstühle` won\'t be decompounded if the `ü` consists of `u` (U+0075) and `◌̈` (U+0308).
      */
@@ -188,27 +188,27 @@ type BaseIndexSettings = {
     /**
      * Languages for language-specific processing steps, such as word detection and dictionary settings.  **You should always specify an indexing language.** If you don\'t specify an indexing language, the search engine uses all [supported languages](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to unexpected search results. For more information, see [Language-specific configuration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/).
      */
-    indexLanguages?: SupportedLanguage[];
+    indexLanguages?: Array<SupportedLanguage>;
     /**
      * Searchable attributes for which you want to turn off [prefix matching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#adjusting-prefix-search). Attribute names are case-sensitive.
      */
-    disablePrefixOnAttributes?: string[];
+    disablePrefixOnAttributes?: Array<string>;
     /**
      * Whether arrays with exclusively non-negative integers should be compressed for better performance. If true, the compressed arrays may be reordered.
      */
     allowCompressionOfIntegerArray?: boolean;
     /**
-     * Numeric attributes that can be used as [numerical filters](https://www.algolia.com/doc/guides/managing-results/rules/detecting-intent/how-to/applying-a-custom-filter-for-a-specific-query/#numerical-filters). Attribute names are case-sensitive.  By default, all numeric attributes are available as numerical filters. For faster indexing, reduce the number of numeric attributes.  If you want to turn off filtering for all numeric attributes, specifiy an attribute that doesn\'t exist in your index, such as `NO_NUMERIC_FILTERING`.  **Modifier**  - `equalOnly(\"ATTRIBUTE\")`.   Support only filtering based on equality comparisons `=` and `!=`.
+     * Numeric attributes that can be used as [numerical filters](https://www.algolia.com/doc/guides/managing-results/rules/detecting-intent/how-to/applying-a-custom-filter-for-a-specific-query/#numerical-filters). Attribute names are case-sensitive.  By default, all numeric attributes are available as numerical filters. For faster indexing, reduce the number of numeric attributes.  To turn off filtering for all numeric attributes, specify an attribute that doesn\'t exist in your index, such as `NO_NUMERIC_FILTERING`.  **Modifier**  - `equalOnly(\"ATTRIBUTE\")`.   Support only filtering based on equality comparisons `=` and `!=`.
      */
-    numericAttributesForFiltering?: string[];
+    numericAttributesForFiltering?: Array<string>;
     /**
      * Controls which separators are indexed.  Separators are all non-letter characters except spaces and currency characters, such as $€£¥. By default, separator characters aren\'t indexed. With `separatorsToIndex`, Algolia treats separator characters as separate words. For example, a search for `C#` would report two matches.
      */
     separatorsToIndex?: string;
     /**
-     * Attributes used for searching. Attribute names are case-sensitive.  By default, all attributes are searchable and the [Attribute](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute) ranking criterion is turned off. With a non-empty list, Algolia only returns results with matches in the selected attributes. In addition, the Attribute ranking criterion is turned on: matches in attributes that are higher in the list of `searchableAttributes` rank first. To make matches in two attributes rank equally, include them in a comma-separated string, such as `\"title,alternate_title\"`. Attributes with the same priority are always unordered.  For more information, see [Searchable attributes](https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/how-to/setting-searchable-attributes/).  **Modifier**  - `unordered(\"ATTRIBUTE\")`.   Ignore the position of a match within the attribute.  Without modifier, matches at the beginning of an attribute rank higer than matches at the end.
+     * Attributes used for searching. Attribute names are case-sensitive.  By default, all attributes are searchable and the [Attribute](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute) ranking criterion is turned off. With a non-empty list, Algolia only returns results with matches in the selected attributes. In addition, the Attribute ranking criterion is turned on: matches in attributes that are higher in the list of `searchableAttributes` rank first. To make matches in two attributes rank equally, include them in a comma-separated string, such as `\"title,alternate_title\"`. Attributes with the same priority are always unordered.  For more information, see [Searchable attributes](https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/how-to/setting-searchable-attributes/).  **Modifier**  - `unordered(\"ATTRIBUTE\")`.   Ignore the position of a match within the attribute.  Without a modifier, matches at the beginning of an attribute rank higher than matches at the end.
      */
-    searchableAttributes?: string[];
+    searchableAttributes?: Array<string>;
     /**
      * An object with custom data.  You can store up to 32kB as custom data.
      */
@@ -216,7 +216,11 @@ type BaseIndexSettings = {
     /**
      * Characters and their normalized replacements. This overrides Algolia\'s default [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/).
      */
-    customNormalization?: Record<string, Record<string, string>>;
+    customNormalization?: {
+        [key: string]: {
+            [key: string]: string;
+        };
+    };
     /**
      * Attribute that should be used to establish groups of results. Attribute names are case-sensitive.  All records with the same value for this attribute are considered a group. You can combine `attributeForDistinct` with the `distinct` search parameter to control how many items per group are included in the search results.  If you want to use the same attribute also for faceting, use the `afterDistinct` modifier of the `attributesForFaceting` setting. This applies faceting _after_ deduplication, which will result in accurate facet counts.
      */
@@ -225,7 +229,7 @@ type BaseIndexSettings = {
 
 type AdvancedSyntaxFeatures = 'exactPhrase' | 'excludeWords';
 
-type AlternativesAsExact = 'ignorePlurals' | 'multiWordsSynonym' | 'singleWordSynonym';
+type AlternativesAsExact = 'ignorePlurals' | 'singleWordSynonym' | 'multiWordsSynonym';
 
 /**
  * Determines how many records of a group are included in the search results.  Records with the same value for the `attributeForDistinct` attribute are considered a group. The `distinct` setting controls how many members of the group are returned. This is useful for [deduplication and grouping](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature).  The `distinct` setting is ignored if `attributeForDistinct` is not set.
@@ -237,32 +241,32 @@ type Distinct = boolean | number;
  */
 type ExactOnSingleWordQuery = 'attribute' | 'none' | 'word';
 
-type BooleanString = 'false' | 'true';
+type BooleanString = 'true' | 'false';
 
 /**
  * Treat singular, plurals, and other forms of declensions as equivalent. You should only use this feature for the languages used in your index.
  */
-type IgnorePlurals = BooleanString | SupportedLanguage[] | boolean;
+type IgnorePlurals = Array<SupportedLanguage> | BooleanString | boolean;
 
 /**
- * Determines if and how query words are interpreted as prefixes.  By default, only the last query word is treated as prefix (`prefixLast`). To turn off prefix search, use `prefixNone`. Avoid `prefixAll`, which treats all query words as prefixes. This might lead to counterintuitive results and makes your search slower.  For more information, see [Prefix searching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/).
+ * Determines if and how query words are interpreted as prefixes.  By default, only the last query word is treated as a prefix (`prefixLast`). To turn off prefix search, use `prefixNone`. Avoid `prefixAll`, which treats all query words as prefixes. This might lead to counterintuitive results and makes your search slower.  For more information, see [Prefix searching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/).
  */
-type QueryType = 'prefixAll' | 'prefixLast' | 'prefixNone';
+type QueryType = 'prefixLast' | 'prefixAll' | 'prefixNone';
 
 /**
  * Restrict [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) to records that match these filters.
  */
-type ReRankingApplyFilter = ReRankingApplyFilter[] | string;
+type ReRankingApplyFilter = Array<ReRankingApplyFilter> | string;
 
 /**
  * Removes stop words from the search query.  Stop words are common words like articles, conjunctions, prepositions, or pronouns that have little or no meaning on their own. In English, \"the\", \"a\", or \"and\" are stop words.  You should only use this feature for the languages used in your index.
  */
-type RemoveStopWords = SupportedLanguage[] | boolean;
+type RemoveStopWords = Array<SupportedLanguage> | boolean;
 
 /**
  * Strategy for removing words from the query when it doesn\'t return any results. This helps to avoid returning empty search results.  - `none`.   No words are removed when a query doesn\'t return results.  - `lastWords`.   Treat the last (then second to last, then third to last) word as optional,   until there are results or at most 5 words have been removed.  - `firstWords`.   Treat the first (then second, then third) word as optional,   until there are results or at most 5 words have been removed.  - `allOptional`.   Treat all words as optional.  For more information, see [Remove words to improve results](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results/).
  */
-type RemoveWordsIfNoResults = 'allOptional' | 'firstWords' | 'lastWords' | 'none';
+type RemoveWordsIfNoResults = 'none' | 'lastWords' | 'firstWords' | 'allOptional';
 
 /**
  * Order of facet names.
@@ -271,24 +275,24 @@ type IndexSettingsFacets = {
     /**
      * Explicit order of facets or facet values.  This setting lets you always show specific facets or facet values at the top of the list.
      */
-    order?: string[];
+    order?: Array<string>;
 };
 
 /**
  * Order of facet values that aren\'t explicitly positioned with the `order` setting.  - `count`.   Order remaining facet values by decreasing count.   The count is the number of matching records containing this facet value.  - `alpha`.   Sort facet values alphabetically.  - `hidden`.   Don\'t show facet values that aren\'t explicitly positioned.
  */
-type SortRemainingBy = 'alpha' | 'count' | 'hidden';
+type SortRemainingBy = 'count' | 'alpha' | 'hidden';
 
 type Value = {
     /**
      * Explicit order of facets or facet values.  This setting lets you always show specific facets or facet values at the top of the list.
      */
-    order?: string[];
+    order?: Array<string>;
     sortRemainingBy?: SortRemainingBy;
     /**
      * Hide facet values.
      */
-    hide?: string[];
+    hide?: Array<string>;
 };
 
 /**
@@ -299,7 +303,9 @@ type FacetOrdering = {
     /**
      * Order of facet values. One object for each facet.
      */
-    values?: Record<string, Value>;
+    values?: {
+        [key: string]: Value;
+    };
 };
 
 /**
@@ -310,11 +316,56 @@ type RedirectURL = {
 };
 
 /**
- * Extra data that can be used in the search UI.  You can use this to control aspects of your search UI, such as, the order of facet names and values without changing your frontend code.
+ * url for a search banner image.
+ */
+type BannerImageUrl = {
+    url?: string;
+};
+
+/**
+ * image of a search banner.
+ */
+type BannerImage = {
+    urls?: BannerImageUrl;
+    title?: string;
+};
+
+/**
+ * link for a banner defined in merchandising studio.
+ */
+type BannerLink = {
+    url?: string;
+};
+
+/**
+ * a search banner with image and url.
+ */
+type Banner = {
+    image?: BannerImage;
+    link?: BannerLink;
+};
+
+/**
+ * banners defined in the merchandising studio for the given search.
+ */
+type Banners = {
+    banners?: Banner;
+};
+
+/**
+ * widgets returned from any rules that are applied to the current search.
+ */
+type Widgets = {
+    banners?: Banners;
+};
+
+/**
+ * Extra data that can be used in the search UI.  You can use this to control aspects of your search UI, such as the order of facet names and values without changing your frontend code.
  */
 type RenderingContent = {
     facetOrdering?: FacetOrdering;
     redirect?: RedirectURL;
+    widgets?: Widgets;
 };
 
 /**
@@ -323,19 +374,19 @@ type RenderingContent = {
 type TypoToleranceEnum = 'min' | 'strict';
 
 /**
- * Whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied.  If typo tolerance is true, `min`, or `strict`, [word splitting and concetenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) is also active.
+ * Whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied.  If typo tolerance is true, `min`, or `strict`, [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) are also active.
  */
-type TypoTolerance = TypoToleranceEnum | boolean;
+type TypoTolerance = boolean | TypoToleranceEnum;
 
 type BaseRecommendIndexSettings = {
     /**
      * Attributes to include in the API response.  To reduce the size of your response, you can retrieve only some of the attributes. Attribute names are case-sensitive.  - `*` retrieves all attributes, except attributes included in the `customRanking` and `unretrievableAttributes` settings. - To retrieve all attributes except a specific one, prefix the attribute with a dash and combine it with the `*`: `[\"*\", \"-ATTRIBUTE\"]`. - The `objectID` attribute is always included.
      */
-    attributesToRetrieve?: string[];
+    attributesToRetrieve?: Array<string>;
     /**
      * Determines the order in which Algolia returns your results.  By default, each entry corresponds to a [ranking criteria](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/). The tie-breaking algorithm sequentially applies each criterion in the order they\'re specified. If you configure a replica index for [sorting by an attribute](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/how-to/sort-by-attribute/), you put the sorting attribute at the top of the list.  **Modifiers**  - `asc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in ascending order. - `desc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in descending order.  Before you modify the default setting, you should test your changes in the dashboard, and by [A/B testing](https://www.algolia.com/doc/guides/ab-testing/what-is-ab-testing/).
      */
-    ranking?: string[];
+    ranking?: Array<string>;
     /**
      * Relevancy threshold below which less relevant results aren\'t included in the results.  You can only set `relevancyStrictness` on [virtual replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/#what-are-virtual-replicas). Use this setting to strike a balance between the relevance and number of returned results.
      */
@@ -343,11 +394,11 @@ type BaseRecommendIndexSettings = {
     /**
      * Attributes to highlight.  By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. Attribute names are case-sensitive.  With highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and `highlightPostTag`. You can use this to visually highlight matching parts of a search query in your UI.  For more information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js/).
      */
-    attributesToHighlight?: string[];
+    attributesToHighlight?: Array<string>;
     /**
      * Attributes for which to enable snippets. Attribute names are case-sensitive.  Snippets provide additional context to matched words. If you enable snippets, they include 10 words, including the matched word. The matched word will also be wrapped by HTML tags for highlighting. You can adjust the number of words with the following notation: `ATTRIBUTE:NUMBER`, where `NUMBER` is the number of words to be extracted.
      */
-    attributesToSnippet?: string[];
+    attributesToSnippet?: Array<string>;
     /**
      * HTML tag to insert before the highlighted parts in all highlighted results and snippets.
      */
@@ -380,13 +431,13 @@ type BaseRecommendIndexSettings = {
     /**
      * Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). Attribute names are case-sensitive.  Returning only exact matches can help when:  - [Searching in hyphenated attributes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/). - Reducing the number of matches when you have too many.   This can happen with attributes that are long blocks of text, such as product descriptions.  Consider alternatives such as `disableTypoToleranceOnWords` or adding synonyms if your attributes have intentional unusual spellings that might look like typos.
      */
-    disableTypoToleranceOnAttributes?: string[];
+    disableTypoToleranceOnAttributes?: Array<string>;
     ignorePlurals?: IgnorePlurals;
     removeStopWords?: RemoveStopWords;
     /**
      * Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries.  This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` settings. This setting also sets a dictionary for word detection in the logogram-based [CJK](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/#normalization-for-logogram-based-languages-cjk) languages. To support this, you must place the CJK language **first**.  **You should always specify a query language.** If you don\'t specify an indexing language, the search engine uses all [supported languages](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to unexpected search results. For more information, see [Language-specific configuration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/).
      */
-    queryLanguages?: SupportedLanguage[];
+    queryLanguages?: Array<SupportedLanguage>;
     /**
      * Whether to split compound words in the query into their building blocks.  For more information, see [Word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words). Word segmentation is supported for these languages: German, Dutch, Finnish, Swedish, and Norwegian. Decompounding doesn\'t work for words with [non-spacing mark Unicode characters](https://www.charactercodes.net/category/non-spacing_mark). For example, `Gartenstühle` won\'t be decompounded if the `ü` consists of `u` (U+0075) and `◌̈` (U+0308).
      */
@@ -406,25 +457,25 @@ type BaseRecommendIndexSettings = {
      */
     advancedSyntax?: boolean;
     /**
-     * Words that should be considered optional when found in the query.  By default, records must match all words in the search query to be included in the search results. Adding optional words can help to increase the number of search results by running an additional search query that doesn\'t include the optional words. For example, if the search query is \"action video\" and \"video\" is an optional word, the search engine runs two queries. One for \"action video\" and one for \"action\". Records that match all words are ranked higher.  For a search query with 4 or more words **and** all its words are optional, the number of matched words required for a record to be included in the search results increases for every 1,000 records:  - If `optionalWords` has less than 10 words, the required number of matched words increases by 1:   results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 2 matched words. - If `optionalWords` has 10 or more words, the number of required matched words increases by the number of optional words dividied by 5 (rounded down).   For example, with 18 optional words: results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 4 matched words.  For more information, see [Optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).
+     * Words that should be considered optional when found in the query.  By default, records must match all words in the search query to be included in the search results. Adding optional words can help to increase the number of search results by running an additional search query that doesn\'t include the optional words. For example, if the search query is \"action video\" and \"video\" is an optional word, the search engine runs two queries. One for \"action video\" and one for \"action\". Records that match all words are ranked higher.  For a search query with 4 or more words **and** all its words are optional, the number of matched words required for a record to be included in the search results increases for every 1,000 records:  - If `optionalWords` has less than 10 words, the required number of matched words increases by 1:   results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 2 matched words. - If `optionalWords` has 10 or more words, the number of required matched words increases by the number of optional words divided by 5 (rounded down).   For example, with 18 optional words: results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 4 matched words.  For more information, see [Optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).
      */
-    optionalWords?: string[];
+    optionalWords?: Array<string>;
     /**
-     * Searchable attributes for which you want to [turn off the Exact ranking criterion](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/adjust-exact-settings/#turn-off-exact-for-some-attributes). Attribute names are case-sensitive.  This can be useful for attributes with long values, where the likelyhood of an exact match is high, such as product descriptions. Turning off the Exact ranking criterion for these attributes favors exact matching on other attributes. This reduces the impact of individual attributes with a lot of content on ranking.
+     * Searchable attributes for which you want to [turn off the Exact ranking criterion](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/adjust-exact-settings/#turn-off-exact-for-some-attributes). Attribute names are case-sensitive.  This can be useful for attributes with long values, where the likelihood of an exact match is high, such as product descriptions. Turning off the Exact ranking criterion for these attributes favors exact matching on other attributes. This reduces the impact of individual attributes with a lot of content on ranking.
      */
-    disableExactOnAttributes?: string[];
+    disableExactOnAttributes?: Array<string>;
     exactOnSingleWordQuery?: ExactOnSingleWordQuery;
     /**
      * Alternatives of query words that should be considered as exact matches by the Exact ranking criterion.  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY/NYC\" are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY/New York\" are considered exact matches.
      */
-    alternativesAsExact?: AlternativesAsExact[];
+    alternativesAsExact?: Array<AlternativesAsExact>;
     /**
      * Advanced search syntax features you want to support.  - `exactPhrase`.   Phrases in quotes must match exactly.   For example, `sparkly blue \"iPhone case\"` only returns records with the exact string \"iPhone case\".  - `excludeWords`.   Query words prefixed with a `-` must not occur in a record.   For example, `search -engine` matches records that contain \"search\" but not \"engine\".  This setting only has an effect if `advancedSyntax` is true.
      */
-    advancedSyntaxFeatures?: AdvancedSyntaxFeatures[];
+    advancedSyntaxFeatures?: Array<AdvancedSyntaxFeatures>;
     distinct?: Distinct;
     /**
-     * Whether to replace a highlighted word with the matched synonym.  By default, the original words are highlighted even if a synonym matches. For example, with `home` as a synonym for `house` and a search for `home`, records matching either \"home\" or \"house\" are included in the search results, and either \"home\" or \"house\" are highlighted.  With `replaceSynonymsInHighlight` set to `true`, a search for `home` still matches the same records, but all occurences of \"house\" are replaced by \"home\" in the highlighted response.
+     * Whether to replace a highlighted word with the matched synonym.  By default, the original words are highlighted even if a synonym matches. For example, with `home` as a synonym for `house` and a search for `home`, records matching either \"home\" or \"house\" are included in the search results, and either \"home\" or \"house\" are highlighted.  With `replaceSynonymsInHighlight` set to `true`, a search for `home` still matches the same records, but all occurrences of \"house\" are replaced by \"home\" in the highlighted response.
      */
     replaceSynonymsInHighlight?: boolean;
     /**
@@ -434,7 +485,7 @@ type BaseRecommendIndexSettings = {
     /**
      * Properties to include in the API response of `search` and `browse` requests.  By default, all response properties are included. To reduce the response size, you can select, which attributes should be included.  You can\'t exclude these properties: `message`, `warning`, `cursor`, `serverUsed`, `indexUsed`, `abTestVariantID`, `parsedQuery`, or any property triggered by the `getRankingInfo` parameter.  Don\'t exclude properties that you might need in your search UI.
      */
-    responseFields?: string[];
+    responseFields?: Array<string>;
     /**
      * Maximum number of facet values to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
      */
@@ -474,7 +525,7 @@ type SearchParamsQuery = {
 /**
  * Search parameters for filtering the recommendations.
  */
-type RecommendSearchParams = BaseRecommendSearchParams & RecommendIndexSettings & SearchParamsQuery;
+type RecommendSearchParams = BaseRecommendSearchParams & SearchParamsQuery & RecommendIndexSettings;
 
 type BaseRecommendRequest = {
     /**
@@ -589,757 +640,744 @@ type TrendingItems = {
 
 type TrendingItemsQuery = BaseRecommendRequest & TrendingItems;
 
-type RecommendationsRequest = BoughtTogetherQuery | LookingSimilarQuery | RecommendedForYouQuery | RelatedQuery | TrendingFacetsQuery | TrendingItemsQuery;
+type RecommendationsRequest = BoughtTogetherQuery | RelatedQuery | TrendingItemsQuery | TrendingFacetsQuery | LookingSimilarQuery | RecommendedForYouQuery;
 
 /**
- * - `default`: perform a search query - `facet` [searches for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
+ * Recommend request body.
  */
-type SearchTypeFacet = 'facet';
+type GetRecommendationsParams = {
+    /**
+     * Recommendation request with parameters depending on the requested model.
+     */
+    requests: Array<RecommendationsRequest>;
+};
 
-type SearchForFacetsOptions = {
+/**
+ * Whether certain properties of the search response are calculated exhaustive (exact) or approximated.
+ */
+type Exhaustive = {
     /**
-     * Facet name.
+     * Whether the facet count is exhaustive (`true`) or approximate (`false`). See the [related discussion](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-).
      */
-    facet: string;
+    facetsCount?: boolean;
     /**
-     * Index name (case-sensitive).
+     * The value is `false` if not all facet values are retrieved.
      */
-    indexName: string;
+    facetValues?: boolean;
     /**
-     * Text to search inside the facet\'s values.
+     * Whether the `nbHits` is exhaustive (`true`) or approximate (`false`). When the query takes more than 50ms to be processed, the engine makes an approximation. This can happen when using complex filters on millions of records, when typo-tolerance was not exhaustive, or when enough hits have been retrieved (for example, after the engine finds 10,000 exact matches). `nbHits` is reported as non-exhaustive whenever an approximation is made, even if the approximation didn’t, in the end, impact the exhaustivity of the query.
      */
-    facetQuery?: string;
+    nbHits?: boolean;
     /**
-     * Maximum number of facet values to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
+     * Rules matching exhaustivity. The value is `false` if rules were enable for this query, and could not be fully processed due a timeout. This is generally caused by the number of alternatives (such as typos) which is too large.
      */
-    maxFacetHits?: number;
-    type: SearchTypeFacet;
+    rulesMatch?: boolean;
+    /**
+     * Whether the typo search was exhaustive (`true`) or approximate (`false`). An approximation is done when the typo search query part takes more than 10% of the query budget (ie. 5ms by default) to be processed (this can happen when a lot of typo alternatives exist for the query). This field will not be included when typo-tolerance is entirely disabled.
+     */
+    typo?: boolean;
+};
+
+type FacetStats = {
+    /**
+     * Minimum value in the results.
+     */
+    min?: number;
+    /**
+     * Maximum value in the results.
+     */
+    max?: number;
+    /**
+     * Average facet value in the results.
+     */
+    avg?: number;
+    /**
+     * Sum of all values in the results.
+     */
+    sum?: number;
 };
 
 /**
- * - `default`: perform a search query - `facet` [searches for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
+ * Redirect rule data.
  */
-type SearchTypeDefault = 'default';
+type RedirectRuleIndexData = {
+    ruleObjectID: string;
+};
 
-type SearchForHitsOptions = {
+type RedirectRuleIndexMetadata = {
     /**
-     * Index name (case-sensitive).
+     * Source index for the redirect rule.
      */
-    indexName: string;
-    type?: SearchTypeDefault;
-} & {
-    facet?: never;
-    maxFacetHits?: never;
-    facetQuery?: never;
-};
-
-type BaseSearchParamsWithoutQuery = {
+    source: string;
     /**
-     * Keywords to be used instead of the search query to conduct a more broader search.  Using the `similarQuery` parameter changes other settings:  - `queryType` is set to `prefixNone`. - `removeStopWords` is set to true. - `words` is set as the first ranking criterion. - All remaining words are treated as `optionalWords`.  Since the `similarQuery` is supposed to do a broad search, they usually return many results. Combine it with `filters` to narrow down the list of results.
+     * Destination index for the redirect rule.
      */
-    similarQuery?: string;
+    dest: string;
     /**
-     * Filter expression to only include items that match the filter criteria in the response.  You can use these filter expressions:  - **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive). - **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value. - **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive). - **Boolean filters.** `<facet>: true | false`.  You can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:  - You can only combine filters of the same type with `OR`.   **Not supported:** `facet:value OR num > 3`. - You can\'t use `NOT` with combinations of filters.   **Not supported:** `NOT(facet:value OR facet:value)` - You can\'t combine conjunctions (`AND`) with `OR`.   **Not supported:** `facet:value OR (facet:value AND facet:value)`  Use quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes. If a facet attribute is an array, the filter matches if it matches at least one element of the array.  For more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/).
+     * Reason for the redirect rule.
      */
-    filters?: string;
-    facetFilters?: FacetFilters;
-    optionalFilters?: OptionalFilters;
-    numericFilters?: NumericFilters;
-    tagFilters?: TagFilters;
+    reason: string;
     /**
-     * Whether to sum all filter scores.  If true, all filter scores are summed. Otherwise, the maximum filter score is kept. For more information, see [filter scores](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/in-depth/filter-scoring/#accumulating-scores-with-sumorfiltersscores).
+     * Redirect rule status.
      */
-    sumOrFiltersScores?: boolean;
+    succeed: boolean;
+    data: RedirectRuleIndexData;
+};
+
+/**
+ * [Redirect results to a URL](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/redirects/), this this parameter is for internal use only.
+ */
+type Redirect = {
+    index?: Array<RedirectRuleIndexMetadata>;
+};
+
+type BaseSearchResponse = Record<string, any> & {
     /**
-     * Restricts a search to a subset of your searchable attributes. Attribute names are case-sensitive.
+     * A/B test ID. This is only included in the response for indices that are part of an A/B test.
      */
-    restrictSearchableAttributes?: string[];
+    abTestID?: number;
     /**
-     * Facets for which to retrieve facet values that match the search criteria and the number of matching facet values.  To retrieve all facets, use the wildcard character `*`. For more information, see [facets](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#contextual-facet-values-and-counts).
+     * Variant ID. This is only included in the response for indices that are part of an A/B test.
      */
-    facets?: string[];
+    abTestVariantID?: number;
     /**
-     * Whether faceting should be applied after deduplication with `distinct`.  This leads to accurate facet counts when using faceting in combination with `distinct`. It\'s usually better to use `afterDistinct` modifiers in the `attributesForFaceting` setting, as `facetingAfterDistinct` only computes correct facet counts if all records have the same facet values for the `attributeForDistinct`.
+     * Computed geographical location.
      */
-    facetingAfterDistinct?: boolean;
+    aroundLatLng?: string;
     /**
-     * Page of search results to retrieve.
+     * Distance from a central coordinate provided by `aroundLatLng`.
      */
-    page?: number;
+    automaticRadius?: string;
+    exhaustive?: Exhaustive;
     /**
-     * Position of the first hit to retrieve.
+     * See the `facetsCount` field of the `exhaustive` object in the response.
      */
-    offset?: number;
+    exhaustiveFacetsCount?: boolean;
     /**
-     * Number of hits to retrieve (used in combination with `offset`).
+     * See the `nbHits` field of the `exhaustive` object in the response.
      */
-    length?: number;
+    exhaustiveNbHits?: boolean;
     /**
-     * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude.  Only records included within circle around this central location are included in the results. The radius of the circle is determined by the `aroundRadius` and `minimumAroundRadius` settings. This parameter is ignored if you also specify `insidePolygon` or `insideBoundingBox`.
+     * See the `typo` field of the `exhaustive` object in the response.
      */
-    aroundLatLng?: string;
+    exhaustiveTypo?: boolean;
     /**
-     * Whether to obtain the coordinates from the request\'s IP address.
+     * Facet counts.
      */
-    aroundLatLngViaIP?: boolean;
-    aroundRadius?: AroundRadius;
-    aroundPrecision?: AroundPrecision;
+    facets?: {
+        [key: string]: {
+            [key: string]: number;
+        };
+    };
     /**
-     * Minimum radius (in meters) for a search around a location when `aroundRadius` isn\'t set.
+     * Statistics for numerical facets.
      */
-    minimumAroundRadius?: number;
+    facets_stats?: {
+        [key: string]: FacetStats;
+    };
     /**
-     * Coordinates for a rectangular area in which to search.  Each bounding box is defined by the two opposite points of its diagonal, and expressed as latitude and longitude pair: `[p1 lat, p1 long, p2 lat, p2 long]`. Provide multiple bounding boxes as nested arrays. For more information, see [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas).
+     * Index name used for the query.
      */
-    insideBoundingBox?: number[][];
+    index?: string;
     /**
-     * Coordinates of a polygon in which to search.  Polygons are defined by 3 to 10,000 points. Each point is represented by its latitude and longitude. Provide multiple polygons as nested arrays. For more information, see [filtering inside polygons](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas). This parameter is ignored if you also specify `insideBoundingBox`.
+     * Index name used for the query. During A/B testing, the targeted index isn\'t always the index used by the query.
      */
-    insidePolygon?: number[][];
+    indexUsed?: string;
     /**
-     * ISO language codes that adjust settings that are useful for processing natural language queries (as opposed to keyword searches):  - Sets `removeStopWords` and `ignorePlurals` to the list of provided languages. - Sets `removeWordsIfNoResults` to `allOptional`. - Adds a `natural_language` attribute to `ruleContexts` and `analyticsTags`.
+     * Warnings about the query.
      */
-    naturalLanguages?: SupportedLanguage[];
+    message?: string;
     /**
-     * Assigns a rule context to the search query.  [Rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) are strings that you can use to trigger matching rules.
+     * Number of hits selected and sorted by the relevant sort algorithm.
      */
-    ruleContexts?: string[];
+    nbSortedHits?: number;
     /**
-     * Impact that Personalization should have on this search.  The higher this value is, the more Personalization determines the ranking compared to other factors. For more information, see [Understanding Personalization impact](https://www.algolia.com/doc/guides/personalization/personalizing-results/in-depth/configuring-personalization/#understanding-personalization-impact).
+     * Post-[normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/#what-does-normalization-mean) query string that will be searched.
      */
-    personalizationImpact?: number;
+    parsedQuery?: string;
     /**
-     * Unique pseudonymous or anonymous user identifier.  This helps with analytics and click and conversion events. For more information, see [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
+     * Time the server took to process the request, in milliseconds.
      */
-    userToken?: string;
+    processingTimeMS: number;
     /**
-     * Whether the search response should include detailed ranking information.
+     * Experimental. List of processing steps and their times, in milliseconds. You can use this list to investigate performance issues.
      */
-    getRankingInfo?: boolean;
+    processingTimingsMS?: Record<string, unknown>;
     /**
-     * Whether to take into account an index\'s synonyms for this search.
+     * Markup text indicating which parts of the original query have been removed to retrieve a non-empty result set.
      */
-    synonyms?: boolean;
+    queryAfterRemoval?: string;
+    redirect?: Redirect;
+    renderingContent?: RenderingContent;
     /**
-     * Whether to include a `queryID` attribute in the response.  The query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started/).
+     * Time the server took to process the request, in milliseconds.
      */
-    clickAnalytics?: boolean;
+    serverTimeMS?: number;
     /**
-     * Whether this search will be included in Analytics.
+     * Host name of the server that processed the request.
      */
-    analytics?: boolean;
+    serverUsed?: string;
     /**
-     * Tags to apply to the query for [segmenting analytics data](https://www.algolia.com/doc/guides/search-analytics/guides/segments/).
+     * An object with custom data.  You can store up to 32kB as custom data.
      */
-    analyticsTags?: string[];
+    userData?: Record<string, unknown>;
     /**
-     * Whether to include this search when calculating processing-time percentiles.
+     * Unique identifier for the query. This is used for [click analytics](https://www.algolia.com/doc/guides/analytics/click-analytics/).
      */
-    percentileComputation?: boolean;
+    queryID?: string;
     /**
-     * Whether to enable A/B testing for this search.
+     * Whether automatic events collection is enabled for the application.
      */
-    enableABTest?: boolean;
+    _automaticInsights?: boolean;
 };
 
-type BaseSearchParams = BaseSearchParamsWithoutQuery & SearchParamsQuery;
-
 /**
- * Search mode the index will use to query for results.  This setting only applies to indices, for which Algolia enabled NeuralSearch for you.
+ * Whether the whole query string matches or only a part.
  */
-type Mode = 'keywordSearch' | 'neuralSearch';
+type MatchLevel = 'none' | 'partial' | 'full';
 
 /**
- * Settings for the semantic search part of NeuralSearch. Only used when `mode` is `neuralSearch`.
+ * Surround words that match the query with HTML tags for highlighting.
  */
-type SemanticSearch = {
+type HighlightResultOption = {
     /**
-     * Indices from which to collect click and conversion events.  If null, the current index and all its replicas are used.
+     * Highlighted attribute value, including HTML tags.
      */
-    eventSources?: string[] | null;
-};
-
-type IndexSettingsAsSearchParams = {
+    value: string;
+    matchLevel: MatchLevel;
     /**
-     * Attributes to include in the API response.  To reduce the size of your response, you can retrieve only some of the attributes. Attribute names are case-sensitive.  - `*` retrieves all attributes, except attributes included in the `customRanking` and `unretrievableAttributes` settings. - To retrieve all attributes except a specific one, prefix the attribute with a dash and combine it with the `*`: `[\"*\", \"-ATTRIBUTE\"]`. - The `objectID` attribute is always included.
+     * List of matched words from the search query.
      */
-    attributesToRetrieve?: string[];
+    matchedWords: Array<string>;
     /**
-     * Determines the order in which Algolia returns your results.  By default, each entry corresponds to a [ranking criteria](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/). The tie-breaking algorithm sequentially applies each criterion in the order they\'re specified. If you configure a replica index for [sorting by an attribute](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/how-to/sort-by-attribute/), you put the sorting attribute at the top of the list.  **Modifiers**  - `asc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in ascending order. - `desc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in descending order.  Before you modify the default setting, you should test your changes in the dashboard, and by [A/B testing](https://www.algolia.com/doc/guides/ab-testing/what-is-ab-testing/).
+     * Whether the entire attribute value is highlighted.
      */
-    ranking?: string[];
+    fullyHighlighted?: boolean;
+};
+
+type HighlightResult = HighlightResultOption | {
+    [key: string]: HighlightResult;
+} | Array<HighlightResult>;
+
+type MatchedGeoLocation = {
     /**
-     * Attributes to use as [custom ranking](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/). Attribute names are case-sensitive.  The custom ranking attributes decide which items are shown first if the other ranking criteria are equal.  Records with missing values for your selected custom ranking attributes are always sorted last. Boolean attributes are sorted based on their alphabetical order.  **Modifiers**  - `asc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in ascending order.  - `desc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in descending order.  If you use two or more custom ranking attributes, [reduce the precision](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/how-to/controlling-custom-ranking-metrics-precision/) of your first attributes, or the other attributes will never be applied.
+     * Latitude of the matched location.
      */
-    customRanking?: string[];
+    lat?: number;
     /**
-     * Relevancy threshold below which less relevant results aren\'t included in the results.  You can only set `relevancyStrictness` on [virtual replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/#what-are-virtual-replicas). Use this setting to strike a balance between the relevance and number of returned results.
+     * Longitude of the matched location.
      */
-    relevancyStrictness?: number;
+    lng?: number;
     /**
-     * Attributes to highlight.  By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. Attribute names are case-sensitive.  With highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and `highlightPostTag`. You can use this to visually highlight matching parts of a search query in your UI.  For more information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js/).
+     * Distance between the matched location and the search location (in meters).
      */
-    attributesToHighlight?: string[];
+    distance?: number;
+};
+
+type Personalization = {
     /**
-     * Attributes for which to enable snippets. Attribute names are case-sensitive.  Snippets provide additional context to matched words. If you enable snippets, they include 10 words, including the matched word. The matched word will also be wrapped by HTML tags for highlighting. You can adjust the number of words with the following notation: `ATTRIBUTE:NUMBER`, where `NUMBER` is the number of words to be extracted.
+     * The score of the filters.
      */
-    attributesToSnippet?: string[];
+    filtersScore?: number;
     /**
-     * HTML tag to insert before the highlighted parts in all highlighted results and snippets.
+     * The score of the ranking.
      */
-    highlightPreTag?: string;
+    rankingScore?: number;
     /**
-     * HTML tag to insert after the highlighted parts in all highlighted results and snippets.
+     * The score of the event.
      */
-    highlightPostTag?: string;
-    /**
-     * String used as an ellipsis indicator when a snippet is truncated.
-     */
-    snippetEllipsisText?: string;
-    /**
-     * Whether to restrict highlighting and snippeting to items that at least partially matched the search query. By default, all items are highlighted and snippeted.
-     */
-    restrictHighlightAndSnippetArrays?: boolean;
+    score?: number;
+};
+
+/**
+ * Object with detailed information about the record\'s ranking.
+ */
+type RankingInfo = {
     /**
-     * Number of hits per page.
+     * Whether a filter matched the query.
      */
-    hitsPerPage?: number;
+    filters?: number;
     /**
-     * Minimum number of characters a word in the search query must contain to accept matches with [one typo](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#configuring-word-length-for-typos).
+     * Position of the first matched word in the best matching attribute of the record.
      */
-    minWordSizefor1Typo?: number;
+    firstMatchedWord: number;
     /**
-     * Minimum number of characters a word in the search query must contain to accept matches with [two typos](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#configuring-word-length-for-typos).
+     * Distance between the geo location in the search query and the best matching geo location in the record, divided by the geo precision (in meters).
      */
-    minWordSizefor2Typos?: number;
-    typoTolerance?: TypoTolerance;
+    geoDistance: number;
     /**
-     * Whether to allow typos on numbers in the search query.  Turn off this setting to reduce the number of irrelevant matches when searching in large sets of similar numbers.
+     * Precision used when computing the geo distance, in meters.
      */
-    allowTyposOnNumericTokens?: boolean;
+    geoPrecision?: number;
+    matchedGeoLocation?: MatchedGeoLocation;
+    personalization?: Personalization;
     /**
-     * Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). Attribute names are case-sensitive.  Returning only exact matches can help when:  - [Searching in hyphenated attributes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/). - Reducing the number of matches when you have too many.   This can happen with attributes that are long blocks of text, such as product descriptions.  Consider alternatives such as `disableTypoToleranceOnWords` or adding synonyms if your attributes have intentional unusual spellings that might look like typos.
+     * Number of exactly matched words.
      */
-    disableTypoToleranceOnAttributes?: string[];
-    ignorePlurals?: IgnorePlurals;
-    removeStopWords?: RemoveStopWords;
+    nbExactWords: number;
     /**
-     * Characters for which diacritics should be preserved.  By default, Algolia removes diacritics from letters. For example, `é` becomes `e`. If this causes issues in your search, you can specify characters that should keep their diacritics.
+     * Number of typos encountered when matching the record.
      */
-    keepDiacriticsOnCharacters?: string;
+    nbTypos: number;
     /**
-     * Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries.  This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` settings. This setting also sets a dictionary for word detection in the logogram-based [CJK](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/#normalization-for-logogram-based-languages-cjk) languages. To support this, you must place the CJK language **first**.  **You should always specify a query language.** If you don\'t specify an indexing language, the search engine uses all [supported languages](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to unexpected search results. For more information, see [Language-specific configuration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/).
+     * Whether the record was promoted by a rule.
      */
-    queryLanguages?: SupportedLanguage[];
+    promoted?: boolean;
     /**
-     * Whether to split compound words in the query into their building blocks.  For more information, see [Word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words). Word segmentation is supported for these languages: German, Dutch, Finnish, Swedish, and Norwegian. Decompounding doesn\'t work for words with [non-spacing mark Unicode characters](https://www.charactercodes.net/category/non-spacing_mark). For example, `Gartenstühle` won\'t be decompounded if the `ü` consists of `u` (U+0075) and `◌̈` (U+0308).
+     * Number of words between multiple matches in the query plus 1. For single word queries, `proximityDistance` is 0.
      */
-    decompoundQuery?: boolean;
+    proximityDistance?: number;
     /**
-     * Whether to enable rules.
+     * Overall ranking of the record, expressed as a single integer. This attribute is internal.
      */
-    enableRules?: boolean;
+    userScore: number;
     /**
-     * Whether to enable Personalization.
+     * Number of matched words.
      */
-    enablePersonalization?: boolean;
-    queryType?: QueryType;
-    removeWordsIfNoResults?: RemoveWordsIfNoResults;
-    mode?: Mode;
-    semanticSearch?: SemanticSearch;
+    words?: number;
     /**
-     * Whether to support phrase matching and excluding words from search queries.  Use the `advancedSyntaxFeatures` parameter to control which feature is supported.
+     * Whether the record is re-ranked.
      */
-    advancedSyntax?: boolean;
+    promotedByReRanking?: boolean;
+};
+
+/**
+ * Snippets that show the context around a matching search query.
+ */
+type SnippetResultOption = {
     /**
-     * Words that should be considered optional when found in the query.  By default, records must match all words in the search query to be included in the search results. Adding optional words can help to increase the number of search results by running an additional search query that doesn\'t include the optional words. For example, if the search query is \"action video\" and \"video\" is an optional word, the search engine runs two queries. One for \"action video\" and one for \"action\". Records that match all words are ranked higher.  For a search query with 4 or more words **and** all its words are optional, the number of matched words required for a record to be included in the search results increases for every 1,000 records:  - If `optionalWords` has less than 10 words, the required number of matched words increases by 1:   results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 2 matched words. - If `optionalWords` has 10 or more words, the number of required matched words increases by the number of optional words dividied by 5 (rounded down).   For example, with 18 optional words: results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 4 matched words.  For more information, see [Optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).
+     * Highlighted attribute value, including HTML tags.
      */
-    optionalWords?: string[];
+    value: string;
+    matchLevel: MatchLevel;
+};
+
+type SnippetResult = SnippetResultOption | {
+    [key: string]: SnippetResult;
+} | Array<SnippetResult>;
+
+/**
+ * Recommend hit.
+ */
+type RecommendHit = Record<string, any> & {
     /**
-     * Searchable attributes for which you want to [turn off the Exact ranking criterion](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/adjust-exact-settings/#turn-off-exact-for-some-attributes). Attribute names are case-sensitive.  This can be useful for attributes with long values, where the likelyhood of an exact match is high, such as product descriptions. Turning off the Exact ranking criterion for these attributes favors exact matching on other attributes. This reduces the impact of individual attributes with a lot of content on ranking.
+     * Unique record identifier.
      */
-    disableExactOnAttributes?: string[];
-    exactOnSingleWordQuery?: ExactOnSingleWordQuery;
+    objectID: string;
     /**
-     * Alternatives of query words that should be considered as exact matches by the Exact ranking criterion.  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY/NYC\" are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY/New York\" are considered exact matches.
+     * Surround words that match the query with HTML tags for highlighting.
      */
-    alternativesAsExact?: AlternativesAsExact[];
+    _highlightResult?: {
+        [key: string]: HighlightResult;
+    };
     /**
-     * Advanced search syntax features you want to support.  - `exactPhrase`.   Phrases in quotes must match exactly.   For example, `sparkly blue \"iPhone case\"` only returns records with the exact string \"iPhone case\".  - `excludeWords`.   Query words prefixed with a `-` must not occur in a record.   For example, `search -engine` matches records that contain \"search\" but not \"engine\".  This setting only has an effect if `advancedSyntax` is true.
+     * Snippets that show the context around a matching search query.
      */
-    advancedSyntaxFeatures?: AdvancedSyntaxFeatures[];
-    distinct?: Distinct;
+    _snippetResult?: {
+        [key: string]: SnippetResult;
+    };
+    _rankingInfo?: RankingInfo;
+    _distinctSeqID?: number;
     /**
-     * Whether to replace a highlighted word with the matched synonym.  By default, the original words are highlighted even if a synonym matches. For example, with `home` as a synonym for `house` and a search for `home`, records matching either \"home\" or \"house\" are included in the search results, and either \"home\" or \"house\" are highlighted.  With `replaceSynonymsInHighlight` set to `true`, a search for `home` still matches the same records, but all occurences of \"house\" are replaced by \"home\" in the highlighted response.
+     * Recommendation score.
      */
-    replaceSynonymsInHighlight?: boolean;
+    _score: number;
+};
+
+/**
+ * Trending facet hit.
+ */
+type TrendingFacetHit = {
     /**
-     * Minimum proximity score for two matching words.  This adjusts the [Proximity ranking criterion](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#proximity) by equally scoring matches that are farther apart.  For example, if `minProximity` is 2, neighboring matches and matches with one word between them would have the same score.
+     * Recommendation score.
      */
-    minProximity?: number;
+    _score: number;
     /**
-     * Properties to include in the API response of `search` and `browse` requests.  By default, all response properties are included. To reduce the response size, you can select, which attributes should be included.  You can\'t exclude these properties: `message`, `warning`, `cursor`, `serverUsed`, `indexUsed`, `abTestVariantID`, `parsedQuery`, or any property triggered by the `getRankingInfo` parameter.  Don\'t exclude properties that you might need in your search UI.
+     * Facet attribute. To be used in combination with `facetValue`. If specified, only recommendations matching the facet filter will be returned.
      */
-    responseFields?: string[];
+    facetName: string;
     /**
-     * Maximum number of facet values to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
+     * Facet value. To be used in combination with `facetName`. If specified, only recommendations matching the facet filter will be returned.
      */
-    maxFacetHits?: number;
+    facetValue: string;
+};
+
+type RecommendationsHit = RecommendHit | TrendingFacetHit;
+
+type RecommendationsHits = {
+    hits: Array<RecommendationsHit>;
+};
+
+type SearchPagination = {
     /**
-     * Maximum number of facet values to return for each facet.
+     * Page of search results to retrieve.
      */
-    maxValuesPerFacet?: number;
+    page?: number;
     /**
-     * Order in which to retrieve facet values.  - `count`.   Facet values are retrieved by decreasing count.   The count is the number of matching records containing this facet value.  - `alpha`.   Retrieve facet values alphabetically.  This setting doesn\'t influence how facet values are displayed in your UI (see `renderingContent`). For more information, see [facet value display](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/facet-display/js/).
+     * Number of results (hits).
      */
-    sortFacetValuesBy?: string;
+    nbHits?: number;
     /**
-     * Whether the best matching attribute should be determined by minimum proximity.  This setting only affects ranking if the Attribute ranking criterion comes before Proximity in the `ranking` setting. If true, the best matching attribute is selected based on the minimum proximity of multiple matches. Otherwise, the best matching attribute is determined by the order in the `searchableAttributes` setting.
+     * Number of pages of results.
      */
-    attributeCriteriaComputedByMinProximity?: boolean;
-    renderingContent?: RenderingContent;
+    nbPages?: number;
     /**
-     * Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/).  This setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
+     * Number of hits per page.
      */
-    enableReRanking?: boolean;
-    reRankingApplyFilter?: ReRankingApplyFilter | null;
+    hitsPerPage?: number;
 };
 
-/**
- * Each parameter value, including the `query` must not be larger than 512 bytes.
- */
-type SearchParamsObject = BaseSearchParams & IndexSettingsAsSearchParams;
+type RecommendationsResults = BaseSearchResponse & SearchPagination & RecommendationsHits;
+
+type GetRecommendationsResponse = {
+    results: Array<RecommendationsResults>;
+};
 
 /**
- * Properties for the `customPost` method.
+ * - `default`: perform a search query - `facet` [searches for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
  */
-type CustomPostProps = {
+type SearchTypeFacet = 'facet';
+
+type SearchForFacetsOptions = {
     /**
-     * Path of the endpoint, anything after \"/1\" must be specified.
+     * Facet name.
      */
-    path: string;
+    facet: string;
     /**
-     * Query parameters to apply to the current query.
+     * Index name (case-sensitive).
      */
-    parameters?: Record<string, any>;
+    indexName: string;
     /**
-     * Parameters to send with the custom request.
+     * Text to search inside the facet\'s values.
      */
-    body?: Record<string, unknown>;
-};
-/**
- * Recommend method signature compatible with the `algoliasearch` v4 package. When using this signature, extra computation will be required to make it match the new signature.
- *
- * @deprecated This signature will be removed from the next major version, we recommend using the `GetRecommendationsParams` type for performances and future proof reasons.
- */
-type LegacyGetRecommendationsParams = RecommendationsRequest[];
-/**
- * In v4, the search parameters are wrapped in a `params` parameter.
- *
- * @deprecated The `search` method now accepts flat `searchParams` at the root of the method.
- */
-type LegacySearchParams = {
-    params?: SearchParamsObject;
-};
-/**
- * In v4, the search parameters are wrapped in a `params` parameter.
- *
- * @deprecated The `search` method now accepts flat `searchParams` at the root of the method.
- */
-type LegacySearchForFacets = LegacySearchParams & SearchForFacetsOptions;
-/**
- * In v4, the search parameters are wrapped in a `params` parameter.
- *
- * @deprecated The `search` method now accepts flat `searchParams` at the root of the method.
- */
-type LegacySearchForHits = LegacySearchParams & SearchForHitsOptions;
-type LegacySearchQuery = LegacySearchForFacets | LegacySearchForHits;
-/**
- * Search method signature compatible with the `algoliasearch` v4 package. When using this signature, extra computation will be required to make it match the new signature.
- *
- * @deprecated This signature will be removed from the next major version, we recommend using the `SearchMethodParams` type for performances and future proof reasons.
- */
-type LegacySearchMethodProps = LegacySearchQuery[];
-
-/**
- * Recommend request body.
- */
-type GetRecommendationsParams = {
+    facetQuery?: string;
     /**
-     * Recommendation request with parameters depending on the requested model.
+     * Maximum number of facet values to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
      */
-    requests: RecommendationsRequest[];
+    maxFacetHits?: number;
+    type: SearchTypeFacet;
 };
 
-/**
- * Whether certain properties of the search response are calculated exhaustive (exact) or approximated.
- */
-type Exhaustive = {
-    /**
-     * Whether the facet count is exhaustive (`true`) or approximate (`false`). See the [related discussion](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-).
-     */
-    facetsCount?: boolean;
+type BaseSearchParamsWithoutQuery = {
     /**
-     * The value is `false` if not all facet values are retrieved.
+     * Keywords to be used instead of the search query to conduct a more broader search.  Using the `similarQuery` parameter changes other settings:  - `queryType` is set to `prefixNone`. - `removeStopWords` is set to true. - `words` is set as the first ranking criterion. - All remaining words are treated as `optionalWords`.  Since the `similarQuery` is supposed to do a broad search, they usually return many results. Combine it with `filters` to narrow down the list of results.
      */
-    facetValues?: boolean;
+    similarQuery?: string;
     /**
-     * Whether the `nbHits` is exhaustive (`true`) or approximate (`false`). When the query takes more than 50ms to be processed, the engine makes an approximation. This can happen when using complex filters on millions of records, when typo-tolerance was not exhaustive, or when enough hits have been retrieved (for example, after the engine finds 10,000 exact matches). `nbHits` is reported as non-exhaustive whenever an approximation is made, even if the approximation didn’t, in the end, impact the exhaustivity of the query.
+     * Filter expression to only include items that match the filter criteria in the response.  You can use these filter expressions:  - **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`. - **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive). - **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value. - **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive). - **Boolean filters.** `<facet>: true | false`.  You can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:  - You can only combine filters of the same type with `OR`.   **Not supported:** `facet:value OR num > 3`. - You can\'t use `NOT` with combinations of filters.   **Not supported:** `NOT(facet:value OR facet:value)` - You can\'t combine conjunctions (`AND`) with `OR`.   **Not supported:** `facet:value OR (facet:value AND facet:value)`  Use quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes. If a facet attribute is an array, the filter matches if it matches at least one element of the array.  For more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/).
      */
-    nbHits?: boolean;
+    filters?: string;
+    facetFilters?: FacetFilters;
+    optionalFilters?: OptionalFilters;
+    numericFilters?: NumericFilters;
+    tagFilters?: TagFilters;
     /**
-     * Rules matching exhaustivity. The value is `false` if rules were enable for this query, and could not be fully processed due a timeout. This is generally caused by the number of alternatives (such as typos) which is too large.
+     * Whether to sum all filter scores.  If true, all filter scores are summed. Otherwise, the maximum filter score is kept. For more information, see [filter scores](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/in-depth/filter-scoring/#accumulating-scores-with-sumorfiltersscores).
      */
-    rulesMatch?: boolean;
+    sumOrFiltersScores?: boolean;
     /**
-     * Whether the typo search was exhaustive (`true`) or approximate (`false`). An approximation is done when the typo search query part takes more than 10% of the query budget (ie. 5ms by default) to be processed (this can happen when a lot of typo alternatives exist for the query). This field will not be included when typo-tolerance is entirely disabled.
+     * Restricts a search to a subset of your searchable attributes. Attribute names are case-sensitive.
      */
-    typo?: boolean;
-};
-
-type FacetStats = {
+    restrictSearchableAttributes?: Array<string>;
     /**
-     * Minimum value in the results.
+     * Facets for which to retrieve facet values that match the search criteria and the number of matching facet values.  To retrieve all facets, use the wildcard character `*`. For more information, see [facets](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#contextual-facet-values-and-counts).
      */
-    min?: number;
+    facets?: Array<string>;
     /**
-     * Maximum value in the results.
+     * Whether faceting should be applied after deduplication with `distinct`.  This leads to accurate facet counts when using faceting in combination with `distinct`. It\'s usually better to use `afterDistinct` modifiers in the `attributesForFaceting` setting, as `facetingAfterDistinct` only computes correct facet counts if all records have the same facet values for the `attributeForDistinct`.
      */
-    max?: number;
+    facetingAfterDistinct?: boolean;
     /**
-     * Average facet value in the results.
+     * Page of search results to retrieve.
      */
-    avg?: number;
+    page?: number;
     /**
-     * Sum of all values in the results.
+     * Position of the first hit to retrieve.
      */
-    sum?: number;
-};
-
-/**
- * Redirect rule data.
- */
-type RedirectRuleIndexData = {
-    ruleObjectID: string;
-};
-
-type RedirectRuleIndexMetadata = {
+    offset?: number;
     /**
-     * Source index for the redirect rule.
+     * Number of hits to retrieve (used in combination with `offset`).
      */
-    source: string;
+    length?: number;
     /**
-     * Destination index for the redirect rule.
+     * Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude.  Only records included within a circle around this central location are included in the results. The radius of the circle is determined by the `aroundRadius` and `minimumAroundRadius` settings. This parameter is ignored if you also specify `insidePolygon` or `insideBoundingBox`.
      */
-    dest: string;
+    aroundLatLng?: string;
     /**
-     * Reason for the redirect rule.
+     * Whether to obtain the coordinates from the request\'s IP address.
      */
-    reason: string;
+    aroundLatLngViaIP?: boolean;
+    aroundRadius?: AroundRadius;
+    aroundPrecision?: AroundPrecision;
     /**
-     * Redirect rule status.
+     * Minimum radius (in meters) for a search around a location when `aroundRadius` isn\'t set.
      */
-    succeed: boolean;
-    data: RedirectRuleIndexData;
-};
-
-/**
- * [Redirect results to a URL](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/redirects/), this this parameter is for internal use only.
- */
-type Redirect = {
-    index?: RedirectRuleIndexMetadata[];
-};
-
-type BaseSearchResponse = Record<string, any> & {
+    minimumAroundRadius?: number;
     /**
-     * A/B test ID. This is only included in the response for indices that are part of an A/B test.
+     * Coordinates for a rectangular area in which to search.  Each bounding box is defined by the two opposite points of its diagonal, and expressed as latitude and longitude pair: `[p1 lat, p1 long, p2 lat, p2 long]`. Provide multiple bounding boxes as nested arrays. For more information, see [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas).
      */
-    abTestID?: number;
+    insideBoundingBox?: Array<Array<number>>;
     /**
-     * Variant ID. This is only included in the response for indices that are part of an A/B test.
+     * Coordinates of a polygon in which to search.  Polygons are defined by 3 to 10,000 points. Each point is represented by its latitude and longitude. Provide multiple polygons as nested arrays. For more information, see [filtering inside polygons](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas). This parameter is ignored if you also specify `insideBoundingBox`.
      */
-    abTestVariantID?: number;
+    insidePolygon?: Array<Array<number>>;
     /**
-     * Computed geographical location.
+     * ISO language codes that adjust settings that are useful for processing natural language queries (as opposed to keyword searches):  - Sets `removeStopWords` and `ignorePlurals` to the list of provided languages. - Sets `removeWordsIfNoResults` to `allOptional`. - Adds a `natural_language` attribute to `ruleContexts` and `analyticsTags`.
      */
-    aroundLatLng?: string;
+    naturalLanguages?: Array<SupportedLanguage>;
     /**
-     * Distance from a central coordinate provided by `aroundLatLng`.
+     * Assigns a rule context to the search query.  [Rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) are strings that you can use to trigger matching rules.
      */
-    automaticRadius?: string;
-    exhaustive?: Exhaustive;
+    ruleContexts?: Array<string>;
     /**
-     * See the `facetsCount` field of the `exhaustive` object in the response.
+     * Impact that Personalization should have on this search.  The higher this value is, the more Personalization determines the ranking compared to other factors. For more information, see [Understanding Personalization impact](https://www.algolia.com/doc/guides/personalization/personalizing-results/in-depth/configuring-personalization/#understanding-personalization-impact).
      */
-    exhaustiveFacetsCount?: boolean;
+    personalizationImpact?: number;
     /**
-     * See the `nbHits` field of the `exhaustive` object in the response.
+     * Unique pseudonymous or anonymous user identifier.  This helps with analytics and click and conversion events. For more information, see [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).
      */
-    exhaustiveNbHits?: boolean;
+    userToken?: string;
     /**
-     * See the `typo` field of the `exhaustive` object in the response.
+     * Whether the search response should include detailed ranking information.
      */
-    exhaustiveTypo?: boolean;
+    getRankingInfo?: boolean;
     /**
-     * Facet counts.
+     * Whether to take into account an index\'s synonyms for this search.
      */
-    facets?: Record<string, Record<string, number>>;
+    synonyms?: boolean;
     /**
-     * Statistics for numerical facets.
+     * Whether to include a `queryID` attribute in the response.  The query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started/).
      */
-    facets_stats?: Record<string, FacetStats>;
+    clickAnalytics?: boolean;
     /**
-     * Index name used for the query.
+     * Whether this search will be included in Analytics.
      */
-    index?: string;
+    analytics?: boolean;
     /**
-     * Index name used for the query. During A/B testing, the targeted index isn\'t always the index used by the query.
+     * Tags to apply to the query for [segmenting analytics data](https://www.algolia.com/doc/guides/search-analytics/guides/segments/).
      */
-    indexUsed?: string;
+    analyticsTags?: Array<string>;
     /**
-     * Warnings about the query.
+     * Whether to include this search when calculating processing-time percentiles.
      */
-    message?: string;
+    percentileComputation?: boolean;
     /**
-     * Number of hits selected and sorted by the relevant sort algorithm.
+     * Whether to enable A/B testing for this search.
      */
-    nbSortedHits?: number;
+    enableABTest?: boolean;
+};
+
+type BaseSearchParams = SearchParamsQuery & BaseSearchParamsWithoutQuery;
+
+/**
+ * Search mode the index will use to query for results.  This setting only applies to indices, for which Algolia enabled NeuralSearch for you.
+ */
+type Mode = 'neuralSearch' | 'keywordSearch';
+
+/**
+ * Settings for the semantic search part of NeuralSearch. Only used when `mode` is `neuralSearch`.
+ */
+type SemanticSearch = {
     /**
-     * Post-[normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/#what-does-normalization-mean) query string that will be searched.
+     * Indices from which to collect click and conversion events.  If null, the current index and all its replicas are used.
      */
-    parsedQuery?: string;
+    eventSources?: Array<string> | null;
+};
+
+type IndexSettingsAsSearchParams = {
     /**
-     * Time the server took to process the request, in milliseconds.
+     * Attributes to include in the API response.  To reduce the size of your response, you can retrieve only some of the attributes. Attribute names are case-sensitive.  - `*` retrieves all attributes, except attributes included in the `customRanking` and `unretrievableAttributes` settings. - To retrieve all attributes except a specific one, prefix the attribute with a dash and combine it with the `*`: `[\"*\", \"-ATTRIBUTE\"]`. - The `objectID` attribute is always included.
      */
-    processingTimeMS: number;
+    attributesToRetrieve?: Array<string>;
     /**
-     * Experimental. List of processing steps and their times, in milliseconds. You can use this list to investigate performance issues.
+     * Determines the order in which Algolia returns your results.  By default, each entry corresponds to a [ranking criteria](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/). The tie-breaking algorithm sequentially applies each criterion in the order they\'re specified. If you configure a replica index for [sorting by an attribute](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/how-to/sort-by-attribute/), you put the sorting attribute at the top of the list.  **Modifiers**  - `asc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in ascending order. - `desc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in descending order.  Before you modify the default setting, you should test your changes in the dashboard, and by [A/B testing](https://www.algolia.com/doc/guides/ab-testing/what-is-ab-testing/).
      */
-    processingTimingsMS?: Record<string, unknown>;
+    ranking?: Array<string>;
     /**
-     * Markup text indicating which parts of the original query have been removed to retrieve a non-empty result set.
+     * Attributes to use as [custom ranking](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/). Attribute names are case-sensitive.  The custom ranking attributes decide which items are shown first if the other ranking criteria are equal.  Records with missing values for your selected custom ranking attributes are always sorted last. Boolean attributes are sorted based on their alphabetical order.  **Modifiers**  - `asc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in ascending order.  - `desc(\"ATTRIBUTE\")`.   Sort the index by the values of an attribute, in descending order.  If you use two or more custom ranking attributes, [reduce the precision](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/how-to/controlling-custom-ranking-metrics-precision/) of your first attributes, or the other attributes will never be applied.
      */
-    queryAfterRemoval?: string;
-    redirect?: Redirect;
-    renderingContent?: RenderingContent;
+    customRanking?: Array<string>;
     /**
-     * Time the server took to process the request, in milliseconds.
+     * Relevancy threshold below which less relevant results aren\'t included in the results.  You can only set `relevancyStrictness` on [virtual replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/#what-are-virtual-replicas). Use this setting to strike a balance between the relevance and number of returned results.
      */
-    serverTimeMS?: number;
+    relevancyStrictness?: number;
     /**
-     * Host name of the server that processed the request.
+     * Attributes to highlight.  By default, all searchable attributes are highlighted. Use `*` to highlight all attributes or use an empty array `[]` to turn off highlighting. Attribute names are case-sensitive.  With highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and `highlightPostTag`. You can use this to visually highlight matching parts of a search query in your UI.  For more information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js/).
      */
-    serverUsed?: string;
+    attributesToHighlight?: Array<string>;
     /**
-     * An object with custom data.  You can store up to 32kB as custom data.
+     * Attributes for which to enable snippets. Attribute names are case-sensitive.  Snippets provide additional context to matched words. If you enable snippets, they include 10 words, including the matched word. The matched word will also be wrapped by HTML tags for highlighting. You can adjust the number of words with the following notation: `ATTRIBUTE:NUMBER`, where `NUMBER` is the number of words to be extracted.
      */
-    userData?: Record<string, unknown>;
+    attributesToSnippet?: Array<string>;
     /**
-     * Unique identifier for the query. This is used for [click analytics](https://www.algolia.com/doc/guides/analytics/click-analytics/).
+     * HTML tag to insert before the highlighted parts in all highlighted results and snippets.
      */
-    queryID?: string;
+    highlightPreTag?: string;
     /**
-     * Whether automatic events collection is enabled for the application.
+     * HTML tag to insert after the highlighted parts in all highlighted results and snippets.
      */
-    _automaticInsights?: boolean;
-};
-
-/**
- * Whether the whole query string matches or only a part.
- */
-type MatchLevel = 'full' | 'none' | 'partial';
-
-/**
- * Surround words that match the query with HTML tags for highlighting.
- */
-type HighlightResultOption = {
+    highlightPostTag?: string;
     /**
-     * Highlighted attribute value, including HTML tags.
+     * String used as an ellipsis indicator when a snippet is truncated.
      */
-    value: string;
-    matchLevel: MatchLevel;
+    snippetEllipsisText?: string;
     /**
-     * List of matched words from the search query.
+     * Whether to restrict highlighting and snippeting to items that at least partially matched the search query. By default, all items are highlighted and snippeted.
      */
-    matchedWords: string[];
+    restrictHighlightAndSnippetArrays?: boolean;
     /**
-     * Whether the entire attribute value is highlighted.
+     * Number of hits per page.
      */
-    fullyHighlighted?: boolean;
-};
-
-type HighlightResult = HighlightResult[] | HighlightResultOption | {
-    [key: string]: HighlightResult;
-};
-
-type MatchedGeoLocation = {
+    hitsPerPage?: number;
     /**
-     * Latitude of the matched location.
+     * Minimum number of characters a word in the search query must contain to accept matches with [one typo](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#configuring-word-length-for-typos).
      */
-    lat?: number;
+    minWordSizefor1Typo?: number;
     /**
-     * Longitude of the matched location.
+     * Minimum number of characters a word in the search query must contain to accept matches with [two typos](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#configuring-word-length-for-typos).
      */
-    lng?: number;
+    minWordSizefor2Typos?: number;
+    typoTolerance?: TypoTolerance;
     /**
-     * Distance between the matched location and the search location (in meters).
+     * Whether to allow typos on numbers in the search query.  Turn off this setting to reduce the number of irrelevant matches when searching in large sets of similar numbers.
      */
-    distance?: number;
-};
-
-type Personalization = {
+    allowTyposOnNumericTokens?: boolean;
     /**
-     * The score of the filters.
+     * Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/). Attribute names are case-sensitive.  Returning only exact matches can help when:  - [Searching in hyphenated attributes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/). - Reducing the number of matches when you have too many.   This can happen with attributes that are long blocks of text, such as product descriptions.  Consider alternatives such as `disableTypoToleranceOnWords` or adding synonyms if your attributes have intentional unusual spellings that might look like typos.
      */
-    filtersScore?: number;
+    disableTypoToleranceOnAttributes?: Array<string>;
+    ignorePlurals?: IgnorePlurals;
+    removeStopWords?: RemoveStopWords;
     /**
-     * The score of the ranking.
+     * Characters for which diacritics should be preserved.  By default, Algolia removes diacritics from letters. For example, `é` becomes `e`. If this causes issues in your search, you can specify characters that should keep their diacritics.
      */
-    rankingScore?: number;
+    keepDiacriticsOnCharacters?: string;
     /**
-     * The score of the event.
+     * Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries.  This setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` settings. This setting also sets a dictionary for word detection in the logogram-based [CJK](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/#normalization-for-logogram-based-languages-cjk) languages. To support this, you must place the CJK language **first**.  **You should always specify a query language.** If you don\'t specify an indexing language, the search engine uses all [supported languages](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/), or the languages you specified with the `ignorePlurals` or `removeStopWords` parameters. This can lead to unexpected search results. For more information, see [Language-specific configuration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/).
      */
-    score?: number;
-};
-
-/**
- * Object with detailed information about the record\'s ranking.
- */
-type RankingInfo = {
+    queryLanguages?: Array<SupportedLanguage>;
     /**
-     * Whether a filter matched the query.
+     * Whether to split compound words in the query into their building blocks.  For more information, see [Word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words). Word segmentation is supported for these languages: German, Dutch, Finnish, Swedish, and Norwegian. Decompounding doesn\'t work for words with [non-spacing mark Unicode characters](https://www.charactercodes.net/category/non-spacing_mark). For example, `Gartenstühle` won\'t be decompounded if the `ü` consists of `u` (U+0075) and `◌̈` (U+0308).
      */
-    filters?: number;
+    decompoundQuery?: boolean;
     /**
-     * Position of the first matched word in the best matching attribute of the record.
+     * Whether to enable rules.
      */
-    firstMatchedWord: number;
+    enableRules?: boolean;
     /**
-     * Distance between the geo location in the search query and the best matching geo location in the record, divided by the geo precision (in meters).
+     * Whether to enable Personalization.
      */
-    geoDistance: number;
+    enablePersonalization?: boolean;
+    queryType?: QueryType;
+    removeWordsIfNoResults?: RemoveWordsIfNoResults;
+    mode?: Mode;
+    semanticSearch?: SemanticSearch;
     /**
-     * Precision used when computing the geo distance, in meters.
+     * Whether to support phrase matching and excluding words from search queries.  Use the `advancedSyntaxFeatures` parameter to control which feature is supported.
      */
-    geoPrecision?: number;
-    matchedGeoLocation?: MatchedGeoLocation;
-    personalization?: Personalization;
+    advancedSyntax?: boolean;
     /**
-     * Number of exactly matched words.
+     * Words that should be considered optional when found in the query.  By default, records must match all words in the search query to be included in the search results. Adding optional words can help to increase the number of search results by running an additional search query that doesn\'t include the optional words. For example, if the search query is \"action video\" and \"video\" is an optional word, the search engine runs two queries. One for \"action video\" and one for \"action\". Records that match all words are ranked higher.  For a search query with 4 or more words **and** all its words are optional, the number of matched words required for a record to be included in the search results increases for every 1,000 records:  - If `optionalWords` has less than 10 words, the required number of matched words increases by 1:   results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 2 matched words. - If `optionalWords` has 10 or more words, the number of required matched words increases by the number of optional words divided by 5 (rounded down).   For example, with 18 optional words: results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 4 matched words.  For more information, see [Optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).
      */
-    nbExactWords: number;
+    optionalWords?: Array<string>;
     /**
-     * Number of typos encountered when matching the record.
+     * Searchable attributes for which you want to [turn off the Exact ranking criterion](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/adjust-exact-settings/#turn-off-exact-for-some-attributes). Attribute names are case-sensitive.  This can be useful for attributes with long values, where the likelihood of an exact match is high, such as product descriptions. Turning off the Exact ranking criterion for these attributes favors exact matching on other attributes. This reduces the impact of individual attributes with a lot of content on ranking.
      */
-    nbTypos: number;
+    disableExactOnAttributes?: Array<string>;
+    exactOnSingleWordQuery?: ExactOnSingleWordQuery;
     /**
-     * Whether the record was promoted by a rule.
+     * Alternatives of query words that should be considered as exact matches by the Exact ranking criterion.  - `ignorePlurals`.   Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches.  - `singleWordSynonym`.   Single-word synonyms, such as \"NY/NYC\" are considered exact matches.  - `multiWordsSynonym`.   Multi-word synonyms, such as \"NY/New York\" are considered exact matches.
      */
-    promoted?: boolean;
+    alternativesAsExact?: Array<AlternativesAsExact>;
     /**
-     * Number of words between multiple matches in the query plus 1. For single word queries, `proximityDistance` is 0.
+     * Advanced search syntax features you want to support.  - `exactPhrase`.   Phrases in quotes must match exactly.   For example, `sparkly blue \"iPhone case\"` only returns records with the exact string \"iPhone case\".  - `excludeWords`.   Query words prefixed with a `-` must not occur in a record.   For example, `search -engine` matches records that contain \"search\" but not \"engine\".  This setting only has an effect if `advancedSyntax` is true.
      */
-    proximityDistance?: number;
+    advancedSyntaxFeatures?: Array<AdvancedSyntaxFeatures>;
+    distinct?: Distinct;
     /**
-     * Overall ranking of the record, expressed as a single integer. This attribute is internal.
+     * Whether to replace a highlighted word with the matched synonym.  By default, the original words are highlighted even if a synonym matches. For example, with `home` as a synonym for `house` and a search for `home`, records matching either \"home\" or \"house\" are included in the search results, and either \"home\" or \"house\" are highlighted.  With `replaceSynonymsInHighlight` set to `true`, a search for `home` still matches the same records, but all occurrences of \"house\" are replaced by \"home\" in the highlighted response.
      */
-    userScore: number;
+    replaceSynonymsInHighlight?: boolean;
     /**
-     * Number of matched words.
+     * Minimum proximity score for two matching words.  This adjusts the [Proximity ranking criterion](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#proximity) by equally scoring matches that are farther apart.  For example, if `minProximity` is 2, neighboring matches and matches with one word between them would have the same score.
      */
-    words?: number;
+    minProximity?: number;
     /**
-     * Whether the record is re-ranked.
+     * Properties to include in the API response of `search` and `browse` requests.  By default, all response properties are included. To reduce the response size, you can select, which attributes should be included.  You can\'t exclude these properties: `message`, `warning`, `cursor`, `serverUsed`, `indexUsed`, `abTestVariantID`, `parsedQuery`, or any property triggered by the `getRankingInfo` parameter.  Don\'t exclude properties that you might need in your search UI.
      */
-    promotedByReRanking?: boolean;
-};
-
-/**
- * Snippets that show the context around a matching search query.
- */
-type SnippetResultOption = {
+    responseFields?: Array<string>;
     /**
-     * Highlighted attribute value, including HTML tags.
+     * Maximum number of facet values to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
      */
-    value: string;
-    matchLevel: MatchLevel;
-};
-
-type SnippetResult = SnippetResult[] | SnippetResultOption | {
-    [key: string]: SnippetResult;
-};
-
-/**
- * Recommend hit.
- */
-type RecommendHit = Record<string, any> & {
+    maxFacetHits?: number;
     /**
-     * Unique record identifier.
+     * Maximum number of facet values to return for each facet.
      */
-    objectID: string;
+    maxValuesPerFacet?: number;
     /**
-     * Surround words that match the query with HTML tags for highlighting.
+     * Order in which to retrieve facet values.  - `count`.   Facet values are retrieved by decreasing count.   The count is the number of matching records containing this facet value.  - `alpha`.   Retrieve facet values alphabetically.  This setting doesn\'t influence how facet values are displayed in your UI (see `renderingContent`). For more information, see [facet value display](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/facet-display/js/).
      */
-    _highlightResult?: Record<string, HighlightResult>;
+    sortFacetValuesBy?: string;
     /**
-     * Snippets that show the context around a matching search query.
+     * Whether the best matching attribute should be determined by minimum proximity.  This setting only affects ranking if the Attribute ranking criterion comes before Proximity in the `ranking` setting. If true, the best matching attribute is selected based on the minimum proximity of multiple matches. Otherwise, the best matching attribute is determined by the order in the `searchableAttributes` setting.
      */
-    _snippetResult?: Record<string, SnippetResult>;
-    _rankingInfo?: RankingInfo;
-    _distinctSeqID?: number;
+    attributeCriteriaComputedByMinProximity?: boolean;
+    renderingContent?: RenderingContent;
     /**
-     * Recommendation score.
+     * Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/).  This setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.
      */
-    _score: number;
+    enableReRanking?: boolean;
+    reRankingApplyFilter?: ReRankingApplyFilter | null;
 };
 
 /**
- * Trending facet hit.
+ * Each parameter value, including the `query` must not be larger than 512 bytes.
  */
-type TrendingFacetHit = {
-    /**
-     * Recommendation score.
-     */
-    _score: number;
-    /**
-     * Facet attribute. To be used in combination with `facetValue`. If specified, only recommendations matching the facet filter will be returned.
-     */
-    facetName: string;
+type SearchParamsObject = BaseSearchParams & IndexSettingsAsSearchParams;
+
+/**
+ * Search parameters as query string.
+ */
+type SearchParamsString = {
     /**
-     * Facet value. To be used in combination with `facetName`. If specified, only recommendations matching the facet filter will be returned.
+     * Search parameters as a URL-encoded query string.
      */
-    facetValue: string;
+    params?: string;
 };
 
-type RecommendationsHit = RecommendHit | TrendingFacetHit;
+type SearchParams = SearchParamsString | SearchParamsObject;
 
-type RecommendationsHits = {
-    hits: RecommendationsHit[];
-};
+type SearchForFacets = SearchParams & SearchForFacetsOptions;
 
-type SearchPagination = {
-    /**
-     * Page of search results to retrieve.
-     */
-    page?: number;
-    /**
-     * Number of results (hits).
-     */
-    nbHits?: number;
-    /**
-     * Number of pages of results.
-     */
-    nbPages?: number;
+/**
+ * - `default`: perform a search query - `facet` [searches for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).
+ */
+type SearchTypeDefault = 'default';
+
+type SearchForHitsOptions = {
     /**
-     * Number of hits per page.
+     * Index name (case-sensitive).
      */
-    hitsPerPage?: number;
+    indexName: string;
+    type?: SearchTypeDefault;
+} & {
+    facet?: never;
+    maxFacetHits?: never;
+    facetQuery?: never;
 };
 
-type RecommendationsResults = BaseSearchResponse & RecommendationsHits & SearchPagination;
+type SearchForHits = SearchParams & SearchForHitsOptions;
 
-type GetRecommendationsResponse = {
-    results: RecommendationsResults[];
+type SearchQuery = SearchForHits | SearchForFacets;
+
+/**
+ * Strategy for multiple search queries:  - `none`. Run all queries. - `stopIfEnoughMatches`. Run the queries one by one, stopping as soon as a query matches at least the `hitsPerPage` number of results.
+ */
+type SearchStrategy = 'none' | 'stopIfEnoughMatches';
+
+type SearchMethodParams = {
+    requests: Array<SearchQuery>;
+    strategy?: SearchStrategy;
 };
 
 type FacetHits = {
@@ -1361,7 +1399,7 @@ type SearchForFacetValuesResponse = {
     /**
      * Matching facet values.
      */
-    facetHits: FacetHits[];
+    facetHits: Array<FacetHits>;
     /**
      * Whether the facet count is exhaustive (true) or approximate (false). For more information, see [Why are my facet and hit counts not accurate](https://support.algolia.com/hc/en-us/articles/4406975248145-Why-are-my-facet-and-hit-counts-not-accurate-).
      */
@@ -1372,34 +1410,6 @@ type SearchForFacetValuesResponse = {
     processingTimeMS?: number;
 };
 
-/**
- * Search parameters as query string.
- */
-type SearchParamsString = {
-    /**
-     * Search parameters as a URL-encoded query string.
-     */
-    params?: string;
-};
-
-type SearchParams = SearchParamsObject | SearchParamsString;
-
-type SearchForFacets = SearchForFacetsOptions & SearchParams;
-
-type SearchForHits = SearchForHitsOptions & SearchParams;
-
-type SearchQuery = SearchForFacets | SearchForHits;
-
-/**
- * Strategy for multiple search queries:  - `none`. Run all queries. - `stopIfEnoughMatches`. Run the queries one by one, stopping as soon as a query matches at least the `hitsPerPage` number of results.
- */
-type SearchStrategy = 'none' | 'stopIfEnoughMatches';
-
-type SearchMethodParams = {
-    requests: SearchQuery[];
-    strategy?: SearchStrategy;
-};
-
 /**
  * Search result.  A hit is a record from your index, augmented with special attributes for highlighting, snippeting, and ranking.
  */
@@ -1411,11 +1421,15 @@ type Hit<T = Record<string, any>> = T & {
     /**
      * Surround words that match the query with HTML tags for highlighting.
      */
-    _highlightResult?: Record<string, HighlightResult>;
+    _highlightResult?: {
+        [key: string]: HighlightResult;
+    };
     /**
      * Snippets that show the context around a matching search query.
      */
-    _snippetResult?: Record<string, SnippetResult>;
+    _snippetResult?: {
+        [key: string]: SnippetResult;
+    };
     _rankingInfo?: RankingInfo;
     _distinctSeqID?: number;
 };
@@ -1424,7 +1438,7 @@ type SearchHits<T = Record<string, any>> = Record<string, any> & {
     /**
      * Search results (hits).  Hits are records from your index that match the search criteria, augmented with additional attributes, such as, for highlighting.
      */
-    hits: Array<Hit<T>>;
+    hits: Hit<T>[];
     /**
      * Search query.
      */
@@ -1435,15 +1449,68 @@ type SearchHits<T = Record<string, any>> = Record<string, any> & {
     params: string;
 };
 
-type SearchResponse<T = Record<string, any>> = BaseSearchResponse & SearchHits<T> & SearchPagination;
+type SearchResponse<T = Record<string, any>> = BaseSearchResponse & SearchPagination & SearchHits<T>;
 
-type SearchResult<T = Record<string, any>> = SearchForFacetValuesResponse | SearchResponse<T>;
+type SearchResult<T = Record<string, any>> = SearchResponse<T> | SearchForFacetValuesResponse;
 
 type SearchResponses<T = Record<string, any>> = {
-    results: Array<SearchResult<T>>;
+    results: SearchResult<T>[];
+};
+
+/**
+ * Properties for the `customPost` method.
+ */
+type CustomPostProps = {
+    /**
+     * Path of the endpoint, anything after \"/1\" must be specified.
+     */
+    path: string;
+    /**
+     * Query parameters to apply to the current query.
+     */
+    parameters?: {
+        [key: string]: any;
+    };
+    /**
+     * Parameters to send with the custom request.
+     */
+    body?: Record<string, unknown>;
+};
+/**
+ * Recommend method signature compatible with the `algoliasearch` v4 package. When using this signature, extra computation will be required to make it match the new signature.
+ *
+ * @deprecated This signature will be removed from the next major version, we recommend using the `GetRecommendationsParams` type for performances and future proof reasons.
+ */
+type LegacyGetRecommendationsParams = RecommendationsRequest[];
+/**
+ * In v4, the search parameters are wrapped in a `params` parameter.
+ *
+ * @deprecated The `search` method now accepts flat `searchParams` at the root of the method.
+ */
+type LegacySearchParams = {
+    params?: SearchParamsObject;
 };
+/**
+ * In v4, the search parameters are wrapped in a `params` parameter.
+ *
+ * @deprecated The `search` method now accepts flat `searchParams` at the root of the method.
+ */
+type LegacySearchForFacets = LegacySearchParams & SearchForFacetsOptions;
+/**
+ * In v4, the search parameters are wrapped in a `params` parameter.
+ *
+ * @deprecated The `search` method now accepts flat `searchParams` at the root of the method.
+ */
+type LegacySearchForHits = LegacySearchParams & SearchForHitsOptions;
+type LegacySearchQuery = LegacySearchForFacets | LegacySearchForHits;
+/**
+ * Search method signature compatible with the `algoliasearch` v4 package. When using this signature, extra computation will be required to make it match the new signature.
+ *
+ * @deprecated This signature will be removed from the next major version, we recommend using the `SearchMethodParams` type for performances and future proof reasons.
+ */
+type LegacySearchMethodProps = LegacySearchQuery[];
 
-declare const apiClientVersion = "5.6.1";
+declare const apiClientVersion = "5.8.0";
 declare function createLiteClient({ appId: appIdOption, apiKey: apiKeyOption, authMode, algoliaAgents, ...options }: CreateClientOptions): {
     transporter: _algolia_client_common.Transporter;
     /**
@@ -1494,11 +1561,10 @@ declare function createLiteClient({ appId: appIdOption, apiKey: apiKeyOption, au
      * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions.
      */
     searchForFacets(searchMethodParams: LegacySearchMethodProps | SearchMethodParams, requestOptions?: RequestOptions): Promise<{
-        results: SearchForFacetValuesResponse[];
+        results: Array<SearchForFacetValuesResponse>;
     }>;
     /**
      * This method allow you to send requests to the Algolia REST API.
-     *
      * @param customPost - The customPost object.
      * @param customPost.path - Path of the endpoint, anything after \"/1\" must be specified.
      * @param customPost.parameters - Query parameters to apply to the current query.
@@ -1510,28 +1576,26 @@ declare function createLiteClient({ appId: appIdOption, apiKey: apiKeyOption, au
      * Retrieves recommendations from selected AI models.
      *
      * Required API Key ACLs:
-     * - search.
-     *
+     *  - search
      * @param getRecommendationsParams - The getRecommendationsParams object.
      * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions.
      */
     getRecommendations(getRecommendationsParams: GetRecommendationsParams | LegacyGetRecommendationsParams, requestOptions?: RequestOptions): Promise<GetRecommendationsResponse>;
     /**
-     * Sends multiple search request to one or more indices.  This can be useful in these cases:  - Different indices for different purposes, such as, one index for products, another one for marketing content. - Multiple searches to the same index—for example, with different filters.
+     * Sends multiple search requests to one or more indices.  This can be useful in these cases:  - Different indices for different purposes, such as, one index for products, another one for marketing content. - Multiple searches to the same index—for example, with different filters.
      *
      * Required API Key ACLs:
-     * - search.
-     *
+     *  - search
      * @param searchMethodParams - Muli-search request body. Results are returned in the same order as the requests.
      * @param requestOptions - The requestOptions to send along with the query, they will be merged with the transporter requestOptions.
      */
-    search<T>(searchMethodParams: LegacySearchMethodProps | SearchMethodParams, requestOptions?: RequestOptions): Promise<SearchResponses<T>>;
+    search<T>(searchMethodParams: SearchMethodParams | LegacySearchMethodProps, requestOptions?: RequestOptions): Promise<SearchResponses<T>>;
 };
 
 /**
  * Access control list permissions.
  */
-type Acl = 'addObject' | 'analytics' | 'browse' | 'deleteIndex' | 'deleteObject' | 'editSettings' | 'inference' | 'listIndexes' | 'logs' | 'personalization' | 'recommendation' | 'search' | 'seeUnretrievableAttributes' | 'settings' | 'usage';
+type Acl = 'addObject' | 'analytics' | 'browse' | 'deleteObject' | 'deleteIndex' | 'editSettings' | 'inference' | 'listIndexes' | 'logs' | 'personalization' | 'recommendation' | 'search' | 'seeUnretrievableAttributes' | 'settings' | 'usage';
 
 /**
  * API key object.
@@ -1540,7 +1604,7 @@ type ApiKey = {
     /**
      * Permissions that determine the type of API requests this key can make. The required ACL is listed in each endpoint\'s reference. For more information, see [access control list](https://www.algolia.com/doc/guides/security/api-keys/#access-control-list-acl).
      */
-    acl: Acl[];
+    acl: Array<Acl>;
     /**
      * Description of an API key to help you identify this API key.
      */
@@ -1548,7 +1612,7 @@ type ApiKey = {
     /**
      * Index names or patterns that this API key can access. By default, an API key can access all indices in the same application.  You can use leading and trailing wildcard characters (`*`):  - `dev_*` matches all indices starting with \"dev_\". - `*_dev` matches all indices ending with \"_dev\". - `*_products_*` matches all indices containing \"_products_\".
      */
-    indexes?: string[];
+    indexes?: Array<string>;
     /**
      * Maximum number of results this API key can retrieve in one query. By default, there\'s no limit.
      */
@@ -1558,13 +1622,13 @@ type ApiKey = {
      */
     maxQueriesPerIPPerHour?: number;
     /**
-     * Query parameters to add when making API requests with this API key.  To restrict this API key to specific IP addresses, add the `restrictSources` parameter. You can only add a single source, but you can provide a range of IP addresses.  Creating an API key fails if the request is made from an IP address that\'s outside the restricted range.
+     * Query parameters to add when making API requests with this API key.  To restrict this API key to specific IP addresses, add the `restrictSources` parameter. You can only add a single source, but you can provide a range of IP addresses.  Creating an API key fails if the request is made from an IP address outside the restricted range.
      */
     queryParameters?: string;
     /**
      * Allowed HTTP referrers for this API key.  By default, all referrers are allowed. You can use leading and trailing wildcard characters (`*`):  - `https://algolia.com/_*` allows all referrers starting with \"https://algolia.com/\" - `*.algolia.com` allows all referrers ending with \".algolia.com\" - `*algolia.com*` allows all referrers in the domain \"algolia.com\".  Like all HTTP headers, referrers can be spoofed. Don\'t rely on them to secure your data. For more information, see [HTTP referrer restrictions](https://www.algolia.com/doc/guides/security/security-best-practices/#http-referrers-restrictions).
      */
-    referers?: string[];
+    referers?: Array<string>;
     /**
      * Duration (in seconds) after which the API key expires. By default, API keys don\'t expire.
      */
@@ -1592,7 +1656,7 @@ type AutomaticFacetFilter = {
 /**
  * Filter to be applied to the search.  You can use this to respond to search queries that match a facet value. For example, if users search for \"comedy\", which matches a facet value of the \"genre\" facet, you can filter the results to show the top-ranked comedy movies.
  */
-type AutomaticFacetFilters = AutomaticFacetFilter[] | string[];
+type AutomaticFacetFilters = Array<AutomaticFacetFilter> | Array<string>;
 
 type BaseGetApiKeyResponse = {
     /**
@@ -1631,9 +1695,9 @@ type Cursor = {
     cursor?: string;
 };
 
-type BrowseParamsObject = Cursor & SearchParamsObject;
+type BrowseParamsObject = SearchParamsObject & Cursor;
 
-type BrowseResponse<T = Record<string, any>> = BaseSearchResponse & BrowsePagination & Cursor & SearchHits<T>;
+type BrowseResponse<T = Record<string, any>> = BaseSearchResponse & BrowsePagination & SearchHits<T> & Cursor;
 
 /**
  * Type of edit.
@@ -1656,11 +1720,11 @@ type ConsequenceQueryObject = {
     /**
      * Words to remove from the search query.
      */
-    remove?: string[];
+    remove?: Array<string>;
     /**
      * Changes to make to the search query.
      */
-    edits?: Edit[];
+    edits?: Array<Edit>;
 };
 
 /**
@@ -1687,7 +1751,7 @@ type ErrorBase = Record<string, any> & {
     message?: string;
 };
 
-type GetApiKeyResponse = ApiKey & BaseGetApiKeyResponse;
+type GetApiKeyResponse = BaseGetApiKeyResponse & ApiKey;
 
 /**
  * Index settings.
@@ -1703,8 +1767,7 @@ type WithPrimary = {
 
 type SettingsResponse = IndexSettings & WithPrimary;
 
-type LiteClient = ReturnType<typeof createLiteClient>;
-
 declare function liteClient(appId: string, apiKey: string, options?: ClientOptions): LiteClient;
+type LiteClient = ReturnType<typeof createLiteClient>;
 
-export { type Acl, type AdvancedSyntaxFeatures, type AlternativesAsExact, type ApiKey, type AroundPrecision, type AroundRadius, type AroundRadiusAll, type AutomaticFacetFilter, type AutomaticFacetFilters, type BaseGetApiKeyResponse, type BaseIndexSettings, type BaseRecommendIndexSettings, type BaseRecommendRequest, type BaseRecommendSearchParams, type BaseSearchParams, type BaseSearchParamsWithoutQuery, type BaseSearchResponse, type BooleanString, type BoughtTogetherQuery, type BrowsePagination, type BrowseParamsObject, type BrowseResponse, type ConsequenceParams, type ConsequenceQuery, type ConsequenceQueryObject, type Cursor, type CustomPostProps, type Distinct, type Edit, type EditType, type ErrorBase, type ExactOnSingleWordQuery, type Exhaustive, type FacetFilters, type FacetHits, type FacetOrdering, type FacetStats, type FallbackParams, type FbtModel, type FrequentlyBoughtTogether, type GetApiKeyResponse, type GetRecommendationsParams, type GetRecommendationsResponse, type HighlightResult, type HighlightResultOption, type Hit, type IgnorePlurals, type IndexSettings, type IndexSettingsAsSearchParams, type IndexSettingsFacets, type LegacyGetRecommendationsParams, type LegacySearchMethodProps, type LiteClient, type LookingSimilar, type LookingSimilarModel, type LookingSimilarQuery, type MatchLevel, type MatchedGeoLocation, type Mode, type NumericFilters, type OptionalFilters, type Params, type Personalization, type QueryType, type Range, type RankingInfo, type ReRankingApplyFilter, type RecommendHit, type RecommendIndexSettings, type RecommendSearchParams, type RecommendationsHit, type RecommendationsHits, type RecommendationsRequest, type RecommendationsResults, type RecommendedForYou, type RecommendedForYouModel, type RecommendedForYouQuery, type Redirect, type RedirectRuleIndexData, type RedirectRuleIndexMetadata, type RedirectURL, type RelatedModel, type RelatedProducts, type RelatedQuery, type RemoveStopWords, type RemoveWordsIfNoResults, type RenderingContent, type SearchForFacetValuesResponse, type SearchForFacets, type SearchForFacetsOptions, type SearchForHits, type SearchForHitsOptions, type SearchHits, type SearchMethodParams, type SearchPagination, type SearchParams, type SearchParamsObject, type SearchParamsQuery, type SearchParamsString, type SearchQuery, type SearchResponse, type SearchResponses, type SearchResult, type SearchStrategy, type SearchTypeDefault, type SearchTypeFacet, type SemanticSearch, type SettingsResponse, type SnippetResult, type SnippetResultOption, type SortRemainingBy, type SupportedLanguage, type TagFilters, type TrendingFacetHit, type TrendingFacets, type TrendingFacetsModel, type TrendingFacetsQuery, type TrendingItems, type TrendingItemsModel, type TrendingItemsQuery, type TypoTolerance, type TypoToleranceEnum, type Value, type WithPrimary, apiClientVersion, liteClient };
+export { type Acl, type AdvancedSyntaxFeatures, type AlternativesAsExact, type ApiKey, type AroundPrecision, type AroundRadius, type AroundRadiusAll, type AutomaticFacetFilter, type AutomaticFacetFilters, type Banner, type BannerImage, type BannerImageUrl, type BannerLink, type Banners, type BaseGetApiKeyResponse, type BaseIndexSettings, type BaseRecommendIndexSettings, type BaseRecommendRequest, type BaseRecommendSearchParams, type BaseSearchParams, type BaseSearchParamsWithoutQuery, type BaseSearchResponse, type BooleanString, type BoughtTogetherQuery, type BrowsePagination, type BrowseParamsObject, type BrowseResponse, type ConsequenceParams, type ConsequenceQuery, type ConsequenceQueryObject, type Cursor, type CustomPostProps, type Distinct, type Edit, type EditType, type ErrorBase, type ExactOnSingleWordQuery, type Exhaustive, type FacetFilters, type FacetHits, type FacetOrdering, type FacetStats, type FallbackParams, type FbtModel, type FrequentlyBoughtTogether, type GetApiKeyResponse, type GetRecommendationsParams, type GetRecommendationsResponse, type HighlightResult, type HighlightResultOption, type Hit, type IgnorePlurals, type IndexSettings, type IndexSettingsAsSearchParams, type IndexSettingsFacets, type LegacyGetRecommendationsParams, type LegacySearchMethodProps, type LiteClient, type LookingSimilar, type LookingSimilarModel, type LookingSimilarQuery, type MatchLevel, type MatchedGeoLocation, type Mode, type NumericFilters, type OptionalFilters, type Params, type Personalization, type QueryType, type Range, type RankingInfo, type ReRankingApplyFilter, type RecommendHit, type RecommendIndexSettings, type RecommendSearchParams, type RecommendationsHit, type RecommendationsHits, type RecommendationsRequest, type RecommendationsResults, type RecommendedForYou, type RecommendedForYouModel, type RecommendedForYouQuery, type Redirect, type RedirectRuleIndexData, type RedirectRuleIndexMetadata, type RedirectURL, type RelatedModel, type RelatedProducts, type RelatedQuery, type RemoveStopWords, type RemoveWordsIfNoResults, type RenderingContent, type SearchForFacetValuesResponse, type SearchForFacets, type SearchForFacetsOptions, type SearchForHits, type SearchForHitsOptions, type SearchHits, type SearchMethodParams, type SearchPagination, type SearchParams, type SearchParamsObject, type SearchParamsQuery, type SearchParamsString, type SearchQuery, type SearchResponse, type SearchResponses, type SearchResult, type SearchStrategy, type SearchTypeDefault, type SearchTypeFacet, type SemanticSearch, type SettingsResponse, type SnippetResult, type SnippetResultOption, type SortRemainingBy, type SupportedLanguage, type TagFilters, type TrendingFacetHit, type TrendingFacets, type TrendingFacetsModel, type TrendingFacetsQuery, type TrendingItems, type TrendingItemsModel, type TrendingItemsQuery, type TypoTolerance, type TypoToleranceEnum, type Value, type Widgets, type WithPrimary, apiClientVersion, liteClient };