@algolia/n8n-nodes-algolia 0.6.0 → 0.7.0

package/dist/nodes/Algolia/specs/composition.json

@@ -2,7 +2,7 @@
   "openapi": "3.0.2",
   "info": {
     "title": "Composition API",
-    "description": "The Algolia Composition API lets you run composed search requests on your Compositions.\n\n## Client libraries\n\nUse Algolia's API clients and libraries to reliably integrate Algolia's APIs with your apps.\n\nSee: [Algolia's ecosystem](https://www.algolia.com/doc/guides/getting-started/how-algolia-works/in-depth/ecosystem/)\n\n## Base URLs\n\nThe base URLs for requests to the Composition API are:\n\n- `https://{APPLICATION_ID}.algolia.net`\n- `https://{APPLICATION_ID}-dsn.algolia.net`.\n  If your subscription includes a [Distributed Search Network](https://dashboard.algolia.com/infra),\n  this ensures that requests are sent to servers closest to users.\n\nBoth URLs provide high availability by distributing requests with load balancing.\n\n**All requests must use HTTPS.**\n\n## Retry strategy\n\nTo guarantee high availability, implement a retry strategy for all API requests using the URLs of your servers as fallbacks:\n\n- `https://{APPLICATION_ID}-1.algolianet.com`\n- `https://{APPLICATION_ID}-2.algolianet.com`\n- `https://{APPLICATION_ID}-3.algolianet.com`\n\nThese URLs use a different DNS provider than the primary URLs.\nYou should randomize this list to ensure an even load across the three servers.\n\nAll Algolia API clients implement this retry strategy.\n\n## Authentication\n\nTo authenticate your API requests, add these headers:\n\n- `x-algolia-application-id`. Your Algolia application ID.\n- `x-algolia-api-key`. An API key with the necessary permissions to make the request.\n  The required access control list (ACL) to make a request is listed in each endpoint's reference.\n\nYou can find your application ID and API key in the [Algolia dashboard](https://dashboard.algolia.com/account).\n\n## Request format\n\nDepending on the endpoint, request bodies are either JSON objects or arrays of JSON objects,\n\n## Parameters\n\nParameters are passed in the request body for POST and PUT requests.\nQuery parameters must be [URL-encoded](https://developer.mozilla.org/en-US/docs/Glossary/Percent-encoding).\nNon-ASCII characters must be UTF-8 encoded.\nPlus characters (`+`) are interpreted as spaces.\n\n## Response status and errors\n\nThe Composition API returns JSON responses.\nSince JSON doesn't guarantee any specific ordering, don't rely on the order of attributes in the API response.\n\nSuccessful responses return a `2xx` status. Client errors return a `4xx` status. Server errors are indicated by a `5xx` status.\nError responses have a `message` property with more information.\n\n## Version\n\nThe current version of the Composition API is version 1, as indicated by the `/1/` in each endpoint's URL.\n",
+    "description": "The Algolia Composition API lets you run composed search requests on your Compositions.\n\n## Client libraries\n\nUse Algolia's API clients and libraries to reliably integrate Algolia's APIs with your apps.\n\nSee: [Algolia's ecosystem](https://www.algolia.com/doc/guides/getting-started/how-algolia-works/in-depth/ecosystem)\n\n## Base URLs\n\nThe base URLs for requests to the Composition API are:\n\n- `https://{APPLICATION_ID}.algolia.net`\n- `https://{APPLICATION_ID}-dsn.algolia.net`.\n  If your subscription includes a [Distributed Search Network](https://dashboard.algolia.com/infra),\n  this ensures that requests are sent to servers closest to users.\n\nBoth URLs provide high availability by distributing requests with load balancing.\n\n**All requests must use HTTPS.**\n\n## Retry strategy\n\nTo guarantee high availability, implement a retry strategy for all API requests using the URLs of your servers as fallbacks:\n\n- `https://{APPLICATION_ID}-1.algolianet.com`\n- `https://{APPLICATION_ID}-2.algolianet.com`\n- `https://{APPLICATION_ID}-3.algolianet.com`\n\nThese URLs use a different DNS provider than the primary URLs.\nYou should randomize this list to ensure an even load across the three servers.\n\nAll Algolia API clients implement this retry strategy.\n\n## Authentication\n\nTo authenticate your API requests, add these headers:\n\n- `x-algolia-application-id`. Your Algolia application ID.\n- `x-algolia-api-key`. An API key with the necessary permissions to make the request.\n  The required access control list (ACL) to make a request is listed in each endpoint's reference.\n\nYou can find your application ID and API key in the [Algolia dashboard](https://dashboard.algolia.com/account).\n\n## Request format\n\nDepending on the endpoint, request bodies are either JSON objects or arrays of JSON objects,\n\n## Parameters\n\nParameters are passed in the request body for POST and PUT requests.\nQuery parameters must be [URL-encoded](https://developer.mozilla.org/en-US/docs/Glossary/Percent-encoding).\nNon-ASCII characters must be UTF-8 encoded.\nPlus characters (`+`) are interpreted as spaces.\n\n## Response status and errors\n\nThe Composition API returns JSON responses.\nSince JSON doesn't guarantee any specific ordering, don't rely on the order of attributes in the API response.\n\nSuccessful responses return a `2xx` status. Client errors return a `4xx` status. Server errors are indicated by a `5xx` status.\nError responses have a `message` property with more information.\n\n## Version\n\nThe current version of the Composition API is version 1, as indicated by the `/1/` in each endpoint's URL.\n",
     "version": "1.0.0"
   },
   "servers": [
@@ -244,15 +244,11 @@
     },
     "/1/compositions/{compositionID}/run": {
       "post": {
-        "tags": [
-          "Search"
-        ],
+        "tags": ["Search"],
         "operationId": "search",
         "x-use-read-transporter": true,
         "x-cacheable": true,
-        "x-acl": [
-          "search"
-        ],
+        "x-acl": ["search"],
         "summary": "Run a Composition",
         "description": "Runs a query on a single composition and returns matching results.",
         "parameters": [
@@ -305,15 +301,11 @@
     },
     "/1/compositions/{compositionID}/facets/{facetName}/query": {
       "post": {
-        "tags": [
-          "Search"
-        ],
+        "tags": ["Search"],
         "operationId": "searchForFacetValues",
         "x-use-read-transporter": true,
         "x-cacheable": true,
-        "x-acl": [
-          "search"
-        ],
+        "x-acl": ["search"],
         "summary": "Search for facet values",
         "description": "Searches for values of a specified facet attribute on the composition's main source's index.\n\n- By default, facet values are sorted by decreasing count.\n  You can adjust this with the `sortFacetValueBy` parameter.\n- Searching for facet values doesn't work if you have **more than 65 searchable facets and searchable attributes combined**.\n",
         "parameters": [
@@ -386,14 +378,9 @@
     },
     "/1/compositions": {
       "get": {
-        "tags": [
-          "Compositions"
-        ],
+        "tags": ["Compositions"],
         "operationId": "listCompositions",
-        "x-acl": [
-          "editSettings",
-          "settings"
-        ],
+        "x-acl": ["editSettings", "settings"],
         "summary": "List compositions",
         "description": "Lists all compositions in the current Algolia application.\n",
         "parameters": [
@@ -432,14 +419,9 @@
     },
     "/1/compositions/{compositionID}": {
       "get": {
-        "tags": [
-          "Compositions"
-        ],
+        "tags": ["Compositions"],
         "operationId": "getComposition",
-        "x-acl": [
-          "editSettings",
-          "settings"
-        ],
+        "x-acl": ["editSettings", "settings"],
         "summary": "Retrieve a composition",
         "description": "Retrieve a single composition in the current Algolia application.\n",
         "parameters": [
@@ -473,13 +455,9 @@
         }
       },
       "put": {
-        "tags": [
-          "Compositions"
-        ],
+        "tags": ["Compositions"],
         "operationId": "putComposition",
-        "x-acl": [
-          "editSettings"
-        ],
+        "x-acl": ["editSettings"],
         "summary": "Upsert a composition",
         "description": "Upsert a composition in the current Algolia application.\n",
         "parameters": [
@@ -511,9 +489,7 @@
                       "$ref": "#/components/schemas/taskID"
                     }
                   },
-                  "required": [
-                    "taskID"
-                  ]
+                  "required": ["taskID"]
                 }
               }
             }
@@ -533,13 +509,9 @@
         }
       },
       "delete": {
-        "tags": [
-          "Compositions"
-        ],
+        "tags": ["Compositions"],
         "operationId": "deleteComposition",
-        "x-acl": [
-          "editSettings"
-        ],
+        "x-acl": ["editSettings"],
         "summary": "Delete a composition",
         "description": "Delete a composition from the current Algolia application.\n",
         "parameters": [
@@ -561,9 +533,7 @@
                       "$ref": "#/components/schemas/taskID"
                     }
                   },
-                  "required": [
-                    "taskID"
-                  ]
+                  "required": ["taskID"]
                 }
               }
             }
@@ -582,14 +552,10 @@
     },
     "/1/compositions/*/batch": {
       "post": {
-        "tags": [
-          "Compositions"
-        ],
+        "tags": ["Compositions"],
         "operationId": "multipleBatch",
         "description": "Adds, updates, or deletes compositions with a single API request.\n",
-        "x-acl": [
-          "editSettings"
-        ],
+        "x-acl": ["editSettings"],
         "summary": "Batch action to multiple compositions",
         "requestBody": {
           "required": true,
@@ -615,16 +581,11 @@
                           "$ref": "#/components/schemas/batchCompositionAction"
                         }
                       },
-                      "required": [
-                        "action",
-                        "body"
-                      ]
+                      "required": ["action", "body"]
                     }
                   }
                 },
