@algolia/n8n-nodes-algolia 0.6.0 → 0.7.0

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

@@ -2,7 +2,7 @@
   "openapi": "3.0.2",
   "info": {
     "title": "Recommend API",
-    "description": "The Recommend API lets you retrieve recommendations from one of Algolia's AI recommendation models that you previously trained on your data.\n\n## Client libraries\n\nUse Algolia's API clients and libraries to reliably integrate Algolia's APIs with your apps.\nThe official API clients are covered by Algolia's [Service Level Agreement](https://www.algolia.com/policies/sla/).\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 Recommend 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 a 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\nRequest bodies must be JSON objects.\n\n## Response status and errors\n\nThe Recommend 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 Recommend API is version 1, as indicated by the `/1/` in each endpoint's URL.\n",
+    "description": "The Recommend API lets you retrieve recommendations from one of Algolia's AI recommendation models that you previously trained on your data.\n\n## Client libraries\n\nUse Algolia's API clients and libraries to reliably integrate Algolia's APIs with your apps.\nThe official API clients are covered by Algolia's [Service Level Agreement](https://www.algolia.com/policies/sla).\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 Recommend 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 a 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\nRequest bodies must be JSON objects.\n\n## Response status and errors\n\nThe Recommend 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 Recommend API is version 1, as indicated by the `/1/` in each endpoint's URL.\n",
     "version": "1.0.0"
   },
   "servers": [
@@ -57,10 +57,10 @@
     {
       "name": "recommendations",
       "x-displayName": "Recommendations",
-      "description": "Retrieve recommendations from a pre-trained AI model. You can train models in the [Algolia dashboard](https://dashboard.algolia.com/recommend/).",
+      "description": "Retrieve recommendations from a pre-trained AI model. You can train models in the [Algolia dashboard](https://dashboard.algolia.com/recommend).",
       "externalDocs": {
-        "url": "https://www.algolia.com/doc/guides/algolia-recommend/overview/",
-        "description": "Related guide: Algolia Recommend.\n"
+        "url": "https://www.algolia.com/doc/guides/algolia-recommend/overview",
+        "description": "Algolia Recommend."
       }
     },
     {
@@ -68,8 +68,8 @@
       "x-displayName": "Rules",
       "description": "Curate your recommendations with rules, which are _if_-_then_ statements.",
       "externalDocs": {
-        "url": "https://www.algolia.com/doc/guides/algolia-recommend/how-to/rules/",
-        "description": "Related guide: Recommend Rules.\n"
+        "url": "https://www.algolia.com/doc/guides/algolia-recommend/how-to/rules",
+        "description": "Recommend Rules."
       }
     }
   ],
@@ -246,15 +246,11 @@
     },
     "/1/indexes/*/recommendations": {
       "post": {
-        "tags": [
-          "recommendations"
-        ],
+        "tags": ["recommendations"],
         "operationId": "getRecommendations",
         "x-use-read-transporter": true,
         "x-cacheable": true,
-        "x-acl": [
-          "search"
-        ],
+        "x-acl": ["search"],
         "x-legacy-signature-recommend": true,
         "summary": "Retrieve recommendations",
         "description": "Retrieves recommendations from selected AI models.\n",
@@ -276,9 +272,7 @@
                     }
                   }
                 },
-                "required": [
-                  "requests"
-                ]
+                "required": ["requests"]
               }
             }
           }
@@ -300,9 +294,7 @@
                       }
                     }
                   },
-                  "required": [
-                    "results"
-                  ]
+                  "required": ["results"]
                 }
               }
             }
@@ -324,13 +316,9 @@
     },
     "/1/indexes/{indexName}/{model}/recommend/rules/{objectID}": {
       "get": {
-        "tags": [
-          "rules"
-        ],
+        "tags": ["rules"],
         "operationId": "getRecommendRule",
-        "x-acl": [
-          "settings"
-        ],
+        "x-acl": ["settings"],
         "summary": "Retrieve a rule",
         "description": "Retrieves a Recommend rule that you previously created in the Algolia dashboard.",
         "parameters": [
@@ -370,13 +358,9 @@
         }
       },
       "delete": {
-        "tags": [
-          "rules"
-        ],
+        "tags": ["rules"],
         "operationId": "deleteRecommendRule",
-        "x-acl": [
-          "editSettings"
-        ],
+        "x-acl": ["editSettings"],
         "summary": "Delete a rule",
         "description": "Deletes a Recommend rule from a recommendation scenario.",
         "parameters": [
@@ -411,13 +395,9 @@
     },
     "/1/indexes/{indexName}/{model}/task/{taskID}": {
       "get": {
-        "tags": [
-          "rules"
-        ],
+        "tags": ["rules"],
         "operationId": "getRecommendStatus",
-        "x-acl": [
-          "editSettings"
-        ],
+        "x-acl": ["editSettings"],
         "summary": "Check task status",
         "description": "Checks the status of a given task.\n\nDeleting a Recommend rule is asynchronous.\nWhen you delete a rule, a task is created on a queue and completed depending on the load on the server.\nThe API response includes a task ID that you can use to check the status.\n",
         "parameters": [
@@ -451,9 +431,7 @@
                       "$ref": "#/components/schemas/taskStatus"
                     }
                   },
-                  "required": [
-                    "status"
-                  ]
+                  "required": ["status"]
                 }
               }
             }
