Usage
Examples
Display records statistics for the “MOVIES” index for the first 1000 records:Advanced
Whether the best matching attribute should be determined by minimum proximity.
See:
attributeCriteriaComputedByMinProximityWhether to enable A/B testing for this search.
See:
enableABTestWhether the search response should include detailed ranking information.
See:
getRankingInfoMinimum proximity score for two matching words.
See:
minProximityWhether to include this search when calculating processing-time percentiles.
See:
percentileComputationExtra data that can be used in the search UI.
See:
renderingContentProperties to include in the API response of search and browse requests.
See:
responseFieldsAnalytics
Tags to apply to the query for segmenting analytics data.
See:
analyticsTagsWhether to include a queryID attribute in the response.
See:
clickAnalyticsAttributes
Attributes to include in the API response.
See:
attributesToRetrieveFaceting
Whether faceting should be applied after deduplication with distinct.
See:
facetingAfterDistinctFacets for which to retrieve facet values that match the search criteria and the number of matching facet values.
See:
facetsMaximum number of facet values to return for each facet.
See:
maxValuesPerFacetOrder in which to retrieve facet values.
See:
sortFacetValuesByFiltering
Whether this search will use Dynamic Re-Ranking.
See:
enableReRankingFilter the search by facet values, so that only records with the same facet values are retrieved.
See:
facetFiltersFilter expression to only include items that match the filter criteria in the response.
See:
filtersFilter by numeric facets.
See:
numericFiltersFilters to promote or demote records in the search results.
See:
optionalFiltersRestricts a search to a subset of your searchable attributes.
See:
restrictSearchableAttributesWhether to sum all filter scores.
See:
sumOrFiltersScoresFilter the search by values of the special _tags attribute.
See:
tagFiltersGeo-Search
Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude.
See:
aroundLatLngWhether to obtain the coordinates from the request’s IP address.
See:
aroundLatLngViaIPPrecision of a coordinate-based search in meters to group results with similar distances.
See:
aroundPrecisionMaximum radius for a search around a central location.
See:
aroundRadiusMinimum radius (in meters) for a search around a location when aroundRadius isn’t set.
See:
minimumAroundRadiusHighlighting and Snippeting
Attributes to highlight.
See:
attributesToHighlightAttributes for which to enable snippets.
See:
attributesToSnippetHTML tag to insert after the highlighted parts in all highlighted results and snippets.
See:
highlightPostTagHTML tag to insert before the highlighted parts in all highlighted results and snippets.
See:
highlightPreTagWhether to replace a highlighted word with the matched synonym.
See:
replaceSynonymsInHighlightWhether to restrict highlighting and snippeting to items that at least partially matched the search query.
See:
restrictHighlightAndSnippetArraysString used as an ellipsis indicator when a snippet is truncated.
See:
snippetEllipsisTextLanguages
Whether to split compound words in the query into their building blocks.
See:
decompoundQueryTreat singular, plurals, and other forms of declensions as equivalent.
See:
ignorePluralsISO language codes that adjust settings that are useful for processing natural language queries (as opposed to keyword searches).
See:
naturalLanguagesLanguages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries.
See:
queryLanguagesRemoves stop words from the search query.
See:
removeStopWordsOther flags
Cursor to get the next page of the response.
Coordinates for a rectangular area in which to search.
See:
insideBoundingBoxIf set, the command will not limit the number of objects to analyze. Otherwise, the default limit is 1000 objects.
If set, the command will only analyze the specified attribute. Chosen attribute values statistics will be shown in the output.
Words that should be considered optional when found in the query.
See:
optionalWordsRestrict Dynamic Re-Ranking to records that match these filters.
Settings for the semantic search part of NeuralSearch.
Output formatting flags
If true, ignore errors in templates due to missing fields or map keys. This only applies to golang and jsonpath output formats.
Output format. One of: (json, jsonl, ndjson, jsonpath, jsonpath-as-json, jsonpath-file).
Template string or path to a template file to use when —output=jsonpath, —output=jsonpath-file.
Pagination
Number of hits per page.
See:
hitsPerPagePersonalization
Whether to enable Personalization.
See:
enablePersonalizationImpact that Personalization should have on this search.
See:
personalizationImpactQuery strategy
Whether to support phrase matching and excluding words from search queries.
See:
advancedSyntaxAdvanced search syntax features you want to support.
See:
advancedSyntaxFeaturesDetermine which plurals and synonyms should be considered an exact matches.
See:
alternativesAsExactSearchable attributes for which you want to turn off the Exact ranking criterion.
See:
disableExactOnAttributesDetermines how the Exact ranking criterion is computed when the search query has only one word. One of: attribute, none, word.
See:
exactOnSingleWordQuerySearch mode the index will use to query for results. One of: neuralSearch, keywordSearch.
See:
modeDetermines if and how query words are interpreted as prefixes. One of: prefixLast, prefixAll, prefixNone.
See:
queryTypeStrategy for removing words from the query when it doesn’t return any results. One of: none, lastWords, firstWords, allOptional.
See:
removeWordsIfNoResultsRanking
Relevancy threshold below which less relevant results aren’t included in the results.
See:
relevancyStrictnessRules
Whether to enable rules.
See:
enableRulesAssigns a rule context to the search query.
See:
ruleContextsSearch
Keywords to be used instead of the search query to conduct a more broader search.
See:
similarQueryTypos
Whether to allow typos on numbers in the search query.
See:
allowTyposOnNumericTokensAttributes for which you want to turn off typo tolerance.
See:
disableTypoToleranceOnAttributesMinimum number of characters a word in the search query must contain to accept matches with one typo.
See:
minWordSizefor1TypoMinimum number of characters a word in the search query must contain to accept matches with two typos.
See:
minWordSizefor2TyposWhether typo tolerance is enabled and how it is applied.
See:
typoTolerance