-                "required": [
-                  "requests"
-                ]
+                "required": ["requests"]
               }
             }
           }
@@ -647,9 +608,7 @@
                       }
                     }
                   },
-                  "required": [
-                    "taskID"
-                  ]
+                  "required": ["taskID"]
                 }
               }
             }
@@ -671,16 +630,11 @@
     },
     "/1/compositions/{compositionID}/rules/{objectID}": {
       "get": {
-        "tags": [
-          "Composition Rules"
-        ],
+        "tags": ["Composition Rules"],
         "operationId": "getRule",
-        "x-acl": [
-          "editSettings",
-          "settings"
-        ],
+        "x-acl": ["editSettings", "settings"],
         "summary": "Retrieve a rule",
-        "description": "Retrieves a rule by its ID.\nTo find the object ID of rules, use the [`search` operation](#tag/Rules/operation/searchRules).\n",
+        "description": "Retrieves a rule by its ID.\n\nTo find the object ID of a rule, use the [`search` operation](https://www.algolia.com/doc/rest-api/composition/search-composition-rules).\n",
         "parameters": [
           {
             "$ref": "#/components/parameters/compositionID"
@@ -715,15 +669,11 @@
         }
       },
       "put": {
-        "tags": [
-          "Composition Rules"
-        ],
+        "tags": ["Composition Rules"],
         "operationId": "putCompositionRule",
-        "x-acl": [
-          "editSettings"
-        ],
-        "summary": "Upsert a composition rule",
-        "description": "Upsert a Composition Rule for the specified composition ID.\n",
+        "x-acl": ["editSettings"],
+        "summary": "Add or update a composition rule",
+        "description": "If a composition rule with the provided ID already exists,\nit's replaced. Otherwise, a new one is added.\n",
         "parameters": [
           {
             "$ref": "#/components/parameters/compositionID"
@@ -756,9 +706,7 @@
                       "$ref": "#/components/schemas/taskID"
                     }
                   },
-                  "required": [
-                    "taskID"
-                  ]
+                  "required": ["taskID"]
                 }
               }
             }
@@ -781,13 +729,9 @@
         }
       },
       "delete": {
-        "tags": [
-          "Composition Rules"
-        ],
+        "tags": ["Composition Rules"],
         "operationId": "deleteCompositionRule",
-        "x-acl": [
-          "editSettings"
-        ],
+        "x-acl": ["editSettings"],
         "summary": "Delete a Composition Rule",
         "description": "Delete a Composition Rule from the specified Composition ID.\n",
         "parameters": [
@@ -812,9 +756,7 @@
                       "$ref": "#/components/schemas/taskID"
                     }
                   },
-                  "required": [
-                    "taskID"
-                  ]
+                  "required": ["taskID"]
                 }
               }
             }
@@ -836,13 +778,9 @@
     },
     "/1/compositions/{compositionID}/rules/batch": {
       "post": {
-        "tags": [
-          "Composition Rules"
-        ],
+        "tags": ["Composition Rules"],
         "operationId": "saveRules",
-        "x-acl": [
-          "editSettings"
-        ],
+        "x-acl": ["editSettings"],
         "summary": "Create or update or delete composition rules",
         "description": "Create or update or delete multiple composition rules.\n",
         "x-codegen-request-body-name": "rules",
@@ -875,10 +813,7 @@
                           "$ref": "#/components/schemas/rulesBatchCompositionAction"
                         }
                       },
-                      "required": [
-                        "action",
-                        "body"
-                      ]
+                      "required": ["action", "body"]
                     }
                   }
                 }
@@ -900,9 +835,7 @@
                       "$ref": "#/components/schemas/taskID"
                     }
                   },
-                  "required": [
-                    "taskID"
-                  ]
+                  "required": ["taskID"]
                 }
               }
             }