@@ -475,15 +453,11 @@
     },
     "/1/indexes/{indexName}/{model}/recommend/rules/search": {
       "post": {
-        "tags": [
-          "rules"
-        ],
+        "tags": ["rules"],
         "operationId": "searchRecommendRules",
         "x-use-read-transporter": true,
         "x-cacheable": true,
-        "x-acl": [
-          "settings"
-        ],
+        "x-acl": ["settings"],
         "summary": "Search for rules",
         "description": "Searches for Recommend rules.\n\nUse an empty query to list all rules for this recommendation scenario.\n",
         "parameters": [
@@ -529,9 +503,7 @@
                   "facets": {
                     "type": "array",
                     "description": "Include facets and facet values in the response. Use `['*']` to include all facets.",
-                    "example": [
-                      "*"
-                    ],
+                    "example": ["*"],
                     "items": {
                       "type": "string",
                       "description": "Facet name for rule objects or `*` as wildcard character.",
@@ -558,12 +530,7 @@
                   "title": "searchRecommendRulesResponse",
                   "type": "object",
                   "additionalProperties": false,
-                  "required": [
-                    "hits",
-                    "nbHits",
-                    "page",
-                    "nbPages"
-                  ],
+                  "required": ["hits", "nbHits", "page", "nbPages"],
                   "properties": {
                     "hits": {
                       "type": "array",
@@ -603,13 +570,9 @@
     },
     "/1/indexes/{indexName}/{model}/recommend/rules/batch": {
       "post": {
-        "tags": [
-          "rules"
-        ],
+        "tags": ["rules"],
         "operationId": "batchRecommendRules",
-        "x-acl": [
-          "editSettings"
-        ],
+        "x-acl": ["editSettings"],
         "summary": "Create or update a batch of Recommend Rules",
         "description": "Create or update a batch of Recommend Rules\n\nEach Recommend Rule is created or updated, depending on whether a Recommend Rule with the same `objectID` already exists.\nYou may also specify `true` for `clearExistingRules`, in which case the batch will atomically replace all the existing Recommend Rules.\n\nRecommend Rules are similar to Search Rules, except that the conditions and consequences apply to a [source item](/doc/guides/algolia-recommend/overview/#recommend-models) instead of a query. The main differences are the following:\n- Conditions `pattern` and `anchoring` are unavailable.\n- Condition `filters` triggers if the source item matches the specified filters.\n- Condition `filters` accepts numeric filters.\n- Consequence `params` only covers filtering parameters.\n- Consequence `automaticFacetFilters` doesn't require a facet value placeholder (it tries to match the data source item's attributes instead).\n",
         "parameters": [
@@ -648,9 +611,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",
@@ -760,27 +721,17 @@
         "description": "Keywords to be used instead of the search query to conduct a more broader search\nUsing the `similarQuery` parameter changes other settings\n- `queryType` is set to `prefixNone`.\n- `removeStopWords` is set to true.\n- `words` is set as the first ranking criterion.\n- All remaining words are treated as `optionalWords`\nSince the `similarQuery` is supposed to do a broad search, they usually return many results.\nCombine it with `filters` to narrow down the list of results.\n",
         "default": "",
         "example": "comedy drama crime Macy Buscemi",
-        "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"]
       },
       "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",
@@ -792,16 +743,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",
@@ -813,19 +759,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",
@@ -837,19 +775,11 @@
             "type": "string"
           }
         ],
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "tagFilters": {
         "description": "Filter the search by values of the special `_tags` attribute.\n\n**Prefer using the `filters` parameter, which supports all filter types and combinations with boolean operators.**\n\nDifferent from regular facets, `_tags` can only be used for filtering (including or excluding records).\nYou won't get a facet count.\nThe same combination and escaping rules apply as for `facetFilters`.\n",
-        "example": [
-          [
-            "Book",
-            "Movie"
-          ],
-          "SciFi"
-        ],
+        "example": [["Book", "Movie"], "SciFi"],
         "oneOf": [
           {
             "type": "array",
@@ -861,32 +791,23 @@
             "type": "string"
           }
         ],
-        "x-categories": [
-          "Filtering"
-        ]
+        "x-categories": ["Filtering"]
       },
       "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"]
       },
       "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"]
       },
       "facets": {
         "type": "array",
@@ -895,45 +816,33 @@
         },
         "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"]
       },
       "facetingAfterDistinct": {
         "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"]
       },
       "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",
@@ -947,9 +856,7 @@
             "$ref": "#/components/schemas/aroundRadiusAll"
           }
         ],
