@algolia/client-search 5.0.0-alpha.103 → 5.0.0-alpha.105

package/model/securedAPIKeyRestrictions.ts

@@ -0,0 +1,32 @@
+// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
+
+import type { SearchParamsObject } from './searchParamsObject';
+
+export type SecuredAPIKeyRestrictions = {
+  searchParams?: SearchParamsObject;
+
+  /**
+   * Filters that apply to every search made with the secured API key. You can add extra filters at search time with the filters query parameter. For example, if you set the filter group:admin on your generated API key, and you add groups:press OR groups:visitors with the filters query parameter, your final search filter is equivalent to groups:admin AND (groups:press OR groups:visitors).
+   */
+  filters?: string;
+
+  /**
+   * Unix timestamp used to set the expiration date of the API key.
+   */
+  validUntil?: number;
+
+  /**
+   * Index names that can be queried.
+   */
+  restrictIndices?: string[];
+
+  /**
+   * IPv4 network allowed to use the generated key. Use this to protect against API key leaking and reuse. You can only provide a single source, but you can specify a range of IPs (for example, 192.168.1.0/24).
+   */
+  restrictSources?: string;
+
+  /**
+   * Unique user IP address. This can be useful when you want to impose a rate limit on specific users. By default, rate limits are set based on the IP address. This can become an issue when several users search from the same IP address. To avoid this, you can set a unique userToken for each user when generating their API key. This lets you restrict each user to a maximum number of API calls per hour, even if they share their IP with another user. Specifying the userToken in a secured API key is also a good security practice as it ensures users don\'t change it. Many features like Analytics, Personalization, and Dynamic Re-ranking rely on the authenticity of user identifiers. Setting the userToken at the API key level ensures that downstream services work as expected and prevents abuse.
+   */
+  userToken?: string;
+};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@algolia/client-search",
-  "version": "5.0.0-alpha.103",
+  "version": "5.0.0-alpha.105",
   "description": "JavaScript client for client-search",
   "repository": "algolia/algoliasearch-client-javascript",
   "license": "MIT",
@@ -39,12 +39,12 @@
     "clean": "rm -rf ./dist || true"
   },
   "dependencies": {
-    "@algolia/client-common": "5.0.0-alpha.104",
-    "@algolia/requester-browser-xhr": "5.0.0-alpha.104",
-    "@algolia/requester-node-http": "5.0.0-alpha.104"
+    "@algolia/client-common": "5.0.0-alpha.106",
+    "@algolia/requester-browser-xhr": "5.0.0-alpha.106",
+    "@algolia/requester-node-http": "5.0.0-alpha.106"
   },
   "devDependencies": {
-    "@types/node": "20.11.20",
+    "@types/node": "20.11.24",
     "rollup": "4.12.0",
     "typescript": "5.3.3"
   },