@@ -924,13 +857,9 @@
     },
     "/1/compositions/{compositionID}/rules/search": {
       "post": {
-        "tags": [
-          "Composition Rules"
-        ],
+        "tags": ["Composition Rules"],
         "operationId": "searchCompositionRules",
-        "x-acl": [
-          "settings"
-        ],
+        "x-acl": ["settings"],
         "summary": "Search for composition rules",
         "description": "Searches for composition rules in your index.",
         "parameters": [
@@ -990,12 +919,7 @@
                   "title": "searchCompositionRulesResponse",
                   "type": "object",
                   "additionalProperties": false,
-                  "required": [
-                    "hits",
-                    "nbHits",
-                    "page",
-                    "nbPages"
-                  ],
+                  "required": ["hits", "nbHits", "page", "nbPages"],
                   "properties": {
                     "hits": {
                       "type": "array",
@@ -1038,17 +962,9 @@
     },
     "/1/compositions/{compositionID}/task/{taskID}": {
       "get": {
-        "tags": [
-          "Advanced"
-        ],
+        "tags": ["Advanced"],
         "operationId": "getTask",
-        "x-acl": [
-          "editSettings",
-          "settings",
-          "addObject",
-          "deleteObject",
-          "deleteIndex"
-        ],
+        "x-acl": ["editSettings", "settings", "addObject", "deleteObject", "deleteIndex"],
         "description": "Checks the status of a given task.\n",
         "summary": "Check task status",
         "parameters": [
@@ -1097,9 +1013,7 @@
       "get": {
         "x-helper": true,
         "x-asynchronous-helper": false,
-        "tags": [
-          "Api Key"
-        ],
+        "tags": ["Api Key"],
         "operationId": "setClientApiKey",
         "summary": "Switch the API key used to authenticate requests",
         "description": "Switch the API key used to authenticate requests.\n",
@@ -1124,9 +1038,7 @@
     "/waitForCompositionTask": {
       "get": {
         "x-helper": true,
-        "tags": [
-          "Records"
-        ],
+        "tags": ["Records"],
         "operationId": "waitForCompositionTask",
         "summary": "Wait for operation to complete",
         "description": "Wait for a task to complete to ensure synchronized composition updates.\n\nAll Algolia write operations are asynchronous. When you make a request for a write operation, for example, to upsert or delete a composition, Algolia creates a task on a queue and returns a taskID. The task itself runs separately, depending on the server load.\n",
@@ -1273,53 +1185,37 @@
         "type": "string",
         "description": "Search query.",
         "default": "",
-        "x-categories": [
-          "Search"
-        ]
+        "x-categories": ["Search"]
       },
       "filters": {
         "type": "string",
-        "description": "Filter expression to only include items that match the filter criteria in the response.\n\nYou can use these filter expressions:\n\n- **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`.\n- **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive).\n- **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value.\n- **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive).\n- **Boolean filters.** `<facet>: true | false`.\n\nYou can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:\n\n- You can only combine filters of the same type with `OR`.\n  **Not supported:** `facet:value OR num > 3`.\n- You can't use `NOT` with combinations of filters.\n  **Not supported:** `NOT(facet:value OR facet:value)`\n- You can't combine conjunctions (`AND`) with `OR`.\n  **Not supported:** `facet:value OR (facet:value AND facet:value)`\n\nUse quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes.\nIf a facet attribute is an array, the filter matches if it matches at least one element of the array.\n\nFor more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/).\n",
+        "description": "Filter expression to only include items that match the filter criteria in the response.\n\nYou can use these filter expressions:\n\n- **Numeric filters.** `<facet> <op> <number>`, where `<op>` is one of `<`, `<=`, `=`, `!=`, `>`, `>=`.\n- **Ranges.** `<facet>:<lower> TO <upper>` where `<lower>` and `<upper>` are the lower and upper limits of the range (inclusive).\n- **Facet filters.** `<facet>:<value>` where `<facet>` is a facet attribute (case-sensitive) and `<value>` a facet value.\n- **Tag filters.** `_tags:<value>` or just `<value>` (case-sensitive).\n- **Boolean filters.** `<facet>: true | false`.\n\nYou can combine filters with `AND`, `OR`, and `NOT` operators with the following restrictions:\n\n- You can only combine filters of the same type with `OR`.\n  **Not supported:** `facet:value OR num > 3`.\n- You can't use `NOT` with combinations of filters.\n  **Not supported:** `NOT(facet:value OR facet:value)`\n- You can't combine conjunctions (`AND`) with `OR`.\n  **Not supported:** `facet:value OR (facet:value AND facet:value)`\n\nUse quotes around your filters, if the facet attribute name or facet value has spaces, keywords (`OR`, `AND`, `NOT`), or quotes.\nIf a facet attribute is an array, the filter matches if it matches at least one element of the array.\n\nFor more information, see [Filters](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering).\n",
         "example": "(category:Book OR category:Ebook) AND _tags:published",
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "page": {
         "type": "integer",
         "description": "Page of search results to retrieve.",
         "default": 0,
         "minimum": 0,
-        "x-categories": [
-          "Pagination"
-        ]
+        "x-categories": ["Pagination"]
       },
       "getRankingInfo": {
         "type": "boolean",
         "description": "Whether the run response should include detailed ranking information.",
         "default": false,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "relevancyStrictness": {
         "type": "integer",
         "example": 90,
         "description": "Relevancy threshold below which less relevant results aren't included in the results\nYou can only set `relevancyStrictness` on [virtual replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/#what-are-virtual-replicas).\nUse this setting to strike a balance between the relevance and number of returned results.\n",
         "default": 100,
-        "x-categories": [
-          "Ranking"
-        ]
+        "x-categories": ["Ranking"]
       },
       "facetFilters": {
         "description": "Filter the search by facet values, so that only records with the same facet values are retrieved.\n\n**Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.**\n\n- `[filter1, filter2]` is interpreted as `filter1 AND filter2`.\n- `[[filter1, filter2], filter3]` is interpreted as `filter1 OR filter2 AND filter3`.\n- `facet:-value` is interpreted as `NOT facet:value`.\n\nWhile it's best to avoid attributes that start with a `-`, you can still filter them by escaping with a backslash:\n`facet:\\-value`.\n",
-        "example": [
-          [
-            "category:Book",
-            "category:-Movie"
-          ],
-          "author:John Doe"
-        ],
+        "example": [["category:Book", "category:-Movie"], "author:John Doe"],
         "oneOf": [
           {
             "type": "array",
@@ -1331,16 +1227,11 @@
             "type": "string"
           }
         ],
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "optionalFilters": {
-        "description": "Filters to promote or demote records in the search results.\n\nOptional filters work like facet filters, but they don't exclude records from the search results.\nRecords that match the optional filter rank before records that don't match.\nIf you're using a negative filter `facet:-value`, matching records rank after records that don't match.\n\n- Optional filters don't work on virtual replicas.\n- Optional filters are applied _after_ sort-by attributes.\n- Optional filters are applied _before_ custom ranking attributes (in the default [ranking](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/)).\n- Optional filters don't work with numeric attributes.\n",
-        "example": [
-          "category:Book",
-          "author:John Doe"
-        ],
+        "description": "Filters to promote or demote records in the search results.\n\nOptional filters work like facet filters, but they don't exclude records from the search results.\nRecords that match the optional filter rank before records that don't match.\nIf you're using a negative filter `facet:-value`, matching records rank after records that don't match.\n\n- Optional filters don't work on virtual replicas.\n- Optional filters are applied _after_ sort-by attributes.\n- Optional filters are applied _before_ custom ranking attributes (in the default [ranking](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria)).\n- Optional filters don't work with numeric attributes.\n",
+        "example": ["category:Book", "author:John Doe"],
         "oneOf": [
           {
             "type": "array",
@@ -1352,19 +1243,11 @@
             "type": "string"
           }
         ],
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "numericFilters": {
         "description": "Filter by numeric facets.\n\n**Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.**\n\nYou can use numeric comparison operators: `<`, `<=`, `=`, `!=`, `>`, `>=`.\nComparisons are precise up to 3 decimals.\nYou can also provide ranges: `facet:<lower> TO <upper>`. The range includes the lower and upper boundaries.\nThe same combination rules apply as for `facetFilters`.\n",
-        "example": [
-          [
-            "inStock = 1",
-            "deliveryDate < 1441755506"
-          ],
-          "price < 1000"
-        ],
+        "example": [["inStock = 1", "deliveryDate < 1441755506"], "price < 1000"],
         "oneOf": [
           {
             "type": "array",
@@ -1376,9 +1259,7 @@
             "type": "string"
           }
         ],
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "hitsPerPage": {
         "type": "integer",
@@ -1386,34 +1267,26 @@
         "default": 20,
         "minimum": 1,
         "maximum": 1000,
-        "x-categories": [
-          "Pagination"
-        ]
+        "x-categories": ["Pagination"]
       },
       "aroundLatLng": {
         "type": "string",
         "description": "Coordinates for the center of a circle, expressed as a comma-separated string of latitude and longitude.\n\nOnly records included within a circle around this central location are included in the results.\nThe radius of the circle is determined by the `aroundRadius` and `minimumAroundRadius` settings.\nThis parameter is ignored if you also specify `insidePolygon` or `insideBoundingBox`.\n",
         "example": "40.71,-74.01",
         "default": "",
-        "x-categories": [
-          "Geo-Search"
-        ]
+        "x-categories": ["Geo-Search"]
       },
       "aroundLatLngViaIP": {
         "type": "boolean",
         "description": "Whether to obtain the coordinates from the request's IP address.",
         "default": false,
-        "x-categories": [
-          "Geo-Search"
-        ]
+        "x-categories": ["Geo-Search"]
       },
       "aroundRadiusAll": {
         "title": "all",
         "type": "string",
         "description": "Return all records with a valid `_geoloc` attribute. Don't filter by distance.",
-        "enum": [
-          "all"
-        ]
+        "enum": ["all"]
       },
       "aroundRadius": {
         "description": "Maximum radius for a search around a central location.\n\nThis parameter works in combination with the `aroundLatLng` and `aroundLatLngViaIP` parameters.\nBy default, the search radius is determined automatically from the density of hits around the central location.\nThe search radius is small if there are many hits close to the central coordinates.\n",
@@ -1427,9 +1300,7 @@
             "$ref": "#/components/schemas/aroundRadiusAll"
           }
         ],
-        "x-categories": [
-          "Geo-Search"
-        ]
+        "x-categories": ["Geo-Search"]
       },
       "aroundPrecisionFromValue": {
         "title": "range objects",
@@ -1463,17 +1334,13 @@
             "$ref": "#/components/schemas/aroundPrecisionFromValue"
           }
         ],
-        "x-categories": [
-          "Geo-Search"
-        ]
+        "x-categories": ["Geo-Search"]
       },
       "minimumAroundRadius": {
         "type": "integer",
         "description": "Minimum radius (in meters) for a search around a location when `aroundRadius` isn't set.",
         "minimum": 1,
-        "x-categories": [
-          "Geo-Search"
-        ]
+        "x-categories": ["Geo-Search"]
       },
       "insideBoundingBoxArray": {
         "type": "array",
@@ -1488,22 +1355,10 @@
         },
         "description": "Coordinates for a rectangular area in which to search.\n\nEach bounding box is defined by the two opposite points of its diagonal, and expressed as latitude and longitude pair:\n`[p1 lat, p1 long, p2 lat, p2 long]`.\nProvide multiple bounding boxes as nested arrays.\nFor more information, see [rectangular area](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas).\n",
         "example": [
-          [
-            47.3165,
-            4.9665,
-            47.3424,
-            5.0201
-          ],
-          [
-            40.9234,
-            2.1185,
-            38.643,
-            1.9916
-          ]
+          [47.3165, 4.9665, 47.3424, 5.0201],
+          [40.9234, 2.1185, 38.643, 1.9916]
         ],
-        "x-categories": [
-          "Geo-Search"
-        ]
+        "x-categories": ["Geo-Search"]
       },
       "insideBoundingBox": {
         "oneOf": [
@@ -1531,26 +1386,10 @@
         },
         "description": "Coordinates of a polygon in which to search.\n\nPolygons are defined by 3 to 10,000 points. Each point is represented by its latitude and longitude.\nProvide multiple polygons as nested arrays.\nFor more information, see [filtering inside polygons](https://www.algolia.com/doc/guides/managing-results/refine-results/geolocation/#filtering-inside-rectangular-or-polygonal-areas).\nThis parameter is ignored if you also specify `insideBoundingBox`.\n",
         "example": [
-          [
-            47.3165,
-            4.9665,
-            47.3424,
-            5.0201,
-            47.32,
-            4.9
-          ],
-          [
-            40.9234,
-            2.1185,
-            38.643,
-            1.9916,
-            39.2587,
-            2.0104
-          ]
+          [47.3165, 4.9665, 47.3424, 5.0201, 47.32, 4.9],
+          [40.9234, 2.1185, 38.643, 1.9916, 39.2587, 2.0104]
         ],
-        "x-categories": [
-          "Geo-Search"
-        ]
+        "x-categories": ["Geo-Search"]
       },
       "supportedLanguage": {
         "type": "string",
@@ -1631,14 +1470,10 @@
         "items": {
           "$ref": "#/components/schemas/supportedLanguage"
         },
-        "example": [
-          "es"
-        ],
-        "description": "Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries \nThis setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` settings.\nThis setting also sets a dictionary for word detection in the logogram-based [CJK](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/#normalization-for-logogram-based-languages-cjk) languages.\nTo support this, you must place the CJK language **first** \n**You should always specify a query language.**\nIf you don't specify an indexing language, the search engine uses all [supported languages](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages/),\nor the languages you specified with the `ignorePlurals` or `removeStopWords` parameters.\nThis can lead to unexpected search results.\nFor more information, see [Language-specific configuration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/).\n",
+        "example": ["es"],
+        "description": "Languages for language-specific query processing steps such as plurals, stop-word removal, and word-detection dictionaries \nThis setting sets a default list of languages used by the `removeStopWords` and `ignorePlurals` settings.\nThis setting also sets a dictionary for word detection in the logogram-based [CJK](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/#normalization-for-logogram-based-languages-cjk) languages.\nTo support this, you must place the CJK language **first** \n**You should always specify a query language.**\nIf you don't specify an indexing language, the search engine uses all [supported languages](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/supported-languages),\nor the languages you specified with the `ignorePlurals` or `removeStopWords` parameters.\nThis can lead to unexpected search results.\nFor more information, see [Language-specific configuration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations).\n",
         "default": [],
-        "x-categories": [
-          "Languages"
-        ]
+        "x-categories": ["Languages"]
       },
       "naturalLanguages": {
         "type": "array",
@@ -1647,17 +1482,13 @@
         },
         "description": "ISO language codes that adjust settings that are useful for processing natural language queries (as opposed to keyword searches)\n- Sets `removeStopWords` and `ignorePlurals` to the list of provided languages.\n- Sets `removeWordsIfNoResults` to `allOptional`.\n- Adds a `natural_language` attribute to `ruleContexts` and `analyticsTags`.\n",
         "default": [],
-        "x-categories": [
-          "Languages"
-        ]
+        "x-categories": ["Languages"]
       },
       "enableRules": {
         "type": "boolean",
         "description": "Whether to enable composition rules.",
         "default": true,
-        "x-categories": [
-          "Composition Rules"
-        ]
+        "x-categories": ["Composition Rules"]
       },
       "ruleContexts": {
         "type": "array",
@@ -1666,60 +1497,46 @@
         },
         "description": "Assigns a rule context to the run query\n[Rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) are strings that you can use to trigger matching rules.\n",
         "default": [],
-        "example": [
-          "mobile"
-        ],
-        "x-categories": [
-          "Composition Rules"
-        ]
+        "example": ["mobile"],
+        "x-categories": ["Composition Rules"]
       },
       "userToken": {
         "type": "string",
-        "description": "Unique pseudonymous or anonymous user identifier.\n\nThis helps with analytics and click and conversion events.\nFor more information, see [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken/).\n",
+        "description": "Unique pseudonymous or anonymous user identifier.\n\nThis helps with analytics and click and conversion events.\nFor more information, see [user token](https://www.algolia.com/doc/guides/sending-events/concepts/usertoken).\n",
         "example": "test-user-123",
-        "x-categories": [
-          "Personalization"
-        ]
+        "x-categories": ["Personalization"]
       },
       "clickAnalytics": {
         "type": "boolean",
-        "description": "Whether to include a `queryID` attribute in the response\nThe query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started/).\n",
+        "description": "Whether to include a `queryID` attribute in the response\nThe query ID is a unique identifier for a search query and is required for tracking [click and conversion events](https://www.algolia.com/guides/sending-events/getting-started).\n",
         "default": false,
-        "x-categories": [
-          "Analytics"
-        ]
+        "x-categories": ["Analytics"]
       },
       "analytics": {
         "type": "boolean",
         "description": "Whether this search will be included in Analytics.",
         "default": true,
-        "x-categories": [
-          "Analytics"
-        ]
+        "x-categories": ["Analytics"]
       },
       "analyticsTags": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "description": "Tags to apply to the query for [segmenting analytics data](https://www.algolia.com/doc/guides/search-analytics/guides/segments/).",
+        "description": "Tags to apply to the query for [segmenting analytics data](https://www.algolia.com/doc/guides/search-analytics/guides/segments).",
         "default": []
       },
       "enableABTest": {
         "type": "boolean",
         "description": "Whether to enable index level A/B testing for this run request.\nIf the composition mixes multiple indices, the A/B test is ignored.\n",
         "default": true,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "enableReRanking": {
         "type": "boolean",
-        "description": "Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/)\nThis setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.\n",
+        "description": "Whether this search will use [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking)\nThis setting only has an effect if you activated Dynamic Re-Ranking for this index in the Algolia dashboard.\n",
         "default": true,
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "externalInjectedItem": {
         "type": "object",
@@ -1744,9 +1561,7 @@
                   }
                 }
               },
-              "required": [
-                "objectID"
-              ],
+              "required": ["objectID"],
               "example": {
                 "objectID": "my-object-1",
                 "metadata": {
@@ -1756,9 +1571,7 @@
             }
           }
         },
-        "required": [
-          "items"
-        ]
+        "required": ["items"]
       },
       "injectedItems": {
         "type": "object",
@@ -1767,9 +1580,7 @@
         },
         "description": "A list of extenrally injected objectID groups into from an external source.\n",
         "default": {},
-        "x-categories": [
-          "Retail Media Network"
-        ]
+        "x-categories": ["Retail Media Network"]
       },
       "params": {
         "title": "Run composition parameters as object",
@@ -1881,15 +1692,11 @@
                   "$ref": "#/components/schemas/objectID"
                 }
               },
-              "required": [
-                "objectID"
-              ]
+              "required": ["objectID"]
             }
           }
         },