-        "x-categories": [
-          "Geo-Search"
-        ]
+        "x-categories": ["Geo-Search"]
       },
       "aroundPrecisionFromValue": {
         "title": "range objects",
@@ -983,17 +890,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",
@@ -1008,22 +911,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": [
@@ -1051,26 +942,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",
@@ -1153,9 +1028,7 @@
         },
         "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"]
       },
       "ruleContexts": {
         "type": "array",
@@ -1164,12 +1037,8 @@
         },
         "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"]
       },
       "personalizationImpact": {
         "type": "integer",
@@ -1177,73 +1046,57 @@
         "default": 100,
         "minimum": 0,
         "maximum": 100,
-        "x-categories": [
-          "Personalization"
-        ]
+        "x-categories": ["Personalization"]
       },
       "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"]
       },
       "getRankingInfo": {
         "type": "boolean",
         "description": "Whether the search response should include detailed ranking information.",
         "default": false,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "synonyms": {
         "type": "boolean",
         "description": "Whether to take into account an index's synonyms for this search.",
         "default": true,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "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": []
       },
       "percentileComputation": {
         "type": "boolean",
         "description": "Whether to include this search when calculating processing-time percentiles.",
         "default": true,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "enableABTest": {
         "type": "boolean",
         "description": "Whether to enable A/B testing for this search.",
         "default": true,
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "baseRecommendSearchParams": {
         "type": "object",
@@ -1339,9 +1192,7 @@
         "type": "string",
         "description": "Search query.",
         "default": "",
-        "x-categories": [
-          "Search"
-        ]
+        "x-categories": ["Search"]
       },
       "searchParamsQuery": {
         "type": "object",
@@ -1359,18 +1210,14 @@
         },
         "description": "An object with custom data.\n\nYou can store up to 32kB as custom data.\n",
         "default": {},
-        "x-categories": [
-          "Advanced"
-        ]
+        "x-categories": ["Advanced"]
       },
       "maxFacetHits": {
         "type": "integer",
         "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"]
       },
       "baseIndexSettings": {
         "type": "object",
@@ -1388,26 +1235,19 @@
               "afterDistinct(category)",
               "afterDistinct(searchable(publisher))"
             ],
-            "description": "Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting/).\n\nFacets are attributes that let you categorize search results.\nThey can be used for filtering search results.\nBy default, no attribute is used for faceting.\nAttribute names are case-sensitive.\n\n**Modifiers**\n\n- `filterOnly(\"ATTRIBUTE\")`.\n  Allows the attribute to be used as a filter but doesn't evaluate the facet values.\n\n- `searchable(\"ATTRIBUTE\")`.\n  Allows searching for facet values.\n\n- `afterDistinct(\"ATTRIBUTE\")`.\n  Evaluates the facet count _after_ deduplication with `distinct`.\n  This ensures accurate facet counts.\n  You can apply this modifier to searchable facets: `afterDistinct(searchable(ATTRIBUTE))`.\n",
+            "description": "Attributes used for [faceting](https://www.algolia.com/doc/guides/managing-results/refine-results/faceting).\n\nFacets are attributes that let you categorize search results.\nThey can be used for filtering search results.\nBy default, no attribute is used for faceting.\nAttribute names are case-sensitive.\n\n**Modifiers**\n\n- `filterOnly(\"ATTRIBUTE\")`.\n  Allows the attribute to be used as a filter but doesn't evaluate the facet values.\n\n- `searchable(\"ATTRIBUTE\")`.\n  Allows searching for facet values.\n\n- `afterDistinct(\"ATTRIBUTE\")`.\n  Evaluates the facet count _after_ deduplication with `distinct`.\n  This ensures accurate facet counts.\n  You can apply this modifier to searchable facets: `afterDistinct(searchable(ATTRIBUTE))`.\n",
             "default": [],
-            "x-categories": [
-              "Faceting"
-            ]
+            "x-categories": ["Faceting"]
           },
           "replicas": {
             "type": "array",
             "items": {
               "type": "string"
             },
-            "example": [
-              "virtual(prod_products_price_asc)",
-              "dev_products_replica"
-            ],
-            "description": "Creates [replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas/).\n\nReplicas are copies of a primary index with the same records but different settings, synonyms, or rules.\nIf you want to offer a different ranking or sorting of your search results, you'll use replica indices.\nAll index operations on a primary index are automatically forwarded to its replicas.\nTo add a replica index, you must provide the complete set of replicas to this parameter.\nIf you omit a replica from this list, the replica turns into a regular, standalone index that will no longer be synced with the primary index.\n\n**Modifier**\n\n- `virtual(\"REPLICA\")`.\n  Create a virtual replica,\n  Virtual replicas don't increase the number of records and are optimized for [Relevant sorting](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/relevant-sort/).\n",
+            "example": ["virtual(prod_products_price_asc)", "dev_products_replica"],
+            "description": "Creates [replica indices](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/replicas).\n\nReplicas are copies of a primary index with the same records but different settings, synonyms, or rules.\nIf you want to offer a different ranking or sorting of your search results, you'll use replica indices.\nAll index operations on a primary index are automatically forwarded to its replicas.\nTo add a replica index, you must provide the complete set of replicas to this parameter.\nIf you omit a replica from this list, the replica turns into a regular, standalone index that will no longer be synced with the primary index.\n\n**Modifier**\n\n- `virtual(\"REPLICA\")`.\n  Create a virtual replica,\n  Virtual replicas don't increase the number of records and are optimized for [Relevant sorting](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/in-depth/relevant-sort).\n",
             "default": [],
-            "x-categories": [
-              "Ranking"
-            ]
+            "x-categories": ["Ranking"]
           },
           "paginationLimitedTo": {
             "type": "integer",
@@ -1421,29 +1261,20 @@
             "items": {
               "type": "string"
             },
-            "example": [
-              "total_sales"
-            ],
-            "description": "Attributes that can't be retrieved at query time.\n\nThis can be useful if you want to use an attribute for ranking or to [restrict access](https://www.algolia.com/doc/guides/security/api-keys/how-to/user-restricted-access-to-data/),\nbut don't want to include it in the search results.\nAttribute names are case-sensitive.\n",
+            "example": ["total_sales"],
+            "description": "Attributes that can't be retrieved at query time.\n\nThis can be useful if you want to use an attribute for ranking or to [restrict access](https://www.algolia.com/doc/guides/security/api-keys/how-to/user-restricted-access-to-data),\nbut don't want to include it in the search results.\nAttribute names are case-sensitive.\n",
             "default": [],
-            "x-categories": [
-              "Attributes"
-            ]
+            "x-categories": ["Attributes"]
           },
           "disableTypoToleranceOnWords": {
             "type": "array",
             "items": {
               "type": "string"
             },
-            "example": [
-              "wheel",
-              "1X2BCD"
-            ],
-            "description": "Creates a list of [words which require exact matches](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#turn-off-typo-tolerance-for-certain-words).\nThis also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation/) for the specified words.\n",
+            "example": ["wheel", "1X2BCD"],
+            "description": "Creates a list of [words which require exact matches](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/in-depth/configuring-typo-tolerance/#turn-off-typo-tolerance-for-certain-words).\nThis also turns off [word splitting and concatenation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/splitting-and-concatenation) for the specified words.\n",
             "default": [],
-            "x-categories": [
-              "Typos"
-            ]
+            "x-categories": ["Typos"]
           },
           "attributesToTransliterate": {
             "description": "Attributes, for which you want to support [Japanese transliteration](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/language-specific-configurations/#japanese-transliteration-and-type-ahead).\n\nTransliteration supports searching in any of the Japanese writing systems.\nTo support transliteration, you must set the indexing language to Japanese.\nAttribute names are case-sensitive.\n",
@@ -1451,76 +1282,53 @@
             "items": {
               "type": "string"
             },
-            "example": [
-              "name",
-              "description"
-            ],
-            "x-categories": [
-              "Languages"
-            ]
+            "example": ["name", "description"],
+            "x-categories": ["Languages"]
           },
           "camelCaseAttributes": {
             "type": "array",
             "items": {
               "type": "string"
             },
-            "example": [
-              "description"
-            ],
+            "example": ["description"],
             "description": "Attributes for which to split [camel case](https://wikipedia.org/wiki/Camel_case) words.\nAttribute names are case-sensitive.\n",
             "default": [],
-            "x-categories": [
-              "Languages"
-            ]
+            "x-categories": ["Languages"]
           },
           "decompoundedAttributes": {
             "type": "object",
             "example": {
-              "de": [
-                "name"
-              ]
+              "de": ["name"]
             },
-            "description": "Searchable attributes to which Algolia should apply [word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation/) (decompounding).\nAttribute names are case-sensitive.\n\nCompound words are formed by combining two or more individual words,\nand are particularly prevalent in Germanic languages—for example, \"firefighter\".\nWith decompounding, the individual components are indexed separately.\n\nYou can specify different lists for different languages.\nDecompounding is supported for these languages:\nDutch (`nl`), German (`de`), Finnish (`fi`), Danish (`da`), Swedish (`sv`), and Norwegian (`no`).\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",
+            "description": "Searchable attributes to which Algolia should apply [word segmentation](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/how-to/customize-segmentation) (decompounding).\nAttribute names are case-sensitive.\n\nCompound words are formed by combining two or more individual words,\nand are particularly prevalent in Germanic languages—for example, \"firefighter\".\nWith decompounding, the individual components are indexed separately.\n\nYou can specify different lists for different languages.\nDecompounding is supported for these languages:\nDutch (`nl`), German (`de`), Finnish (`fi`), Danish (`da`), Swedish (`sv`), and Norwegian (`no`).\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": {},
-            "x-categories": [
-              "Languages"
-            ]
+            "x-categories": ["Languages"]
           },
           "indexLanguages": {
             "type": "array",
             "items": {
               "$ref": "#/components/schemas/supportedLanguage"
             },
-            "example": [
-              "ja"
-            ],
-            "description": "Languages for language-specific processing steps, such as word detection and dictionary settings.\n\n**You should always specify an indexing 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": ["ja"],
+            "description": "Languages for language-specific processing steps, such as word detection and dictionary settings.\n\n**You should always specify an indexing 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"]
           },
           "disablePrefixOnAttributes": {
             "type": "array",
             "items": {
               "type": "string"
             },
-            "example": [
-              "sku"
-            ],
+            "example": ["sku"],
             "description": "Searchable attributes for which you want to turn off [prefix matching](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/override-search-engine-defaults/#adjusting-prefix-search).\nAttribute names are case-sensitive.\n",
             "default": [],
-            "x-categories": [
-              "Query strategy"
-            ]
+            "x-categories": ["Query strategy"]
           },
           "allowCompressionOfIntegerArray": {
             "type": "boolean",
             "description": "Whether arrays with exclusively non-negative integers should be compressed for better performance.\nIf true, the compressed arrays may be reordered.\n",
             "default": false,
-            "x-categories": [
-              "Performance"
-            ]
+            "x-categories": ["Performance"]
           },
           "numericAttributesForFiltering": {
             "type": "array",
@@ -1528,46 +1336,32 @@
               "type": "string"
             },
             "description": "Numeric attributes that can be used as [numerical filters](https://www.algolia.com/doc/guides/managing-results/rules/detecting-intent/how-to/applying-a-custom-filter-for-a-specific-query/#numerical-filters).\nAttribute names are case-sensitive.\n\nBy default, all numeric attributes are available as numerical filters.\nFor faster indexing, reduce the number of numeric attributes.\n\nTo turn off filtering for all numeric attributes, specify an attribute that doesn't exist in your index, such as `NO_NUMERIC_FILTERING`.\n\n**Modifier**\n\n- `equalOnly(\"ATTRIBUTE\")`.\n  Support only filtering based on equality comparisons `=` and `!=`.\n",
