---
title: "List filters"
method: GET
path: "/v1/filters"
tags: ["filters"]
---

# List filters

`GET /v1/filters`

Filters endpoint should be used to display a reduced list of products based on specific criteria. Often, it is the same criteria, as it was sent to show products.
Multiple filter criteria can and should be combined in the single request.

As an example, the following request: `/v1/filters?filters[category]=235870&filters[sale]=true&with=values`
will restrict the response to include only the available filter values for a specific *category* for products on *sale*.
When adding the `with=values` parameter, the response will include values and their product counts for the combination of the filters used.

In the next section, all the available filters will be described in detail.

__Note__: Inactive products (sold out) are always automatically filtered out from the filter's response, and they are not taken into account for any of the described filters below.

## Query parameters

- `filters[category]` integer[]
- `filters[ean]` string[]
- `filters[term]` string
- `disableFuzziness` boolean
- `filters[isNew]` boolean
- `filters[maxPrice]` integer
- `filters[minPrice]` integer
- `filters[sale]` boolean
- `filters[attributeKey]` string[]
- `filters:not[attributeKey]` integer[]
- `orFiltersOperator` string[]
- `filters[masterKey]` string[]
- `filters[referenceKey]` string
- `filters[variants.referenceKey]` string[]
- `filters[merchantId]` integer
- `filters[hasCampaignReduction]` boolean
- `campaignKey` string
- `includeSoldOut` boolean
- `with` string[]

## Response `200`

successful operation

- Filter[]
  - `id` integer, nullable, required
  - `name` string, required
  - `slug` string, required — short text to describe the current category (usable, for example, in URLs as `fashion`).
  - `attributeGroupType` string, required
  - `type` string, required
  - `values` union
    - AttributeFilterValue[]
      - `name` string, required
      - `productCount` integer, required
      - `id` integer, required
      - `value` string, required
    - BooleanFilterValue[]
      - `name` boolean, required
      - `productCount` integer, required
    - RangeFilterValue[]
      - `max` integer
      - `min` integer
      - `productCount` integer, required

## Changes

- **2026-07-17** `8cfa924ae703` — 4 breaking, 4 warning, 10 info
  - for the `query` request parameter `filters:not[attributeKey]`, the type/format was changed from `string`/`` to `array`/``
  - for the `query` request parameter `filters[attributeKey]`, the type/format was changed from `string`/`` to `array`/``
  - for the `query` request parameter `orFiltersOperator`, the type/format was changed from `string`/`` to `array`/``
  - added `subschema #1, subschema #2, subschema #3` to the `items/values` response property `oneOf` list for the response status `200`
  - …14 more
- **2023-08-06** `302b7c443b51` — 7 breaking, 3 warning, 8 info
  - for the `query` request parameter `filters[term]`, the type/format was changed from `string`/`` to `array`/``
  - the response property `items/attributeGroupType` became optional for the status `200`
  - the response property `items/id` became optional for the status `200`
  - the response property `items/name` became optional for the status `200`
  - …14 more

[Change history](https://skmtc.dev/scayle/apis/storefront-api-documentation/changes/v1/filters/get.md)

---

[API](https://skmtc.dev/scayle/apis/storefront-api-documentation.md) · [All operations](https://skmtc.dev/scayle/apis/storefront-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/scayle/storefront-api-documentation/revisions/8cfa924ae703/schema)