-        "required": [
-          "objectID"
-        ]
+        "required": ["objectID"]
       },
       "compositionsSearchResponse": {
         "type": "object",
@@ -1902,16 +1709,12 @@
             }
           }
         },
-        "required": [
-          "run"
-        ]
+        "required": ["run"]
       },
       "compositionBaseSearchResponse": {
         "type": "object",
         "additionalProperties": true,
-        "required": [
-          "processingTimeMS"
-        ],
+        "required": ["processingTimeMS"],
         "properties": {
           "compositions": {
             "$ref": "#/components/schemas/compositionsSearchResponse"
@@ -1946,9 +1749,7 @@
             "title": "redirectRuleIndexData",
             "type": "object",
             "description": "Redirect rule data.",
-            "required": [
-              "ruleObjectID"
-            ],
+            "required": ["ruleObjectID"],
             "properties": {
               "ruleObjectID": {
                 "type": "string"
@@ -1956,13 +1757,7 @@
             }
           }
         },
-        "required": [
-          "data",
-          "succeed",
-          "reason",
-          "dest",
-          "source"
-        ]
+        "required": ["data", "succeed", "reason", "dest", "source"]
       },
       "order": {
         "description": "Explicit order of facets or facet values.\n\nThis setting lets you always show specific facets or facet values at the top of the list.\n",
@@ -1984,11 +1779,7 @@
       "sortRemainingBy": {
         "description": "Order of facet values that aren't explicitly positioned with the `order` setting.\n\n- `count`.\n  Order remaining facet values by decreasing count.\n  The count is the number of matching records containing this facet value.\n\n- `alpha`.\n  Sort facet values alphabetically.\n\n- `hidden`.\n  Don't show facet values that aren't explicitly positioned.\n",
         "type": "string",
-        "enum": [
-          "count",
-          "alpha",
-          "hidden"
-        ]
+        "enum": ["count", "alpha", "hidden"]
       },
       "hide": {
         "description": "Hide facet values.",
@@ -2124,9 +1915,7 @@
             "$ref": "#/components/schemas/widgets"
           }
         },
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "userData": {
         "example": {
@@ -2135,9 +1924,7 @@
         },
         "description": "An object with custom data.\n\nYou can store up to 32kB as custom data.\n",
         "default": {},
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "baseSearchResponse": {
         "type": "object",
@@ -2304,7 +2091,7 @@
           "redirect": {
             "title": "redirect",
             "type": "object",
-            "description": "[Redirect results to a URL](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/redirects/), this this parameter is for internal use only.\n",
+            "description": "[Redirect results to a URL](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/redirects), this this parameter is for internal use only.\n",
             "properties": {
               "index": {
                 "type": "array",
@@ -2332,7 +2119,7 @@
           },
           "queryID": {
             "type": "string",
-            "description": "Unique identifier for the query. This is used for [click analytics](https://www.algolia.com/doc/guides/analytics/click-analytics/).",
+            "description": "Unique identifier for the query. This is used for [click analytics](https://www.algolia.com/doc/guides/analytics/click-analytics).",
             "example": "a00dbc80a8d13c4565a442e7e2dca80a"
           },
           "_automaticInsights": {
@@ -2368,12 +2155,7 @@
             "$ref": "#/components/schemas/hitsPerPage"
           }
         },
-        "required": [
-          "page",
-          "nbHits",
-          "nbPages",
-          "hitsPerPage"
-        ]
+        "required": ["page", "nbHits", "nbPages", "hitsPerPage"]
       },
       "highlightedValue": {
         "type": "string",
@@ -2383,11 +2165,7 @@
       "matchLevel": {
         "type": "string",
         "description": "Whether the whole query string matches or only a part.",
-        "enum": [
-          "none",
-          "partial",
-          "full"
-        ]
+        "enum": ["none", "partial", "full"]
       },
       "highlightResultOption": {
         "title": "highlightResultOption",
@@ -2404,9 +2182,7 @@
           "matchedWords": {
             "type": "array",
             "description": "List of matched words from the search query.",
-            "example": [
-              "action"
-            ],
+            "example": ["action"],
             "items": {
               "type": "string"
             }
@@ -2416,15 +2192,8 @@
             "description": "Whether the entire attribute value is highlighted."
           }
         },
-        "required": [
-          "value",
-          "matchLevel",
-          "matchedWords"
-        ],
-        "x-discriminator-fields": [
-          "matchLevel",
-          "matchedWords"
-        ]
+        "required": ["value", "matchLevel", "matchedWords"],
+        "x-discriminator-fields": ["matchLevel", "matchedWords"]
       },
       "highlightResultMap": {
         "title": "highlightResultMap",
@@ -2470,13 +2239,8 @@
             "$ref": "#/components/schemas/matchLevel"
           }
         },
-        "required": [
-          "value",
-          "matchLevel"
-        ],
-        "x-discriminator-fields": [
-          "matchLevel"
-        ]
+        "required": ["value", "matchLevel"],
+        "x-discriminator-fields": ["matchLevel"]
       },
       "snippetResultMap": {
         "title": "snippetResultMap",
@@ -2609,13 +2373,7 @@
             "description": "Whether the record is re-ranked."
           }
         },
-        "required": [
-          "nbTypos",
-          "firstMatchedWord",
-          "geoDistance",
-          "nbExactWords",
-          "userScore"
-        ]
+        "required": ["nbTypos", "firstMatchedWord", "geoDistance", "nbExactWords", "userScore"]
       },
       "compositionRankingInfo": {
         "type": "object",
@@ -2636,10 +2394,7 @@
                   "type": "string"
                 }
               },
-              "required": [
-                "index",
-                "injectedItemKey"
-              ]
+              "required": ["index", "injectedItemKey"]
             }
           }
         }