-            "example": [
-              "equalOnly(quantity)",
-              "popularity"
-            ],
+            "example": ["equalOnly(quantity)", "popularity"],
             "default": [],
-            "x-categories": [
-              "Performance"
-            ]
+            "x-categories": ["Performance"]
           },
           "separatorsToIndex": {
             "type": "string",
             "example": "+#",
             "description": "Control which non-alphanumeric characters are indexed.\n\nBy default, Algolia ignores [non-alphanumeric characters](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/typo-tolerance/how-to/how-to-search-in-hyphenated-attributes/#handling-non-alphanumeric-characters) like hyphen (`-`), plus (`+`), and parentheses (`(`,`)`).\nTo include such characters, define them with `separatorsToIndex`.\n\nSeparators are all non-letter characters except spaces and currency characters, such as $€£¥.\n\nWith `separatorsToIndex`, Algolia treats separator characters as separate words.\nFor example, in a search for \"Disney+\", Algolia considers \"Disney\" and \"+\" as two separate words.\n",
             "default": "",
-            "x-categories": [
-              "Typos"
-            ]
+            "x-categories": ["Typos"]
           },
           "searchableAttributes": {
             "type": "array",
             "items": {
               "type": "string"
             },
-            "example": [
-              "title,alternative_title",
-              "author",
-              "unordered(text)",
-              "emails.personal"
-            ],
-            "description": "Attributes used for searching. Attribute names are case-sensitive.\n\nBy default, all attributes are searchable and the [Attribute](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute) ranking criterion is turned off.\nWith a non-empty list, Algolia only returns results with matches in the selected attributes.\nIn addition, the Attribute ranking criterion is turned on: matches in attributes that are higher in the list of `searchableAttributes` rank first.\nTo make matches in two attributes rank equally, include them in a comma-separated string, such as `\"title,alternate_title\"`.\nAttributes with the same priority are always unordered.\n\nFor more information, see [Searchable attributes](https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/how-to/setting-searchable-attributes/).\n\n**Modifier**\n\n- `unordered(\"ATTRIBUTE\")`.\n  Ignore the position of a match within the attribute.\n\nWithout a modifier, matches at the beginning of an attribute rank higher than matches at the end.\n",
+            "example": ["title,alternative_title", "author", "unordered(text)", "emails.personal"],
+            "description": "Attributes used for searching. Attribute names are case-sensitive.\n\nBy default, all attributes are searchable and the [Attribute](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/#attribute) ranking criterion is turned off.\nWith a non-empty list, Algolia only returns results with matches in the selected attributes.\nIn addition, the Attribute ranking criterion is turned on: matches in attributes that are higher in the list of `searchableAttributes` rank first.\nTo make matches in two attributes rank equally, include them in a comma-separated string, such as `\"title,alternate_title\"`.\nAttributes with the same priority are always unordered.\n\nFor more information, see [Searchable attributes](https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/how-to/setting-searchable-attributes).\n\n**Modifier**\n\n- `unordered(\"ATTRIBUTE\")`.\n  Ignore the position of a match within the attribute.\n\nWithout a modifier, matches at the beginning of an attribute rank higher than matches at the end.\n",
             "default": [],
-            "x-categories": [
-              "Attributes"
-            ]
+            "x-categories": ["Attributes"]
           },
           "userData": {
             "$ref": "#/components/schemas/userData"
           },
           "customNormalization": {
-            "description": "Characters and their normalized replacements.\nThis overrides Algolia's default [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization/).\n",
+            "description": "Characters and their normalized replacements.\nThis overrides Algolia's default [normalization](https://www.algolia.com/doc/guides/managing-results/optimize-search-results/handling-natural-languages-nlp/in-depth/normalization).\n",
             "type": "object",
             "example": {
               "default": {
@@ -1581,9 +1375,7 @@
                 "type": "string"
               }
             },
-            "x-categories": [
-              "Languages"
-            ]
+            "x-categories": ["Languages"]
           },
           "attributeForDistinct": {
             "description": "Attribute that should be used to establish groups of results.\nAttribute names are case-sensitive.\n\nAll records with the same value for this attribute are considered a group.\nYou can combine `attributeForDistinct` with the `distinct` search parameter to control\nhow many items per group are included in the search results.\n\nIf you want to use the same attribute also for faceting, use the `afterDistinct` modifier of the `attributesForFaceting` setting.\nThis applies faceting _after_ deduplication, which will result in accurate facet counts.\n",
@@ -1598,24 +1390,17 @@
             "example": "øé",
             "description": "Characters for which diacritics should be preserved.\n\nBy default, Algolia removes diacritics from letters.\nFor example, `é` becomes `e`. If this causes issues in your search,\nyou can specify characters that should keep their diacritics.\n",
             "default": "",
-            "x-categories": [
-              "Languages"
-            ]
+            "x-categories": ["Languages"]
           },
           "customRanking": {
             "type": "array",
             "items": {
               "type": "string"
             },
-            "example": [
-              "desc(popularity)",
-              "asc(price)"
-            ],
-            "description": "Attributes to use as [custom ranking](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/).\nAttribute names are case-sensitive.\n\nThe custom ranking attributes decide which items are shown first if the other ranking criteria are equal.\n\nRecords with missing values for your selected custom ranking attributes are always sorted last.\nBoolean attributes are sorted based on their alphabetical order.\n\n**Modifiers**\n\n- `asc(\"ATTRIBUTE\")`.\n  Sort the index by the values of an attribute, in ascending order.\n\n- `desc(\"ATTRIBUTE\")`.\n  Sort the index by the values of an attribute, in descending order.\n\nIf you use two or more custom ranking attributes,\n[reduce the precision](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/how-to/controlling-custom-ranking-metrics-precision/) of your first attributes,\nor the other attributes will never be applied.\n",
+            "example": ["desc(popularity)", "asc(price)"],
+            "description": "Attributes to use as [custom ranking](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking).\nAttribute names are case-sensitive.\n\nThe custom ranking attributes decide which items are shown first if the other ranking criteria are equal.\n\nRecords with missing values for your selected custom ranking attributes are always sorted last.\nBoolean attributes are sorted based on their alphabetical order.\n\n**Modifiers**\n\n- `asc(\"ATTRIBUTE\")`.\n  Sort the index by the values of an attribute, in ascending order.\n\n- `desc(\"ATTRIBUTE\")`.\n  Sort the index by the values of an attribute, in descending order.\n\nIf you use two or more custom ranking attributes,\n[reduce the precision](https://www.algolia.com/doc/guides/managing-results/must-do/custom-ranking/how-to/controlling-custom-ranking-metrics-precision) of your first attributes,\nor the other attributes will never be applied.\n",
             "default": [],
-            "x-categories": [
-              "Ranking"
-            ]
+            "x-categories": ["Ranking"]
           }
         }
       },
