{"section":"known-issues","requestedLocale":"en","requestedSlug":"price-range-at-the-facets-api-doesnt-correspond-to-the-search-results","locale":"en","slug":"price-range-at-the-facets-api-doesnt-correspond-to-the-search-results","path":"docs/en/known-issues/Intelligent Search/price-range-at-the-facets-api-doesnt-correspond-to-the-search-results.md","branch":"main","content":"## Summary\n\n\nThe price ranges from the facets API (\"Get list of the possible facets for a given query\") may vary between returning buckets of \"from\" and \"to\" values with rounded prices and the minimum and maximum prices between the search results.\n\nWhile the rounded prices generate a better UX to present a list of price ranges to the shopper, it's not desired to use as a price \"slider\".\n\nMoreover, since the minimum and maximum prices are applied at a second moment, the price ranges as \"buckets\" in a search that already applies a price filter get out of bounds of bounds in relation to the specified prices.\n\n\n##\n\n## Simulation\n\n\nUsing the  API, make a request with and without a price filter like \"/price/100:500\" and observe the returned price ranges (from/to) in the \"values\" object for the facet with type \"PRICERANGE\".\n\n\n##\n\n## Workaround\n\n\nN/A"}