@@ -2673,9 +2428,7 @@
         "description": "Search result.\n\nA hit is a record from your index, augmented with special attributes for highlighting, snippeting, and ranking.\n",
         "x-is-generic": true,
         "additionalProperties": true,
-        "required": [
-          "objectID"
-        ],
+        "required": ["objectID"],
         "properties": {
           "objectID": {
             "$ref": "#/components/schemas/objectID"
@@ -2717,11 +2470,7 @@
             "example": "query=a&hitsPerPage=20"
           }
         },
-        "required": [
-          "hits",
-          "query",
-          "params"
-        ]
+        "required": ["hits", "query", "params"]
       },
       "resultsInjectedItemInfoResponse": {
         "type": "object",
@@ -2740,15 +2489,11 @@
                   "$ref": "#/components/schemas/objectID"
                 }
               },
-              "required": [
-                "objectID"
-              ]
+              "required": ["objectID"]
             }
           }
         },
-        "required": [
-          "key"
-        ]
+        "required": ["key"]
       },
       "resultsCompositionsResponse": {
         "type": "object",
@@ -2769,15 +2514,11 @@
                   }
                 }
               },
-              "required": [
-                "injectedItems"
-              ]
+              "required": ["injectedItems"]
             }
           }
         },
-        "required": [
-          "compositions"
-        ]
+        "required": ["compositions"]
       },
       "searchResultsItem": {
         "allOf": [
@@ -2807,9 +2548,7 @@
             }
           }
         },
-        "required": [
-          "results"
-        ]
+        "required": ["results"]
       },
       "searchResponse": {
         "additionalProperties": true,
@@ -2827,21 +2566,13 @@
         "description": "Maximum number of facet values to return when [searching for facet values](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#search-for-facet-values).",
         "maximum": 100,
         "default": 10,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "searchForFacetValuesResults": {
         "type": "object",
         "additionalProperties": false,
-        "required": [
-          "facetHits",
-          "exhaustiveFacetsCount",
-          "indexName"
-        ],
-        "x-discriminator-fields": [
-          "facetHits"
-        ],
+        "required": ["facetHits", "exhaustiveFacetsCount", "indexName"],
+        "x-discriminator-fields": ["facetHits"],
         "properties": {
           "indexName": {
             "type": "string"
@@ -2853,11 +2584,7 @@
               "title": "facetHits",
               "type": "object",
               "additionalProperties": false,
-              "required": [
-                "value",
-                "highlighted",
-                "count"
-              ],
+              "required": ["value", "highlighted", "count"],
               "properties": {
                 "value": {
                   "description": "Facet value.",
@@ -2900,19 +2627,12 @@
         "type": "boolean",
         "description": "Whether to support phrase matching and excluding words from search queries\nUse the `advancedSyntaxFeatures` parameter to control which feature is supported.\n",
         "default": false,
-        "x-categories": [
-          "Query strategy"
-        ]
+        "x-categories": ["Query strategy"]
       },
       "advancedSyntaxFeatures": {
         "type": "string",
-        "enum": [
-          "exactPhrase",
-          "excludeWords"
-        ],
-        "x-categories": [
-          "Query strategy"
-        ]
+        "enum": ["exactPhrase", "excludeWords"],
+        "x-categories": ["Query strategy"]
       },
       "IndexSettings_advancedSyntaxFeatures": {
         "type": "array",
@@ -2920,33 +2640,19 @@
           "$ref": "#/components/schemas/advancedSyntaxFeatures"
         },
         "description": "Advanced search syntax features you want to support\n- `exactPhrase`.\n  Phrases in quotes must match exactly.\n  For example, `sparkly blue \"iPhone case\"` only returns records with the exact string \"iPhone case\"\n- `excludeWords`.\n  Query words prefixed with a `-` must not occur in a record.\n  For example, `search -engine` matches records that contain \"search\" but not \"engine\"\nThis setting only has an effect if `advancedSyntax` is true.\n",
-        "default": [
-          "exactPhrase",
-          "excludeWords"
-        ],
-        "x-categories": [
-          "Query strategy"
-        ]
+        "default": ["exactPhrase", "excludeWords"],
+        "x-categories": ["Query strategy"]
       },
       "allowTyposOnNumericTokens": {
         "type": "boolean",
         "description": "Whether to allow typos on numbers in the search query\nTurn off this setting to reduce the number of irrelevant matches\nwhen searching in large sets of similar numbers.\n",
         "default": true,
-        "x-categories": [
-          "Typos"
-        ]
+        "x-categories": ["Typos"]
       },
       "alternativesAsExact": {
         "type": "string",
-        "enum": [
-          "ignorePlurals",
-          "singleWordSynonym",
-          "multiWordsSynonym",
-          "ignoreConjugations"
-        ],
-        "x-categories": [
-          "Query strategy"
-        ]
+        "enum": ["ignorePlurals", "singleWordSynonym", "multiWordsSynonym", "ignoreConjugations"],
+        "x-categories": ["Query strategy"]
       },
       "IndexSettings_alternativesAsExact": {
         "type": "array",
@@ -2954,106 +2660,69 @@
           "$ref": "#/components/schemas/alternativesAsExact"
         },
         "description": "Determine which plurals and synonyms should be considered an exact matches\nBy default, Algolia treats singular and plural forms of a word, and single-word synonyms, as [exact](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#exact) matches when searching.\nFor example\n- \"swimsuit\" and \"swimsuits\" are treated the same\n- \"swimsuit\" and \"swimwear\" are treated the same (if they are [synonyms](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/adding-synonyms/#regular-synonyms))\n- `ignorePlurals`.\n  Plurals and similar declensions added by the `ignorePlurals` setting are considered exact matches\n- `singleWordSynonym`.\n  Single-word synonyms, such as \"NY\" = \"NYC\", are considered exact matches\n- `multiWordsSynonym`.\n  Multi-word synonyms, such as \"NY\" = \"New York\", are considered exact matches.\n",
-        "default": [
-          "ignorePlurals",
-          "singleWordSynonym"
-        ],
-        "x-categories": [
-          "Query strategy"
-        ]
+        "default": ["ignorePlurals", "singleWordSynonym"],
+        "x-categories": ["Query strategy"]
       },
       "attributeCriteriaComputedByMinProximity": {
         "type": "boolean",
         "description": "Whether the best matching attribute should be determined by minimum proximity\nThis setting only affects ranking if the Attribute ranking criterion comes before Proximity in the `ranking` setting.\nIf true, the best matching attribute is selected based on the minimum proximity of multiple matches.\nOtherwise, the best matching attribute is determined by the order in the `searchableAttributes` setting.\n",
         "default": false,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "attributesToHighlight": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "example": [
-          "author",
-          "title",
-          "conten",
-          "content"
-        ],
-        "description": "Attributes to highlight\nBy default, all searchable attributes are highlighted.\nUse `*` to highlight all attributes or use an empty array `[]` to turn off highlighting.\nAttribute names are case-sensitive\nWith highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and `highlightPostTag`.\nYou can use this to visually highlight matching parts of a search query in your UI\nFor more information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js/).\n",
-        "x-categories": [
-          "Highlighting and Snippeting"
-        ]
+        "example": ["author", "title", "conten", "content"],
+        "description": "Attributes to highlight\nBy default, all searchable attributes are highlighted.\nUse `*` to highlight all attributes or use an empty array `[]` to turn off highlighting.\nAttribute names are case-sensitive\nWith highlighting, strings that match the search query are surrounded by HTML tags defined by `highlightPreTag` and `highlightPostTag`.\nYou can use this to visually highlight matching parts of a search query in your UI\nFor more information, see [Highlighting and snippeting](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/highlighting-snippeting/js).\n",
+        "x-categories": ["Highlighting and Snippeting"]
       },
       "attributesToRetrieve": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "example": [
-          "author",
-          "title",
-          "content"
-        ],
+        "example": ["author", "title", "content"],
         "description": "Attributes to include in the API response\nTo reduce the size of your response, you can retrieve only some of the attributes.\nAttribute names are case-sensitive\n- `*` retrieves all attributes, except attributes included in the `customRanking` and `unretrievableAttributes` settings.\n- To retrieve all attributes except a specific one, prefix the attribute with a dash and combine it with the `*`: `[\"*\", \"-ATTRIBUTE\"]`.\n- The `objectID` attribute is always included.\n",
-        "default": [
-          "*"
-        ],
-        "x-categories": [
-          "Attributes"
-        ]
+        "default": ["*"],
+        "x-categories": ["Attributes"]
       },
       "attributesToSnippet": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "example": [
-          "content:80",
-          "description"
-        ],
+        "example": ["content:80", "description"],
         "description": "Attributes for which to enable snippets.\nAttribute names are case-sensitive\nSnippets provide additional context to matched words.\nIf you enable snippets, they include 10 words, including the matched word.\nThe matched word will also be wrapped by HTML tags for highlighting.\nYou can adjust the number of words with the following notation: `ATTRIBUTE:NUMBER`,\nwhere `NUMBER` is the number of words to be extracted.\n",
         "default": [],
-        "x-categories": [
-          "Highlighting and Snippeting"
-        ]
+        "x-categories": ["Highlighting and Snippeting"]
       },
       "decompoundQuery": {
         "type": "boolean",
         "description": "Whether to split compound words in the query into their building blocks\nFor more information, see [Word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#splitting-compound-words).\nWord segmentation is supported for these languages: German, Dutch, Finnish, Swedish, and Norwegian.\nDecompounding doesn't work for words with [non-spacing mark Unicode characters](https://www.charactercodes.net/category/non-spacing_mark).\nFor example, `Gartenstühle` won't be decompounded if the `ü` consists of `u` (U+0075) and `◌̈` (U+0308).\n",
         "default": true,
-        "x-categories": [
-          "Languages"
-        ]
+        "x-categories": ["Languages"]
       },
       "disableExactOnAttributes": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "example": [
-          "description"
-        ],
+        "example": ["description"],
         "description": "Searchable attributes for which you want to [turn off the Exact ranking criterion](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/adjust-exact-settings/#turn-off-exact-for-some-attributes).\nAttribute names are case-sensitive\nThis can be useful for attributes with long values, where the likelihood of an exact match is high,\nsuch as product descriptions.\nTurning off the Exact ranking criterion for these attributes favors exact matching on other attributes.\nThis reduces the impact of individual attributes with a lot of content on ranking.\n",
         "default": [],
-        "x-categories": [
-          "Query strategy"
-        ]
+        "x-categories": ["Query strategy"]
       },
       "disableTypoToleranceOnAttributes": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "example": [
-          "sku"
-        ],
-        "description": "Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/).\nAttribute names are case-sensitive\nReturning only exact matches can help when\n- [Searching in hyphenated attributes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/).\n- Reducing the number of matches when you have too many.\n  This can happen with attributes that are long blocks of text, such as product descriptions\nConsider alternatives such as `disableTypoToleranceOnWords` or adding synonyms if your attributes have intentional unusual spellings that might look like typos.\n",
+        "example": ["sku"],
+        "description": "Attributes for which you want to turn off [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance).\nAttribute names are case-sensitive\nReturning only exact matches can help when\n- [Searching in hyphenated attributes](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes).\n- Reducing the number of matches when you have too many.\n  This can happen with attributes that are long blocks of text, such as product descriptions\nConsider alternatives such as `disableTypoToleranceOnWords` or adding synonyms if your attributes have intentional unusual spellings that might look like typos.\n",
         "default": [],
