@openfilz-sdk/typescript-ee 1.12.12 → 1.12.14

package/.openapi-generator/openfilz-api-generate-typescript-sdk.sha256

@@ -1 +1 @@
-3d7c37d216e0347ab762772ab95b827cfc76f5286d4f0c547f7d777bf3d3aeaa
+11d14465f6e792730b1b331cc6fe578786fe311a84bb51d900bfd5ea6ed97e9c

package/README.md

@@ -1,4 +1,4 @@
-## @openfilz-sdk/typescript-ee@1.12.12
+## @openfilz-sdk/typescript-ee@1.12.14
 
 This generator creates TypeScript/JavaScript client that utilizes [axios](https://github.com/axios/axios). The generated Node module can be used in the following environments:
 
@@ -36,7 +36,7 @@ navigate to the folder of your consuming project and run one of the following co
 _published:_
 
 ```
-npm install @openfilz-sdk/typescript-ee@1.12.12 --save
+npm install @openfilz-sdk/typescript-ee@1.12.14 --save
 ```
 
 _unPublished (not recommended):_

package/api/aichat-api.ts

@@ -310,7 +310,7 @@ export const AIChatApiAxiosParamCreator = function (configuration?: Configuratio
             };
         },
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -347,7 +347,7 @@ export const AIChatApiAxiosParamCreator = function (configuration?: Configuratio
             };
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -484,7 +484,7 @@ export const AIChatApiFp = function(configuration?: Configuration) {
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -497,7 +497,7 @@ export const AIChatApiFp = function(configuration?: Configuration) {
             return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -589,7 +589,7 @@ export const AIChatApiFactory = function (configuration?: Configuration, basePat
             return localVarFp.listConversations(options).then((request) => request(axios, basePath));
         },
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -599,7 +599,7 @@ export const AIChatApiFactory = function (configuration?: Configuration, basePat
             return localVarFp.proposeByKind(folderSelectionByKindRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest] 
          * @param {*} [options] Override http request option.
@@ -693,7 +693,7 @@ export class AIChatApi extends BaseAPI {
     }
 
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest] 
      * @param {*} [options] Override http request option.
@@ -704,7 +704,7 @@ export class AIChatApi extends BaseAPI {
     }
 
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest] 
      * @param {*} [options] Override http request option.

package/dist/api/aichat-api.d.ts

@@ -82,7 +82,7 @@ export declare const AIChatApiAxiosParamCreator: (configuration?: Configuration)
      */
     listConversations: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -90,7 +90,7 @@ export declare const AIChatApiAxiosParamCreator: (configuration?: Configuration)
      */
     proposeByKind: (folderSelectionByKindRequest?: FolderSelectionByKindRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -159,7 +159,7 @@ export declare const AIChatApiFp: (configuration?: Configuration) => {
      */
     listConversations(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<AiChatConversation>>>;
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -167,7 +167,7 @@ export declare const AIChatApiFp: (configuration?: Configuration) => {
      */
     proposeByKind(folderSelectionByKindRequest?: FolderSelectionByKindRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<FolderSelectionByKindResponse>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -236,7 +236,7 @@ export declare const AIChatApiFactory: (configuration?: Configuration, basePath?
      */
     listConversations(options?: RawAxiosRequestConfig): AxiosPromise<Array<AiChatConversation>>;
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -244,7 +244,7 @@ export declare const AIChatApiFactory: (configuration?: Configuration, basePath?
      */
     proposeByKind(folderSelectionByKindRequest?: FolderSelectionByKindRequest, options?: RawAxiosRequestConfig): AxiosPromise<FolderSelectionByKindResponse>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -313,7 +313,7 @@ export declare class AIChatApi extends BaseAPI {
      */
     listConversations(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<AiChatConversation[], any, {}, any>>;
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -321,7 +321,7 @@ export declare class AIChatApi extends BaseAPI {
      */
     proposeByKind(folderSelectionByKindRequest?: FolderSelectionByKindRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<FolderSelectionByKindResponse, any, {}, any>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.

package/dist/api/aichat-api.js

@@ -265,7 +265,7 @@ const AIChatApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
          * @param {*} [options] Override http request option.
@@ -297,7 +297,7 @@ const AIChatApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -450,7 +450,7 @@ const AIChatApiFp = function (configuration) {
             });
         },
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
          * @param {*} [options] Override http request option.
@@ -466,7 +466,7 @@ const AIChatApiFp = function (configuration) {
             });
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -561,7 +561,7 @@ const AIChatApiFactory = function (configuration, basePath, axios) {
             return localVarFp.listConversations(options).then((request) => request(axios, basePath));
         },
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
          * @param {*} [options] Override http request option.
@@ -571,7 +571,7 @@ const AIChatApiFactory = function (configuration, basePath, axios) {
             return localVarFp.proposeByKind(folderSelectionByKindRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -658,7 +658,7 @@ class AIChatApi extends base_1.BaseAPI {
         return (0, exports.AIChatApiFp)(this.configuration).listConversations(options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -668,7 +668,7 @@ class AIChatApi extends base_1.BaseAPI {
         return (0, exports.AIChatApiFp)(this.configuration).proposeByKind(folderSelectionByKindRequest, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.

package/dist/esm/api/aichat-api.d.ts

@@ -82,7 +82,7 @@ export declare const AIChatApiAxiosParamCreator: (configuration?: Configuration)
      */
     listConversations: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -90,7 +90,7 @@ export declare const AIChatApiAxiosParamCreator: (configuration?: Configuration)
      */
     proposeByKind: (folderSelectionByKindRequest?: FolderSelectionByKindRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -159,7 +159,7 @@ export declare const AIChatApiFp: (configuration?: Configuration) => {
      */
     listConversations(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<AiChatConversation>>>;
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -167,7 +167,7 @@ export declare const AIChatApiFp: (configuration?: Configuration) => {
      */
     proposeByKind(folderSelectionByKindRequest?: FolderSelectionByKindRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<FolderSelectionByKindResponse>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -236,7 +236,7 @@ export declare const AIChatApiFactory: (configuration?: Configuration, basePath?
      */
     listConversations(options?: RawAxiosRequestConfig): AxiosPromise<Array<AiChatConversation>>;
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -244,7 +244,7 @@ export declare const AIChatApiFactory: (configuration?: Configuration, basePath?
      */
     proposeByKind(folderSelectionByKindRequest?: FolderSelectionByKindRequest, options?: RawAxiosRequestConfig): AxiosPromise<FolderSelectionByKindResponse>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.
@@ -313,7 +313,7 @@ export declare class AIChatApi extends BaseAPI {
      */
     listConversations(options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<AiChatConversation[], any, {}, any>>;
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -321,7 +321,7 @@ export declare class AIChatApi extends BaseAPI {
      */
     proposeByKind(folderSelectionByKindRequest?: FolderSelectionByKindRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<FolderSelectionByKindResponse, any, {}, any>>;
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.

package/dist/esm/api/aichat-api.js

@@ -262,7 +262,7 @@ export const AIChatApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
          * @param {*} [options] Override http request option.
@@ -294,7 +294,7 @@ export const AIChatApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -446,7 +446,7 @@ export const AIChatApiFp = function (configuration) {
             });
         },
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
          * @param {*} [options] Override http request option.
@@ -462,7 +462,7 @@ export const AIChatApiFp = function (configuration) {
             });
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -556,7 +556,7 @@ export const AIChatApiFactory = function (configuration, basePath, axios) {
             return localVarFp.listConversations(options).then((request) => request(axios, basePath));
         },
         /**
-         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+         * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
          * @summary Organise several folders by kind of document as one plan — no model involved
          * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
          * @param {*} [options] Override http request option.
@@ -566,7 +566,7 @@ export const AIChatApiFactory = function (configuration, basePath, axios) {
             return localVarFp.proposeByKind(folderSelectionByKindRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+         * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
          * @summary Propose a reorganisation by kind of document — no model involved
          * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
          * @param {*} [options] Override http request option.
@@ -652,7 +652,7 @@ export class AIChatApi extends BaseAPI {
         return AIChatApiFp(this.configuration).listConversations(options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+     * Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
      * @summary Organise several folders by kind of document as one plan — no model involved
      * @param {FolderSelectionByKindRequest} [folderSelectionByKindRequest]
      * @param {*} [options] Override http request option.
@@ -662,7 +662,7 @@ export class AIChatApi extends BaseAPI {
         return AIChatApiFp(this.configuration).proposeByKind(folderSelectionByKindRequest, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+     * Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
      * @summary Propose a reorganisation by kind of document — no model involved
      * @param {ReorganizationByKindRequest} [reorganizationByKindRequest]
      * @param {*} [options] Override http request option.

package/dist/esm/models/folder-selection-by-kind-request.d.ts

@@ -11,4 +11,5 @@
  */
 export interface FolderSelectionByKindRequest {
     'folderIds'?: Array<string>;
+    'language'?: string;
 }

package/dist/esm/models/reorganization-by-kind-request.d.ts

@@ -11,4 +11,5 @@
  */
 export interface ReorganizationByKindRequest {
     'rootFolderId'?: string;
+    'language'?: string;
 }

package/dist/models/folder-selection-by-kind-request.d.ts

@@ -11,4 +11,5 @@
  */
 export interface FolderSelectionByKindRequest {
     'folderIds'?: Array<string>;
+    'language'?: string;
 }

package/dist/models/reorganization-by-kind-request.d.ts

@@ -11,4 +11,5 @@
  */
 export interface ReorganizationByKindRequest {
     'rootFolderId'?: string;
+    'language'?: string;
 }

package/docs/AIChatApi.md

@@ -371,7 +371,7 @@ This endpoint does not have any parameters.
 # **proposeByKind**
 > FolderSelectionByKindResponse proposeByKind()
 
-Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
+Files of the selected folders that have no kind yet are first classified by the local classifier (at most 200 per request; never a chat model), then every folder of the selection holding documents of several kinds gets one sub-folder per kind. The answer carries ONE stored plan rooted at the selection\'s common parent (a plan without an id means nothing needs splitting) and the classification counts. folderIds absent or empty = the root level; at most 20; a folder nested in another selected one is covered by it. language (optional, e.g. fr) names new folders when the existing folder names do not tell. 404 for a folder you cannot open, 403 without the CONTRIBUTOR role.
 
 ### Example
 
@@ -423,7 +423,7 @@ const { status, data } = await apiInstance.proposeByKind(
 # **proposeByKind1**
 > ReorganizationPlanView proposeByKind1()
 
-Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…), and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
+Every folder of the scope holding documents of several kinds (their insight category) gets one sub-folder per kind, named like the existing folders (Invoices / Factures…) or else in the request\'s language, and the files move there. The answer is a stored plan to review and apply; a plan without an id means nothing needs splitting.
 
 ### Example
 

package/docs/FolderSelectionByKindRequest.md

@@ -6,6 +6,7 @@
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **folderIds** | **Array<string>** |  | [optional] [default to undefined]
+**language** | **string** |  | [optional] [default to undefined]
 
 ## Example
 
@@ -14,6 +15,7 @@ import { FolderSelectionByKindRequest } from '@openfilz-sdk/typescript-ee';
 
 const instance: FolderSelectionByKindRequest = {
     folderIds,
+    language,
 };
 ```
 

package/docs/ReorganizationByKindRequest.md

@@ -6,6 +6,7 @@
 Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **rootFolderId** | **string** |  | [optional] [default to undefined]
+**language** | **string** |  | [optional] [default to undefined]
 
 ## Example
 
@@ -14,6 +15,7 @@ import { ReorganizationByKindRequest } from '@openfilz-sdk/typescript-ee';
 
 const instance: ReorganizationByKindRequest = {
     rootFolderId,
+    language,
 };
 ```
 

package/docs/TusControllerApi.md

@@ -374,6 +374,7 @@ void (empty response body)
 |-------------|-------------|------------------|
 |**200** | Upload info returned |  * Tus-Resumable - TUS protocol version <br>  * Upload-Offset - New offset after this chunk <br>  * Upload-Length - Total file size in bytes <br>  |
 |**404** | Upload not found |  -  |
+|**410** | Upload expired before it was complete - start it again |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)
 
@@ -487,6 +488,7 @@ const { status, data } = await apiInstance.uploadChunk(
 |-------------|-------------|------------------|
 |**204** | Chunk received successfully |  * Tus-Resumable - TUS protocol version <br>  * Upload-Offset - New offset after this chunk <br>  |
 |**409** | Offset mismatch - resume from HEAD request |  -  |
+|**410** | Upload expired - start it again |  -  |
 |**413** | The chunk would go past the declared Upload-Length |  -  |
 |**404** | Upload not found |  -  |
 

package/models/folder-selection-by-kind-request.ts

@@ -16,5 +16,6 @@
 
 export interface FolderSelectionByKindRequest {
     'folderIds'?: Array<string>;
+    'language'?: string;
 }
 

package/models/reorganization-by-kind-request.ts

@@ -16,5 +16,6 @@
 
 export interface ReorganizationByKindRequest {
     'rootFolderId'?: string;
+    'language'?: string;
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@openfilz-sdk/typescript-ee",
-  "version": "1.12.12",
+  "version": "1.12.14",
   "description": "OpenAPI client for @openfilz-sdk/typescript-ee",
   "author": "OpenAPI-Generator Contributors",
   "repository": {