Create nested attributes

Learn about nested attributes, and when to use them.

With nested attributes, you can add subcategories to your attributes. For example, instead of having a single attribute price, you can set up different prices as subcategories: price.net, price.gross, price.margin. To refer to nested attributes, separate parent and child attribute with a ..

To create nested attributes, add them as nested JSON objects to your records. For example:

JSON

[
  {
    "country": "CA",
    // price is a nested attribute
    "price": {
      "net": 2.30,
      "gross": 2.62
    }
  },
  {
    "country": "US",
    // price is a nested attribute
    "price": {
      "net": 1.99,
      "gross": 1.75
    }
  }
]

Example: filtering nested attributes

If you want to filter a search using nested attributes, use the filters parameter in your search request and separate the parent and child attribute by a .. For example, with the JavaScript API client:

C#

var response = await client.SearchSingleIndexAsync<Hit>(
  "ALGOLIA_INDEX_NAME",
  new SearchParams(new SearchParamsObject { Filters = "country:US AND price.gross < 2.0" })
);

Where you can use nested attributes

You can use nested attributes wherever you might use a regular attribute, such as searchableAttributes and attributesForFaceting. Just make sure you use the appropriate dot notation such as price.country to refer to them.

There’s no limit on the number of nested attributes apart from the default restrictions on record size. The maximum nesting depth is 256 levels, which is more than enough for most use cases. For example, you could use something like price.net.us.ca.