-        "x-categories": [
-          "Typos"
-        ]
+        "x-categories": ["Typos"]
       },
       "distinct": {
         "description": "Determines how many records of a group are included in the search results.\n\nRecords with the same value for the `attributeForDistinct` attribute are considered a group.\nThe `distinct` setting controls how many members of the group are returned.\nThis is useful for [deduplication and grouping](https://www.algolia.com/doc/guides/managing-results/refine-results/grouping/#introducing-algolias-distinct-feature).\n\nThe `distinct` setting is ignored if `attributeForDistinct` is not set.\n",
@@ -3065,90 +2734,64 @@
           },
           {
             "type": "integer",
-            "description": "Number of members of a group of records to include in the search results.\n\n- Don't use `distinct > 1` for records that might be [promoted by rules](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/promote-hits/).\n  The number of hits won't be correct and faceting won't work as expected.\n- With `distinct > 1`, the `hitsPerPage` parameter controls the number of returned groups.\n  For example, with `hitsPerPage: 10` and `distinct: 2`, up to 20 records are returned.\n  Likewise, the `nbHits` response attribute contains the number of returned groups.\n",
+            "description": "Number of members of a group of records to include in the search results.\n\n- Don't use `distinct > 1` for records that might be [promoted by rules](https://www.algolia.com/doc/guides/managing-results/rules/merchandising-and-promoting/how-to/promote-hits).\n  The number of hits won't be correct and faceting won't work as expected.\n- With `distinct > 1`, the `hitsPerPage` parameter controls the number of returned groups.\n  For example, with `hitsPerPage: 10` and `distinct: 2`, up to 20 records are returned.\n  Likewise, the `nbHits` response attribute contains the number of returned groups.\n",
             "minimum": 0,
             "maximum": 4,
             "default": 0
           }
         ],
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "SearchParams_enableABTest": {
         "type": "boolean",
         "description": "Whether to enable A/B testing for this search.",
         "default": true,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "enablePersonalization": {
         "type": "boolean",
         "description": "Whether to enable Personalization.",
         "default": false,
-        "x-categories": [
-          "Personalization"
-        ]
+        "x-categories": ["Personalization"]
       },
       "IndexSettings_enableRules": {
         "type": "boolean",
         "description": "Whether to enable rules.",
         "default": true,
-        "x-categories": [
-          "Rules"
-        ]
+        "x-categories": ["Rules"]
       },
       "exactOnSingleWordQuery": {
         "type": "string",
-        "enum": [
-          "attribute",
-          "none",
-          "word"
-        ],
+        "enum": ["attribute", "none", "word"],
         "description": "Determines how the [Exact ranking criterion](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/adjust-exact-settings/#turn-off-exact-for-some-attributes) is computed when the search query has only one word.\n\n- `attribute`.\n  The Exact ranking criterion is 1 if the query word and attribute value are the same.\n  For example, a search for \"road\" will match the value \"road\", but not \"road trip\".\n\n- `none`.\n  The Exact ranking criterion is ignored on single-word searches.\n\n- `word`.\n  The Exact ranking criterion is 1 if the query word is found in the attribute value.\n  The query word must have at least 3 characters and must not be a stop word.\n  Only exact matches will be highlighted,\n  partial and prefix matches won't.\n",
         "default": "attribute",
-        "x-categories": [
-          "Query strategy"
-        ]
+        "x-categories": ["Query strategy"]
       },
       "SearchParams_getRankingInfo": {
         "type": "boolean",
         "description": "Whether the search response should include detailed ranking information.",
         "default": false,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "highlightPostTag": {
         "type": "string",
         "description": "HTML tag to insert after the highlighted parts in all highlighted results and snippets.",
         "default": "</em>",
-        "x-categories": [
-          "Highlighting and Snippeting"
-        ]
+        "x-categories": ["Highlighting and Snippeting"]
       },
       "highlightPreTag": {
         "type": "string",
         "description": "HTML tag to insert before the highlighted parts in all highlighted results and snippets.",
         "default": "<em>",
-        "x-categories": [
-          "Highlighting and Snippeting"
-        ]
+        "x-categories": ["Highlighting and Snippeting"]
       },
       "booleanString": {
         "type": "string",
-        "enum": [
-          "true",
-          "false"
-        ]
+        "enum": ["true", "false"]
       },
       "ignorePlurals": {
         "description": "Treat singular, plurals, and other forms of declensions as equivalent.\nYou should only use this feature for the languages used in your index.\n",
-        "example": [
-          "ca",
-          "es"
-        ],
+        "example": ["ca", "es"],
         "oneOf": [
           {
             "type": "array",
@@ -3166,9 +2809,7 @@
             "default": false
           }
         ],
-        "x-categories": [
-          "Languages"
-        ]
+        "x-categories": ["Languages"]
       },
       "minProximity": {
         "type": "integer",
@@ -3176,40 +2817,29 @@
         "maximum": 7,
         "description": "Minimum proximity score for two matching words\nThis adjusts the [Proximity ranking criterion](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#proximity)\nby equally scoring matches that are farther apart\nFor example, if `minProximity` is 2, neighboring matches and matches with one word between them would have the same score.\n",
         "default": 1,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "minWordSizefor1Typo": {
         "type": "integer",
         "description": "Minimum number of characters a word in the search query must contain to accept matches with [one typo](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#configuring-word-length-for-typos).",
         "default": 4,
-        "x-categories": [
-          "Typos"
-        ]
+        "x-categories": ["Typos"]
       },
       "minWordSizefor2Typos": {
         "type": "integer",
         "description": "Minimum number of characters a word in the search query must contain to accept matches with [two typos](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#configuring-word-length-for-typos).",
         "default": 8,
-        "x-categories": [
-          "Typos"
-        ]
+        "x-categories": ["Typos"]
       },
       "optionalWordsArray": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "example": [
-          "blue",
-          "iphone case"
-        ],
+        "example": ["blue", "iphone case"],
         "description": "List of [optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).",
         "default": [],
-        "x-categories": [
-          "Query strategy"
-        ]
+        "x-categories": ["Query strategy"]
       },
       "optionalWords": {
         "description": "Words that should be considered optional when found in the query.\n\nBy default, records must match all words in the search query to be included in the search results.\nAdding optional words can help to increase the number of search results by running an additional search query that doesn't include the optional words.\nFor example, if the search query is \"action video\" and \"video\" is an optional word,\nthe search engine runs two queries. One for \"action video\" and one for \"action\".\nRecords that match all words are ranked higher.\n\nFor a search query with 4 or more words **and** all its words are optional,\nthe number of matched words required for a record to be included in the search results increases for every 1,000 records:\n\n- If `optionalWords` has less than 10 words, the required number of matched words increases by 1:\n  results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 2 matched words.\n- If `optionalWords` has 10 or more words, the number of required matched words increases by the number of optional words divided by 5 (rounded down).\n  For example, with 18 optional words: results 1 to 1,000 require 1 matched word, results 1,001 to 2000 need 4 matched words.\n\nFor more information, see [Optional words](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/#creating-a-list-of-optional-words).\n",
@@ -3229,9 +2859,7 @@
         "type": "boolean",
         "description": "Whether to include this search when calculating processing-time percentiles.",
         "default": true,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "personalizationImpact": {
         "type": "integer",
@@ -3239,29 +2867,18 @@
         "default": 100,
         "minimum": 0,
         "maximum": 100,
-        "x-categories": [
-          "Personalization"
-        ]
+        "x-categories": ["Personalization"]
       },
       "queryType": {
         "type": "string",
-        "enum": [
-          "prefixLast",
-          "prefixAll",
-          "prefixNone"
-        ],
-        "description": "Determines if and how query words are interpreted as prefixes.\n\nBy default, only the last query word is treated as a prefix (`prefixLast`).\nTo turn off prefix search, use `prefixNone`.\nAvoid `prefixAll`, which treats all query words as prefixes.\nThis might lead to counterintuitive results and makes your search slower.\n\nFor more information, see [Prefix searching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching/).\n",
+        "enum": ["prefixLast", "prefixAll", "prefixNone"],
+        "description": "Determines if and how query words are interpreted as prefixes.\n\nBy default, only the last query word is treated as a prefix (`prefixLast`).\nTo turn off prefix search, use `prefixNone`.\nAvoid `prefixAll`, which treats all query words as prefixes.\nThis might lead to counterintuitive results and makes your search slower.\n\nFor more information, see [Prefix searching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/in-depth/prefix-searching).\n",
         "default": "prefixLast",
-        "x-categories": [
-          "Query strategy"
-        ]
+        "x-categories": ["Query strategy"]
       },
       "removeStopWords": {
         "description": "Removes stop words from the search query.\n\nStop words are common words like articles, conjunctions, prepositions, or pronouns that have little or no meaning on their own.\nIn English, \"the\", \"a\", or \"and\" are stop words.\n\nYou should only use this feature for the languages used in your index.\n",
-        "example": [
-          "ca",
-          "es"
-        ],
+        "example": ["ca", "es"],
         "oneOf": [
           {
             "type": "array",
@@ -3276,32 +2893,21 @@
             "description": "If true, stop words are removed for all languages you included in `queryLanguages`, or for all supported languages, if `queryLanguages` is empty.\nIf false, stop words are not removed.\n"
           }
         ],
-        "x-categories": [
-          "Languages"
-        ]
+        "x-categories": ["Languages"]
       },
       "removeWordsIfNoResults": {
         "type": "string",
-        "enum": [
-          "none",
-          "lastWords",
-          "firstWords",
-          "allOptional"
-        ],
+        "enum": ["none", "lastWords", "firstWords", "allOptional"],
         "example": "firstWords",
-        "description": "Strategy for removing words from the query when it doesn't return any results.\nThis helps to avoid returning empty search results.\n\n- `none`.\n  No words are removed when a query doesn't return results.\n\n- `lastWords`.\n  Treat the last (then second to last, then third to last) word as optional,\n  until there are results or at most 5 words have been removed.\n\n- `firstWords`.\n  Treat the first (then second, then third) word as optional,\n  until there are results or at most 5 words have been removed.\n\n- `allOptional`.\n  Treat all words as optional.\n\nFor more information, see [Remove words to improve results](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results/).\n",
+        "description": "Strategy for removing words from the query when it doesn't return any results.\nThis helps to avoid returning empty search results.\n\n- `none`.\n  No words are removed when a query doesn't return results.\n\n- `lastWords`.\n  Treat the last (then second to last, then third to last) word as optional,\n  until there are results or at most 5 words have been removed.\n\n- `firstWords`.\n  Treat the first (then second, then third) word as optional,\n  until there are results or at most 5 words have been removed.\n\n- `allOptional`.\n  Treat all words as optional.\n\nFor more information, see [Remove words to improve results](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/empty-or-insufficient-results/in-depth/why-use-remove-words-if-no-results).\n",
         "default": "none",
-        "x-categories": [
-          "Query strategy"
-        ]
+        "x-categories": ["Query strategy"]
       },
       "replaceSynonymsInHighlight": {
         "type": "boolean",
         "description": "Whether to replace a highlighted word with the matched synonym\nBy default, the original words are highlighted even if a synonym matches.\nFor example, with `home` as a synonym for `house` and a search for `home`,\nrecords matching either \"home\" or \"house\" are included in the search results,\nand either \"home\" or \"house\" are highlighted\nWith `replaceSynonymsInHighlight` set to `true`, a search for `home` still matches the same records,\nbut all occurrences of \"house\" are replaced by \"home\" in the highlighted response.\n",
         "default": false,
-        "x-categories": [
-          "Highlighting and Snippeting"
-        ]
+        "x-categories": ["Highlighting and Snippeting"]
       },
       "responseFields": {
         "type": "array",
@@ -3309,35 +2915,24 @@
           "type": "string"
         },
         "description": "Properties to include in the API response of search and browse requests\nBy default, all response properties are included.\nTo reduce the response size, you can select which properties should be included\nAn empty list may lead to an empty API response (except properties you can't exclude)\nYou can't exclude these properties:\n`message`, `warning`, `cursor`, `abTestVariantID`,\nor any property added by setting `getRankingInfo` to true\nYour search depends on the `hits` field. If you omit this field, searches won't return any results.\nYour UI might also depend on other properties, for example, for pagination.\nBefore restricting the response size, check the impact on your search experience.\n",
-        "default": [
-          "*"
-        ],
-        "x-categories": [
-          "Advanced"
-        ]
+        "default": ["*"],
+        "x-categories": ["Advanced"]
       },
       "restrictHighlightAndSnippetArrays": {
         "type": "boolean",
         "description": "Whether to restrict highlighting and snippeting to items that at least partially matched the search query.\nBy default, all items are highlighted and snippeted.\n",
         "default": false,
-        "x-categories": [
-          "Highlighting and Snippeting"
-        ]
+        "x-categories": ["Highlighting and Snippeting"]
       },
       "restrictSearchableAttributes": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "example": [
-          "title",
-          "author"
-        ],
+        "example": ["title", "author"],
         "description": "Restricts a search to a subset of your searchable attributes.\nAttribute names are case-sensitive.\n",
         "default": [],
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "SearchParams_ruleContexts": {
         "type": "array",
@@ -3346,42 +2941,29 @@
         },
         "description": "Assigns a rule context to the search query\n[Rule contexts](https://www.algolia.com/doc/guides/managing-results/rules/rules-overview/how-to/customize-search-results-by-platform/#whats-a-context) are strings that you can use to trigger matching rules.\n",
         "default": [],
-        "example": [
-          "mobile"
-        ],
-        "x-categories": [
-          "Rules"
-        ]
+        "example": ["mobile"],
+        "x-categories": ["Rules"]
       },
       "snippetEllipsisText": {
         "type": "string",
         "description": "String used as an ellipsis indicator when a snippet is truncated.",
         "default": "…",
-        "x-categories": [
-          "Highlighting and Snippeting"
-        ]
+        "x-categories": ["Highlighting and Snippeting"]
       },
       "synonyms": {
         "type": "boolean",
         "description": "Whether to take into account an index's synonyms for this search.",
         "default": true,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "typoToleranceEnum": {
         "type": "string",
         "title": "typo tolerance",
         "description": "- `min`. Return matches with the lowest number of typos.\n  For example, if you have matches without typos, only include those.\n  But if there are no matches without typos (with 1 typo), include matches with 1 typo (2 typos).\n- `strict`. Return matches with the two lowest numbers of typos.\n  With `strict`, the Typo ranking criterion is applied first in the `ranking` setting.\n",
-        "enum": [
-          "min",
-          "strict",
-          "true",
-          "false"
-        ]
+        "enum": ["min", "strict", "true", "false"]
       },
       "typoTolerance": {
-        "description": "Whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/) is enabled and how it is applied.\n\nIf typo tolerance is true, `min`, or `strict`, [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) are also active.\n",
+        "description": "Whether [typo tolerance](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance) is enabled and how it is applied.\n\nIf typo tolerance is true, `min`, or `strict`, [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation) are also active.\n",
         "oneOf": [
           {
             "type": "boolean",
@@ -3392,9 +2974,7 @@
             "$ref": "#/components/schemas/typoToleranceEnum"
           }
         ],
-        "x-categories": [
-          "Typos"
-        ]
+        "x-categories": ["Typos"]
       },
       "baseInjectionQueryParameters": {
         "title": "Composition common query parameters between main and injected items as object",
@@ -3548,9 +3128,7 @@
         "type": "boolean",
         "description": "Whether faceting should be applied after deduplication with `distinct`\nThis leads to accurate facet counts when using faceting in combination with `distinct`.\nIt's usually better to use `afterDistinct` modifiers in the `attributesForFaceting` setting,\nas `facetingAfterDistinct` only computes correct facet counts if all records have the same facet values for the `attributeForDistinct`.\n",
         "default": false,
-        "x-categories": [
-          "Faceting"
-        ]
+        "x-categories": ["Faceting"]
       },
       "properties-facets": {
         "type": "array",
@@ -3559,37 +3137,27 @@
         },
         "description": "Facets for which to retrieve facet values that match the search criteria and the number of matching facet values\nTo retrieve all facets, use the wildcard character `*`.\nFor more information, see [facets](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/#contextual-facet-values-and-counts).\n",
         "default": [],
-        "example": [
-          "*"
-        ],
-        "x-categories": [
-          "Faceting"
-        ]
+        "example": ["*"],
+        "x-categories": ["Faceting"]
       },
       "maxValuesPerFacet": {
         "type": "integer",
         "description": "Maximum number of facet values to return for each facet.",
         "default": 100,
         "maximum": 1000,
-        "x-categories": [
-          "Faceting"
-        ]
+        "x-categories": ["Faceting"]
       },
       "sortFacetValuesBy": {
         "type": "string",
-        "description": "Order in which to retrieve facet values\n- `count`.\n  Facet values are retrieved by decreasing count.\n  The count is the number of matching records containing this facet value\n- `alpha`.\n  Retrieve facet values alphabetically\nThis setting doesn't influence how facet values are displayed in your UI (see `renderingContent`).\nFor more information, see [facet value display](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/facet-display/js/).\n",
+        "description": "Order in which to retrieve facet values\n- `count`.\n  Facet values are retrieved by decreasing count.\n  The count is the number of matching records containing this facet value\n- `alpha`.\n  Retrieve facet values alphabetically\nThis setting doesn't influence how facet values are displayed in your UI (see `renderingContent`).\nFor more information, see [facet value display](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/facet-display/js).\n",
         "default": "count",
-        "x-categories": [
-          "Faceting"
-        ]
+        "x-categories": ["Faceting"]
       },
       "sumOrFiltersScores": {
         "type": "boolean",
         "description": "Whether to sum all filter scores\nIf true, all filter scores are summed.\nOtherwise, the maximum filter score is kept.\nFor more information, see [filter scores](https://www.algolia.com/doc/guides/managing-results/refine-results/filtering/in-depth/filter-scoring/#accumulating-scores-with-sumorfiltersscores).\n",
         "default": false,
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "mainInjectionQueryParameters": {
         "title": "Composition Main Injection Query parameters as object",
@@ -3645,20 +3213,13 @@
                 "$ref": "#/components/schemas/baseInjectionQueryParameters"
               }
             },
-            "required": [
-              "index"
-            ]
+            "required": ["index"]
           }
         },