@@ -1624,140 +1409,90 @@
         "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"]
       },
       "ranking": {
         "type": "array",
         "items": {
           "type": "string"
         },
-        "description": "Determines the order in which Algolia returns your results.\n\nBy default, each entry corresponds to a [ranking criteria](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria/).\nThe tie-breaking algorithm sequentially applies each criterion in the order they're specified.\nIf you configure a replica index for [sorting by an attribute](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/how-to/sort-by-attribute/),\nyou put the sorting attribute at the top of the list.\n\n**Modifiers**\n\n- `asc(\"ATTRIBUTE\")`.\n  Sort the index by the values of an attribute, in ascending order.\n- `desc(\"ATTRIBUTE\")`.\n  Sort the index by the values of an attribute, in descending order.\n\nBefore you modify the default setting,\nyou should test your changes in the dashboard,\nand by [A/B testing](https://www.algolia.com/doc/guides/ab-testing/what-is-ab-testing/).\n",
-        "default": [
-          "typo",
-          "geo",
-          "words",
-          "filters",
-          "proximity",
-          "attribute",
-          "exact",
-          "custom"
-        ],
-        "x-categories": [
-          "Ranking"
-        ]
+        "description": "Determines the order in which Algolia returns your results.\n\nBy default, each entry corresponds to a [ranking criteria](https://www.algolia.com/doc/guides/managing-results/relevance-overview/in-depth/ranking-criteria).\nThe tie-breaking algorithm sequentially applies each criterion in the order they're specified.\nIf you configure a replica index for [sorting by an attribute](https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/how-to/sort-by-attribute),\nyou put the sorting attribute at the top of the list.\n\n**Modifiers**\n\n- `asc(\"ATTRIBUTE\")`.\n  Sort the index by the values of an attribute, in ascending order.\n- `desc(\"ATTRIBUTE\")`.\n  Sort the index by the values of an attribute, in descending order.\n\nBefore you modify the default setting,\nyou should test your changes in the dashboard,\nand by [A/B testing](https://www.algolia.com/doc/guides/ab-testing/what-is-ab-testing).\n",
+        "default": ["typo", "geo", "words", "filters", "proximity", "attribute", "exact", "custom"],
+        "x-categories": ["Ranking"]
       },
       "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"]
       },
       "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"]
       },
       "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"]
       },
       "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"]
       },
       "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"]
       },
       "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"]
       },
       "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"]
       },
       "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"]
       },
       "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",
