# Filter Attribute Sets Filters the tenant's Attribute Set resources using OData query options ($select, $expand, $filter, $orderby, $skip, $top, $skipToken). Result's paging is done using the default paging size options. Parameters details X-API-KEY Custom HTTP request header containing the API key used for authentication. Accept-Language Standard HTTP request header indicates the natural language and locale that the client prefers. It can take one of the following values: * : All the localized content is available in the result, regardless of the culture . This option is currently disabled. null : The content localized in the default culture is available in the result. culture-code : The content localized in the specified culture is available in the result. Specifying various culture codes or q-factor weighting are currently disabled. Examples: - Expression es returns the content localized in the culture es. - Expression en-us returns the content localized in the culture en-us. $select Expression describing the list of Attribute Set resource properties to be included in the result. The full list of the available Attribute Set resource properties is available in the JSON schema returned by the /AttributeSets/$metadata endpoint. The name of the Attribute Set resource properties (both implicit and custom properties) must be specified. Currently, the API does not support selecting the properties of an embedded resource or the properties of a resource within an embedded collection. The expression follows the format: ATTRIBUTE_SET_PROPERTY1_NAME{, ATTRIBUTE_SET_PROPERTY2_NAME...}. Examples: - Expression typ_title includes in the result only the property typ_title of the current resource (Attribute Set). - Expression typ_stat,typ_title includes in the result only the properties typ_stat and typ_title of the current resource (Attribute Set). $expand Expression describing the list of collections embedded in the Attribute Set resource (Products) to be included in the result. By default (if no value is supplied to this parameter), the result doesn't include the embedded collections (Products). The expression follows the format: EMBEDDED_COLLECTION_OF_RESOURCE1_NAME{,EMBEDDED_COLLECTION_OF_RESOURCE1_NAME...}. Currently only the embedded collections are supported, not the embedded resources. Examples: - Expression Products includes in the result the number elements of the Products resource, embedded in the current resource (Attribute Set). $filter Expression describing the filters applied to the resources included in the result. By default (if no value is supplied to this parameter), no filters are applied Currently, filtering on the nested resources properties is not supported. The expression follows the ODATA version 4.01 URI conventions (http://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part2-url-conventions.html). The following filter options are currently supported: - logical operators (eq, ne, gt, lt, ge, le, or, and, in) - functions: string functions (contains, startswith, endswith) Currently it supports only the operators and functions applied on the properties of the root resource (Category). The logical operators/functions are applied over the data types of the corresponding properties in the filter criteria: - integer : property_of_type_integer lt -100 - big integer: property_of_type_big_integer gt 10000 - double: property_of_type_double ge 0.31415926535897931e1 - decimal: property_of_type_decimal eq 12.34 - string: property_of_type_string eq 'Hello world!' - date: property_of_type_date eq 2023-12-01 - date time offset: property_of_type_datetimeoffset lt 2012-12-03T07:16:23Z or property_of_type_datetimeoffset lt 2012-12-03T07:16:23+00:00 or property_of_type_datetimeoffset lt 2012-12-03 Further examples: - contains(property1, 'stringValue1') - endswith(property1, 'stringValue1') - startswith(property1, 'stringValue1') - property1 in (value1, value2) - property1 gt integerValue1 and property2 eq 'stringValue1' - property1 gt integerValue1 or property2 eq 'stringValue1' - (property1 eq 'stringValue1' or property1 eq 'stringValue2') and (contains(property2, 'stringValue3') or startsWith(property3, 'stringValue4') or startsWith(property4, 'stringValue5')) $orderby Expression describing the ordering applied to the properties of resources included in the result. By default (if no value is supplied to this parameter), no sorting is applied. Currently, ordering on multiple properties and ordering on embedded resources properties are not supported. The expression follows the format: RESOURCE_PROPERTY_NAME (asc)|desc. Examples: - Expression typ_title orders the result ascendingly on the property typ_title of the current resource (Attribute Set). - Expression typ_title asc orders the result ascendingly on the property typ_title of the current resource (Attribute Set). - Expression typ_stat desc orders the result descendingly on the property typ_stat of the current resource (Attribute Set). $skip Expression setting up result's paging according to the limit and offset paging strategy. Using this paging strategy involves using both $skip and $top parameters. We recommend limit and offset paging strategy for the extraction of data where $orderby clauses needs to be applied to the data to be extracted. limit and offset paging is not as fast as the continuation token paging, but has 2 advantages over the later: - the possibility of applying sorting on the result; - a fine control over the data extracted. The expression follows the format: NUMBER_OF_ITEMS_TO_BE_SKIPPED_IN_THE_RESULT. The page size for the Attribute Set resource is limited by default to 100 items. The paging is performed through resource (Attribute Set), not through the resources in the embedded collections. Examples: - Expression 1000 returns the Attribute Set items starting from the 1001st element in the result. $skipToken Expression setting up the continuation token used in paging the result. The expression follows the format: [CONTINUATION_TOKEN]. The page size for the Attribute Set resource is limited to 1 item. The paging is performed through resource (Attribute Set), not through the resources in the embedded collections. Examples: - Expression 123456789 limits the Attribute Set items to the next default number of items, starting from the continuation token 123456789. $top Expression setting up the number of items in the result. The expression follows the format: [PAGE_SIZE]. The page size for the Attribute Set resource is limited to 1 item. The paging is performed through resource (Attribute Set), not through the resources in the embedded collections. Examples: - Expression 10 limits the Attribute Set items to the first 10 elements, given the other filter, sorting and paging criteria. See also: A newer version of this endpoint is available at GET /v2/AttributeSets. The v2 endpoint returns a structured response (GetAttributeSetsResponse) that includes form layout configuration (ProductLayout, VariantLayout) and is not interchangeable with the OData-style response returned by this endpoint. Endpoint: GET /AttributeSets Version: 2.0.0 ## Query parameters: - `$filter` (string) - `$orderby` (string) - `$skip` (integer) - `$skipToken` (string) - `$top` (integer) - `$select` (string) - `$expand` (string) ## Header parameters: - `X-API-KEY` (string) Tenant's API key - `Accept-Language` (string) The localization cultures ## Response 200 fields (application/json): - `@readLink` (string) - `@nextLink` (string) - `@deltaLink` (string) - `@context` (string) - `value` (any) - `@count` (integer) ## Response 401 fields (application/json): - `message` (string) - `request_id` (string) ## Response 403 fields (application/json): - `type` (string) - `title` (string) - `status` (integer) - `detail` (string) - `instance` (string) ## Response 404 fields (application/json): - `type` (string) - `title` (string) - `status` (integer) - `detail` (string) - `instance` (string) ## Response 500 fields (application/json): - `error` (string) - `details` (any)