-        "required": [
-          "search"
-        ]
+        "required": ["search"]
       },
       "externalOrdering": {
-        "enum": [
-          "default",
-          "userDefined"
-        ],
+        "enum": ["default", "userDefined"],
         "default": "default"
       },
       "ExternalSource": {
@@ -3684,14 +3245,10 @@
                 "$ref": "#/components/schemas/externalOrdering"
               }
             },
-            "required": [
-              "index"
-            ]
+            "required": ["index"]
           }
         },
-        "required": [
-          "external"
-        ]
+        "required": ["external"]
       },
       "injectedItemSource": {
         "oneOf": [
@@ -3749,12 +3306,14 @@
             }
           }
         },
-        "required": [
-          "key",
-          "source",
-          "position",
-          "length"
-        ]
+        "required": ["key", "source", "position", "length"]
+      },
+      "dedupPositioning": {
+        "type": "string",
+        "enum": ["highest", "highestInjected"],
+        "description": "Deduplication positioning configures how a duplicate result should be resolved between an injected item and main search results.\nCurrent configuration supports:\n- 'highest': always select the item in the highest position, and remove duplicates that appear lower in the results.\n- 'highestInjected': duplicate result will be moved to its highest possible injected position, but not higher. \n  If a duplicate appears higher in main search results, it will be removed to stay it's intended group position (which could be lower than main).\n",
+        "example": "highest",
+        "default": "highestInjected"
       },
       "compositionBehavior": {
         "type": "object",
@@ -3789,19 +3348,13 @@
                             "$ref": "#/components/schemas/mainInjectionQueryParameters"
                           }
                         },