@@ -1768,45 +1503,31 @@
             "$ref": "#/components/schemas/typoToleranceEnum"
           }
         ],
-        "x-categories": [
-          "Typos"
-        ]
+        "x-categories": ["Typos"]
       },
       "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"]
       },
       "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"]
       },
       "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",
@@ -1824,16 +1545,11 @@
             "default": false
           }
         ],
-        "x-categories": [
-          "Languages"
-        ]
+        "x-categories": ["Languages"]
       },
       "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",
@@ -1848,98 +1564,66 @@
             "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"]
       },
       "queryLanguages": {
         "type": "array",
         "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"]
       },
       "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"]
       },
       "enableRules": {
         "type": "boolean",
         "description": "Whether to enable rules.",
         "default": true,
-        "x-categories": [
-          "Rules"
-        ]
+        "x-categories": ["Rules"]
       },
       "enablePersonalization": {
         "type": "boolean",
         "description": "Whether to enable Personalization.",
         "default": false,
-        "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"]
       },
       "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"]
       },
       "advancedSyntax": {
         "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"]
       },
       "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",
@@ -1960,39 +1644,22 @@
         "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"]
       },
       "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"]
       },
       "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",
@@ -2000,23 +1667,13 @@
           "$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"]
       },
       "advancedSyntaxFeatures": {
         "type": "string",
-        "enum": [
-          "exactPhrase",
-          "excludeWords"
-        ],
-        "x-categories": [
-          "Query strategy"
-        ]
+        "enum": ["exactPhrase", "excludeWords"],
+        "x-categories": ["Query strategy"]
       },
       "IndexSettings_advancedSyntaxFeatures": {
         "type": "array",
@@ -2024,13 +1681,8 @@
           "$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"]
       },
       "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",