-                        "required": [
-                          "index"
-                        ]
+                        "required": ["index"]
                       }
                     },
-                    "required": [
-                      "search"
-                    ]
+                    "required": ["search"]
                   }
                 },
-                "required": [
-                  "source"
-                ]
+                "required": ["source"]
               },
               "injectedItems": {
                 "type": "array",
@@ -3811,16 +3364,24 @@
                 "items": {
                   "$ref": "#/components/schemas/injectedItem"
                 }
+              },
+              "deduplication": {
+                "title": "deduplication",
+                "type": "object",
+                "additionalProperties": false,
+                "description": "Deduplication configures the methods used to resolve duplicate items between main search results and injected group results.",
+                "properties": {
+                  "positioning": {
+                    "$ref": "#/components/schemas/dedupPositioning"
+                  }
+                },
+                "required": ["positioning"]
               }
             },
-            "required": [
-              "main"
-            ]
+            "required": ["main"]
           }
         },
-        "required": [
-          "injection"
-        ]
+        "required": ["injection"]
       },
       "composition": {
         "type": "object",
@@ -3843,11 +3404,7 @@
             "$ref": "#/components/schemas/compositionBehavior"
           }
         },
-        "required": [
-          "objectID",
-          "behavior",
-          "name"
-        ]
+        "required": ["objectID", "behavior", "name"]
       },
       "listCompositionsResponse": {
         "type": "object",
@@ -3881,26 +3438,17 @@
             "example": 200
           }
         },
-        "required": [
-          "hitsPerPage",
-          "items",
-          "nbHits",
-          "nbPages",
-          "page"
-        ]
+        "required": ["hitsPerPage", "items", "nbHits", "nbPages", "page"]
       },
       "taskID": {
         "type": "integer",
         "format": "int64",
         "example": 1514562690001,
-        "description": "Unique identifier of a task.\n\nA successful API response means that a task was added to a queue. It might not run immediately. You can check the task's progress with the [`task` operation](#tag/Indices/operation/getTask) and this `taskID`.\n"
+        "description": "Unique identifier of a task.\n\nA successful API response means that a task was added to a queue.\nIt might not run immediately.\nYou can check the task's progress with the [`task` operation](https://www.algolia.com/doc/rest-api/search/get-task) and this task ID.\n"
       },
       "action": {
         "type": "string",
-        "enum": [
-          "upsert",
-          "delete"
-        ],
+        "enum": ["upsert", "delete"],
         "description": "Type of Composition Batch operation."
       },
       "deleteCompositionAction": {
@@ -3912,9 +3460,7 @@
             "$ref": "#/components/schemas/compositionObjectID"
           }
         },
-        "required": [
-          "objectID"
-        ]
+        "required": ["objectID"]
       },
       "batchCompositionAction": {
         "oneOf": [
@@ -3939,12 +3485,7 @@
       "anchoring": {
         "type": "string",
         "description": "Which part of the search query the pattern should match:\n\n- `startsWith`. The pattern must match the beginning of the query.\n- `endsWith`. The pattern must match the end of the query.\n- `is`. The pattern must match the query exactly.\n- `contains`. The pattern must match anywhere in the query.\n\nEmpty queries are only allowed as patterns with `anchoring: is`.\n",
-        "enum": [
-          "is",
-          "startsWith",
-          "endsWith",
-          "contains"
-        ]
+        "enum": ["is", "startsWith", "endsWith", "contains"]
       },
       "context": {
         "type": "string",
@@ -4016,9 +3557,7 @@
                 "$ref": "#/components/schemas/compositionBehavior"
               }
             },
-            "required": [
-              "behavior"
-            ]
+            "required": ["behavior"]
           },
           "description": {
             "type": "string",
@@ -4043,16 +3582,10 @@
             "items": {
               "type": "string"
             },
-            "example": [
-              "conditional"
-            ]
+            "example": ["conditional"]
           }
         },
-        "required": [
-          "objectID",
-          "conditions",
-          "consequence"
-        ]
+        "required": ["objectID", "conditions", "consequence"]
       },
       "deleteCompositionRuleAction": {
         "type": "object",
@@ -4063,9 +3596,7 @@
             "$ref": "#/components/schemas/compositionRuleObjectID"
           }
         },
-        "required": [
-          "objectID"
-        ]
+        "required": ["objectID"]
       },
       "rulesBatchCompositionAction": {
         "oneOf": [
@@ -4085,21 +3616,18 @@
       "parameters_page": {
         "type": "integer",
         "minimum": 0,
-        "description": "Requested page of the API response.\n\nAlgolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).\n\n- `hitsPerPage`: sets the number of search results (_hits_) displayed per page.\n- `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.\n\nFor example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.\n"
+        "description": "Requested page of the API response.\n\nAlgolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js)).\n\n- `hitsPerPage`: sets the number of search results (_hits_) displayed per page.\n- `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.\n\nFor example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.\n"
       },
       "parameters_hitsPerPage": {
         "type": "integer",
         "default": 20,
         "minimum": 1,
         "maximum": 1000,
-        "description": "Maximum number of hits per page.\n\nAlgolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js/)).\n\n- `hitsPerPage`: sets the number of search results (_hits_) displayed per page.\n- `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.\n\nFor example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.\n"
+        "description": "Maximum number of hits per page.\n\nAlgolia uses `page` and `hitsPerPage` to control how search results are displayed ([paginated](https://www.algolia.com/doc/guides/building-search-ui/ui-and-ux-patterns/pagination/js)).\n\n- `hitsPerPage`: sets the number of search results (_hits_) displayed per page.\n- `page`: specifies the page number of the search results you want to retrieve. Page numbering starts at 0, so the first page is `page=0`, the second is `page=1`, and so on.\n\nFor example, to display 10 results per page starting from the third page, set `hitsPerPage` to 10 and `page` to 2.\n"
       },
       "taskStatus": {
         "type": "string",
-        "enum": [
-          "published",
-          "notPublished"
-        ],
+        "enum": ["published", "notPublished"],
         "description": "Task status, `published` if the task is completed, `notPublished` otherwise."
       },
       "GetTaskResponse": {
@@ -4111,9 +3639,7 @@
             "$ref": "#/components/schemas/taskStatus"
           }
         },
-        "required": [
-          "status"
-        ]
+        "required": ["status"]
       }
     },
     "responses": {
@@ -4182,12 +3708,7 @@
   "x-tagGroups": [
     {
       "name": "Composition",
-      "tags": [
-        "Search",
-        "Compositions",
-        "Composition Rules",
-        "Advanced"
-      ]
+      "tags": ["Search", "Compositions", "Composition Rules", "Advanced"]
     }
   ]
-}
+}