@@ -2042,23 +1694,19 @@
           },
           {
             "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"]
       },
       "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"]
       },
       "minProximity": {
         "type": "integer",
@@ -2066,9 +1714,7 @@
         "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"]
       },
       "responseFields": {
         "type": "array",
@@ -2076,37 +1722,27 @@
           "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"]
       },
       "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"]
       },
       "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"]
       },
       "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",
@@ -2128,11 +1764,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.",
@@ -2268,20 +1900,16 @@
             "$ref": "#/components/schemas/widgets"
           }
         },
-        "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"]
       },
       "reRankingApplyFilter": {
-        "description": "Restrict [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking/) to records that match these filters.\n",
+        "description": "Restrict [Dynamic Re-Ranking](https://www.algolia.com/doc/guides/algolia-ai/re-ranking) to records that match these filters.\n",
         "oneOf": [
           {
             "type": "array",
@@ -2291,9 +1919,7 @@
           },
           {
             "type": "string",
-            "x-categories": [
-              "Filtering"
-            ]
+            "x-categories": ["Filtering"]
           }
         ]
       },
@@ -2478,17 +2104,12 @@
             "$ref": "#/components/schemas/recommendSearchParams"
           }
         },
-        "required": [
-          "indexName",
-          "threshold"
-        ]
+        "required": ["indexName", "threshold"]
       },
       "fbtModel": {
         "type": "string",
         "description": "Frequently bought together model.\n\nThis model recommends items that have been purchased within 1 day with the item with the ID `objectID`.\n",
-        "enum": [
-          "bought-together"
-        ]
+        "enum": ["bought-together"]
       },
       "objectID": {
         "type": "string",
@@ -2505,10 +2126,7 @@
             "$ref": "#/components/schemas/objectID"
           }
         },
-        "required": [
-          "model",
-          "objectID"
-        ]
+        "required": ["model", "objectID"]
       },
       "boughtTogetherQuery": {
         "title": "Frequently bought together",
@@ -2524,9 +2142,7 @@
       "relatedModel": {
         "type": "string",
         "description": "Related products or similar content model.\n\nThis model recommends items that are similar to the item with the ID `objectID`.\nSimilarity is determined from the user interactions and attributes.\n",
-        "enum": [
-          "related-products"
-        ]
+        "enum": ["related-products"]
       },
       "fallbackParams": {
         "title": "fallbackParameters",
@@ -2553,10 +2169,7 @@
             "$ref": "#/components/schemas/fallbackParams"
           }
         },
-        "required": [
-          "model",
-          "objectID"
-        ]
+        "required": ["model", "objectID"]
       },
       "relatedQuery": {
         "title": "Related products",
@@ -2580,9 +2193,7 @@
       "trendingItemsModel": {
         "description": "Trending items model.\n\nTrending items are determined from the number of conversion events collected on them.\n",
         "type": "string",
-        "enum": [
-          "trending-items"
-        ]
+        "enum": ["trending-items"]
       },
       "trendingItems": {
         "type": "object",
@@ -2600,9 +2211,7 @@
             "$ref": "#/components/schemas/fallbackParams"
           }
         },
-        "required": [
-          "model"
-        ]
+        "required": ["model"]
       },
       "trendingItemsQuery": {
         "title": "Trending items",
@@ -2618,9 +2227,7 @@
       "trendingFacetsModel": {
         "type": "string",
         "description": "Trending facet values model.\n\nThis model recommends trending facet values for the specified facet attribute.\n",
-        "enum": [
-          "trending-facets"
-        ]
+        "enum": ["trending-facets"]
       },
       "trendingFacets": {
         "type": "object",
@@ -2636,10 +2243,7 @@
             "$ref": "#/components/schemas/fallbackParams"
           }
         },
-        "required": [
-          "facetName",
-          "model"
-        ]
+        "required": ["facetName", "model"]
       },
       "trendingFacetsQuery": {
         "title": "Trending facet values",
@@ -2655,9 +2259,7 @@
       "lookingSimilarModel": {
         "type": "string",
         "description": "Looking similar model.\n\nThis model recommends items that look similar to the item with the ID `objectID` based on image attributes in your index.\n",
-        "enum": [
-          "looking-similar"
-        ]
+        "enum": ["looking-similar"]
       },
       "lookingSimilar": {
         "type": "object",
@@ -2672,10 +2274,7 @@
             "$ref": "#/components/schemas/fallbackParams"
           }
         },
-        "required": [
-          "model",
-          "objectID"
-        ]
+        "required": ["model", "objectID"]
       },
       "lookingSimilarQuery": {
         "title": "Looking similar",
@@ -2735,9 +2334,7 @@
             "title": "redirectRuleIndexData",
             "type": "object",
             "description": "Redirect rule data.",
-            "required": [
-              "ruleObjectID"
-            ],
+            "required": ["ruleObjectID"],
             "properties": {
               "ruleObjectID": {
                 "type": "string"
@@ -2745,13 +2342,7 @@
             }
           }
         },
-        "required": [
-          "data",
-          "succeed",
-          "reason",
-          "dest",
-          "source"
-        ]
+        "required": ["data", "succeed", "reason", "dest", "source"]
       },
       "baseSearchResponse": {
         "type": "object",
@@ -2918,7 +2509,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",
@@ -2946,7 +2537,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": {
@@ -2960,9 +2551,7 @@
         "description": "Page of search results to retrieve.",
         "default": 0,
         "minimum": 0,
-        "x-categories": [
-          "Pagination"
-        ]
+        "x-categories": ["Pagination"]
       },
       "nbHits": {
         "type": "integer",
@@ -2980,9 +2569,7 @@
         "default": 20,
         "minimum": 1,
         "maximum": 1000,
-        "x-categories": [
-          "Pagination"
-        ]
+        "x-categories": ["Pagination"]
       },
       "SearchPagination": {
         "type": "object",
@@ -3010,11 +2597,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",
@@ -3031,9 +2614,7 @@
           "matchedWords": {
             "type": "array",
             "description": "List of matched words from the search query.",
-            "example": [
-              "action"
-            ],
+            "example": ["action"],
             "items": {
               "type": "string"
             }
@@ -3043,15 +2624,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",
@@ -3097,13 +2671,8 @@
             "$ref": "#/components/schemas/matchLevel"
           }
         },
-        "required": [
-          "value",
-          "matchLevel"
-        ],
-        "x-discriminator-fields": [
-          "matchLevel"
-        ]
+        "required": ["value", "matchLevel"],
+        "x-discriminator-fields": ["matchLevel"]
       },
       "snippetResultMap": {
         "title": "snippetResultMap",
@@ -3236,13 +2805,7 @@
             "description": "Whether the record is re-ranked."
           }
         },
-        "required": [
-          "nbTypos",
-          "firstMatchedWord",
-          "geoDistance",
-          "nbExactWords",
-          "userScore"
-        ]
+        "required": ["nbTypos", "firstMatchedWord", "geoDistance", "nbExactWords", "userScore"]
       },
       "distinctSeqID": {
         "type": "integer"
@@ -3258,9 +2821,7 @@
         "type": "object",
         "description": "Recommend hit.",
         "additionalProperties": true,
-        "required": [
-          "objectID"
-        ],
+        "required": ["objectID"],
         "properties": {
           "objectID": {
             "$ref": "#/components/schemas/objectID"
@@ -3281,17 +2842,12 @@
             "$ref": "#/components/schemas/recommendScore"
           }
         },
-        "x-discriminator-fields": [
-          "objectID"
-        ]
+        "x-discriminator-fields": ["objectID"]
       },
       "trendingFacetHit": {
         "type": "object",
         "description": "Trending facet hit.",
-        "required": [
-          "facetName",
-          "facetValue"
-        ],
+        "required": ["facetName", "facetValue"],
         "properties": {
           "_score": {
             "$ref": "#/components/schemas/recommendScore"
@@ -3303,10 +2859,7 @@
             "$ref": "#/components/schemas/facetValue"
           }
         },
-        "x-discriminator-fields": [
-          "facetName",
-          "facetValue"
-        ]
+        "x-discriminator-fields": ["facetName", "facetValue"]
       },
       "recommendationsHit": {
         "oneOf": [
@@ -3329,9 +2882,7 @@
             }
           }
         },
-        "required": [
-          "hits"
-        ]
+        "required": ["hits"]
       },
       "recommendationsResults": {
         "allOf": [
@@ -3348,12 +2899,7 @@
       },
       "recommendModels": {
         "type": "string",
-        "enum": [
-          "related-products",
-          "bought-together",
-          "trending-facets",
-          "trending-items"
-        ]
+        "enum": ["related-products", "bought-together", "trending-facets", "trending-items"]
       },
       "updatedAt": {
         "type": "string",
@@ -3456,10 +3002,7 @@
             "items": {
               "type": "string"
             },
-            "example": [
-              "category:books<score=1>",
-              "category:-movies<score=1>"
-            ]
+            "example": ["category:books<score=1>", "category:-movies<score=1>"]
           }
         }
       },
@@ -3541,7 +3084,7 @@
         "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"
       },
       "deletedAt": {
         "type": "string",
@@ -3550,10 +3093,7 @@
       },
       "taskStatus": {
         "type": "string",
-        "enum": [
-          "published",
-          "notPublished"
-        ],
+        "enum": ["published", "notPublished"],
         "description": "Task status, `published` if the task is completed, `notPublished` otherwise."
       },
       "parameters_query": {
@@ -3564,23 +3104,20 @@
       "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"
       },
       "recommendUpdatedAtResponse": {
         "type": "object",
         "description": "Response, taskID, and update timestamp.",
         "additionalProperties": false,
-        "required": [
-          "taskID",
-          "updatedAt"
-        ],
+        "required": ["taskID", "updatedAt"],
         "properties": {
           "taskID": {
             "$ref": "#/components/schemas/taskID"
@@ -3641,10 +3178,7 @@
               "description": "Response, taskID, and deletion timestamp.",
               "additionalProperties": false,
               "type": "object",
-              "required": [
-                "taskID",
-                "deletedAt"
-              ],
+              "required": ["taskID", "deletedAt"],
               "properties": {
                 "taskID": {
                   "$ref": "#/components/schemas/taskID"
@@ -3672,10 +3206,7 @@
   "x-tagGroups": [
     {
       "name": "Recommend",
-      "tags": [
-        "recommendations",
-        "rules"
-      ]
+      "tags": ["recommendations", "rules"]
     }
   ]
-}
+}