@meeco/svx-api-sdk 1.0.0-stage.20240502114933.d123429 → 1.0.0-stage.20240703124311.f085df0

package/lib/umd/apis/HelpersApi.js

@@ -5,7 +5,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 1.3.5
+ * The version of the OpenAPI document: 1.3.6
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -53,8 +53,8 @@ const models_1 = require("../models");
  */
 class HelpersApi extends runtime.BaseAPI {
     /**
-     *   Redirect to a file in Azure Blob Storage.    This endpoint is public and it only requires the file key in the URL.    The `Content Disposition` header in the response is hardcoded to be `inline` for now, but it can be made a parameter to this endpoint in future if needed. The filename and the content type included in `Content Disposition` are taken from the database record created in `POST /blobs`.\"
-     * Redirect to a file in Azure Blob Storage
+     *   Redirect to a file in a cloud file storage.    This endpoint is public and it only requires the file key in the URL.    The `Content Disposition` header in the response is hardcoded to be `inline` for now, but it can be made a parameter to this endpoint in future if needed. The filename and the content type included in `Content Disposition` are taken from the database record created in `POST /blobs`.\"
+     * Redirect to a file in a cloud file storage
      */
     blobsIdGetRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -73,8 +73,8 @@ class HelpersApi extends runtime.BaseAPI {
         });
     }
     /**
-     *   Redirect to a file in Azure Blob Storage.    This endpoint is public and it only requires the file key in the URL.    The `Content Disposition` header in the response is hardcoded to be `inline` for now, but it can be made a parameter to this endpoint in future if needed. The filename and the content type included in `Content Disposition` are taken from the database record created in `POST /blobs`.\"
-     * Redirect to a file in Azure Blob Storage
+     *   Redirect to a file in a cloud file storage.    This endpoint is public and it only requires the file key in the URL.    The `Content Disposition` header in the response is hardcoded to be `inline` for now, but it can be made a parameter to this endpoint in future if needed. The filename and the content type included in `Content Disposition` are taken from the database record created in `POST /blobs`.\"
+     * Redirect to a file in a cloud file storage
      */
     blobsIdGet(id, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -186,15 +186,21 @@ class HelpersApi extends runtime.BaseAPI {
         });
     }
     /**
-     *   Create a signed upload URL. This endpoint is the first step in creating a file.    Just like most ATOM endpoints, this endpoint requires a valid user (that is, an IDP JWT) and some security rights.   The security rights are those which might require to attach files to entities like organisations, tenants, and so on.   Any of the following security rights grants a permission to create an upload URL    * `atom:global:create_tenant`   * `atom:global:create_org`   * `atom:global:create_tenant_agent`   * `atom:tenant:create_org`   * `atom:tenant:create_agent`   * `atom:org:create_agent`   * `atom:tenant:create_tenant_agent`   * `vc:tenant:manage`   * `vc:org:manage`    ATOM generates a random key under which a file will be registered, and creates a record in the database where the key is stored along with the filename and the content type. A client is then expected to use a signed URL present in response field `upload_url` to upload a file to Azure Blob Storage. This URL is only valid for a short period of time specified in response field `upload_url_expires_in_seconds`.    Uploading is done via HTTP method `PUT`. Header `x-ms-blob-type: BlockBlob` must be present in this request.    The following is an example curl command to upload a file:    ```   curl --location --request PUT \\   \'https://meecodevstorage0.blob.core.windows.net/dev/66c35456-eb64-42fb-a31a-806530786fe2?se=2023-01-23T08%3A49%3A29Z&sig=mzuonk01F8L%2F0q7avsMvvenk2NwLFVXYsyWJeu5Jdgc%3D&sp=rw&sr=b&sv=2018-11-09\' \\   --header \'x-ms-blob-type: BlockBlob\' \\   --data-binary \'@/home/john/file.jpg\'   ```    After the file is uploaded to Azure Blob Storage, the client is supposed to confirm this upload calling `PUT /blobs/{key}`.    The response to `POST /blobs` also contains a URL to retrieve the file, but that functionality is only available after the upload has been confirmed, otherwise it will result in `404 NotFound`.    All expired and not confirmed records created with this endpoint will be removed after a while.
+     *   Create a signed upload URL for one of the supported file storages. This endpoint is the first step in creating a file.    Just like most ATOM endpoints, this endpoint requires a valid user (that is, an IDP JWT) and some security rights.   The security rights are those which might require to attach files to entities like organisations, tenants, and so on.   Any of the following security rights grants a permission to create an upload URL    * `atom:global:create_tenant`   * `atom:global:create_org`   * `atom:global:create_tenant_agent`   * `atom:tenant:create_org`   * `atom:tenant:create_agent`   * `atom:org:create_agent`   * `atom:tenant:create_tenant_agent`   * `vc:tenant:manage`   * `vc:org:manage`    ATOM generates a random key under which a file will be registered, and creates a record in the database where the key is stored along with the filename and the content type. A client is then expected to use a signed URL present in response field `upload_url` to upload a file to a cloud file storage. This URL is only valid for a short period of time specified in response field `upload_url_expires_in_seconds`.    Uploading is done via HTTP method `PUT`. The response of this endpoint contains a list of headers which much be included in   the `PUT` request.    The following is an example curl command to upload a file:    ```   curl --location --request PUT \\   \'https://meecodevstorage0.blob.core.windows.net/dev/66c35456-eb64-42fb-a31a-806530786fe2?se=2023-01-23T08%3A49%3A29Z&sig=mzuonk01F8L%2F0q7avsMvvenk2NwLFVXYsyWJeu5Jdgc%3D&sp=rw&sr=b&sv=2018-11-09\' \\   --header \'x-ms-blob-type: BlockBlob\' \\   --data-binary \'@/home/john/file.jpg\'   ```    After the file is uploaded to Azure Blob Storage, the client is supposed to confirm this upload calling `PUT /blobs/{key}`.    The response to `POST /blobs` also contains a URL to retrieve the file, but that functionality is only available after the upload has been confirmed, otherwise it will result in `404 NotFound`.    All expired and not confirmed records created with this endpoint will be removed after a while.
      * Obtain a signed upload URL
      */
     blobsPostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
+            if (requestParameters.storageName === null || requestParameters.storageName === undefined) {
+                throw new runtime.RequiredError('storageName', 'Required parameter requestParameters.storageName was null or undefined when calling blobsPost.');
+            }
             if (requestParameters.aTOMBlobUploadUrlRequest === null || requestParameters.aTOMBlobUploadUrlRequest === undefined) {
                 throw new runtime.RequiredError('aTOMBlobUploadUrlRequest', 'Required parameter requestParameters.aTOMBlobUploadUrlRequest was null or undefined when calling blobsPost.');
             }
             const queryParameters = {};
+            if (requestParameters.storageName !== undefined) {
+                queryParameters['storage_name'] = requestParameters.storageName;
+            }
             const headerParameters = {};
             headerParameters['Content-Type'] = 'application/json';
             if (this.configuration && this.configuration.accessToken) {
@@ -215,12 +221,12 @@ class HelpersApi extends runtime.BaseAPI {
         });
     }
     /**
-     *   Create a signed upload URL. This endpoint is the first step in creating a file.    Just like most ATOM endpoints, this endpoint requires a valid user (that is, an IDP JWT) and some security rights.   The security rights are those which might require to attach files to entities like organisations, tenants, and so on.   Any of the following security rights grants a permission to create an upload URL    * `atom:global:create_tenant`   * `atom:global:create_org`   * `atom:global:create_tenant_agent`   * `atom:tenant:create_org`   * `atom:tenant:create_agent`   * `atom:org:create_agent`   * `atom:tenant:create_tenant_agent`   * `vc:tenant:manage`   * `vc:org:manage`    ATOM generates a random key under which a file will be registered, and creates a record in the database where the key is stored along with the filename and the content type. A client is then expected to use a signed URL present in response field `upload_url` to upload a file to Azure Blob Storage. This URL is only valid for a short period of time specified in response field `upload_url_expires_in_seconds`.    Uploading is done via HTTP method `PUT`. Header `x-ms-blob-type: BlockBlob` must be present in this request.    The following is an example curl command to upload a file:    ```   curl --location --request PUT \\   \'https://meecodevstorage0.blob.core.windows.net/dev/66c35456-eb64-42fb-a31a-806530786fe2?se=2023-01-23T08%3A49%3A29Z&sig=mzuonk01F8L%2F0q7avsMvvenk2NwLFVXYsyWJeu5Jdgc%3D&sp=rw&sr=b&sv=2018-11-09\' \\   --header \'x-ms-blob-type: BlockBlob\' \\   --data-binary \'@/home/john/file.jpg\'   ```    After the file is uploaded to Azure Blob Storage, the client is supposed to confirm this upload calling `PUT /blobs/{key}`.    The response to `POST /blobs` also contains a URL to retrieve the file, but that functionality is only available after the upload has been confirmed, otherwise it will result in `404 NotFound`.    All expired and not confirmed records created with this endpoint will be removed after a while.
+     *   Create a signed upload URL for one of the supported file storages. This endpoint is the first step in creating a file.    Just like most ATOM endpoints, this endpoint requires a valid user (that is, an IDP JWT) and some security rights.   The security rights are those which might require to attach files to entities like organisations, tenants, and so on.   Any of the following security rights grants a permission to create an upload URL    * `atom:global:create_tenant`   * `atom:global:create_org`   * `atom:global:create_tenant_agent`   * `atom:tenant:create_org`   * `atom:tenant:create_agent`   * `atom:org:create_agent`   * `atom:tenant:create_tenant_agent`   * `vc:tenant:manage`   * `vc:org:manage`    ATOM generates a random key under which a file will be registered, and creates a record in the database where the key is stored along with the filename and the content type. A client is then expected to use a signed URL present in response field `upload_url` to upload a file to a cloud file storage. This URL is only valid for a short period of time specified in response field `upload_url_expires_in_seconds`.    Uploading is done via HTTP method `PUT`. The response of this endpoint contains a list of headers which much be included in   the `PUT` request.    The following is an example curl command to upload a file:    ```   curl --location --request PUT \\   \'https://meecodevstorage0.blob.core.windows.net/dev/66c35456-eb64-42fb-a31a-806530786fe2?se=2023-01-23T08%3A49%3A29Z&sig=mzuonk01F8L%2F0q7avsMvvenk2NwLFVXYsyWJeu5Jdgc%3D&sp=rw&sr=b&sv=2018-11-09\' \\   --header \'x-ms-blob-type: BlockBlob\' \\   --data-binary \'@/home/john/file.jpg\'   ```    After the file is uploaded to Azure Blob Storage, the client is supposed to confirm this upload calling `PUT /blobs/{key}`.    The response to `POST /blobs` also contains a URL to retrieve the file, but that functionality is only available after the upload has been confirmed, otherwise it will result in `404 NotFound`.    All expired and not confirmed records created with this endpoint will be removed after a while.
      * Obtain a signed upload URL
      */
-    blobsPost(aTOMBlobUploadUrlRequest, initOverrides) {
+    blobsPost(storageName, aTOMBlobUploadUrlRequest, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.blobsPostRaw({ aTOMBlobUploadUrlRequest: aTOMBlobUploadUrlRequest }, initOverrides);
+            const response = yield this.blobsPostRaw({ storageName: storageName, aTOMBlobUploadUrlRequest: aTOMBlobUploadUrlRequest }, initOverrides);
             return yield response.value();
         });
     }

package/lib/umd/apis/ItemsApi.js

@@ -5,7 +5,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 1.3.5
+ * The version of the OpenAPI document: 1.3.6
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -834,10 +834,10 @@ class ItemsApi extends runtime.BaseAPI {
      * Delete an item.  If the item is an item shared with the current user, the corresponding share is deleted together with the item.
      * Delete an item
      */
-    itemsIdDeleteRaw(requestParameters, initOverrides) {
+    itemsItemIdDeleteRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.id === null || requestParameters.id === undefined) {
-                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdDelete.');
+            if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
+                throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdDelete.');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -855,7 +855,7 @@ class ItemsApi extends runtime.BaseAPI {
                 }
             }
             const response = yield this.request({
-                path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
+                path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
                 method: 'DELETE',
                 headers: headerParameters,
                 query: queryParameters,
@@ -867,19 +867,19 @@ class ItemsApi extends runtime.BaseAPI {
      * Delete an item.  If the item is an item shared with the current user, the corresponding share is deleted together with the item.
      * Delete an item
      */
-    itemsIdDelete(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
+    itemsItemIdDelete(itemId, meecoDelegationId, meecoOrganisationId, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            yield this.itemsIdDeleteRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
+            yield this.itemsItemIdDeleteRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
         });
     }
     /**
-     * Retrieve a specific Item by `id`.
-     * Get Item
+     * Retrieve a specific Item by `item_id`.
+     * Get item
      */
-    itemsIdGetRaw(requestParameters, initOverrides) {
+    itemsItemIdGetRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.id === null || requestParameters.id === undefined) {
-                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdGet.');
+            if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
+                throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdGet.');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -897,7 +897,7 @@ class ItemsApi extends runtime.BaseAPI {
                 }
             }
             const response = yield this.request({
-                path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
+                path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
                 method: 'GET',
                 headers: headerParameters,
                 query: queryParameters,
@@ -906,23 +906,23 @@ class ItemsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * Retrieve a specific Item by `id`.
-     * Get Item
+     * Retrieve a specific Item by `item_id`.
+     * Get item
      */
-    itemsIdGet(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
+    itemsItemIdGet(itemId, meecoDelegationId, meecoOrganisationId, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.itemsIdGetRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
+            const response = yield this.itemsItemIdGetRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
             return yield response.value();
         });
     }
     /**
-     * Update an Item specified by `id` with fields provided in the JSON body.  --- ### Classifications  In this endpoint it is possible to link the item and its slots to classification nodes, unlink the item and its slots from classification nodes, and to create classification nodes in user-owned classification schemes if they do not exist yet.  There are 2 types of classification schemes:  * owned by users - each user can create their own classification nodes * global - nodes are created by the system  There are 5 parameters for classification of slots and items in `POST /items`: * `node_id` * `node_name` * `scheme_id` * `scheme_name` * `_destroy`  Both a classification scheme and a classification node can be referred to by their name or their ID. If `id` is used, `scheme_id` and `scheme` may be omitted.  Flag `_destroy` is used to unlink a classification node from a slot or the item.  Example payload classifications:  ``` classification_nodes_attributes: [   {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"},   {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"},   {scheme: \"region\", name: \"france\", \"_destroy\": true},   {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", name: \"netherlands\"},   {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", id: \"16557bff-21fe-4bb1-8b0a-0a7847dfc7d6\"},   {scheme: \"tag\", name: \"my-own-cool-tag\"} ] ```  If node `france` is missing in scheme region, the service will return an error, because scheme `region` is a global scheme. `(owned_by_user=false)`. If node `my-own-cool-tag` is missing in scheme `tag`, it will be created, because scheme `tag` is a user owned scheme.  ---
+     * Update an item specified by `item_id` with fields provided in the JSON body.  --- ### Classifications  In this endpoint it is possible to link the item and its slots to classification nodes, unlink the item and its slots from classification nodes, and to create classification nodes in user-owned classification schemes if they do not exist yet.  There are 2 types of classification schemes:  * owned by users - each user can create their own classification nodes * global - nodes are created by the system  There are 5 parameters for classification of slots and items in `POST /items`: * `node_id` * `node_name` * `scheme_id` * `scheme_name` * `_destroy`  Both a classification scheme and a classification node can be referred to by their name or their ID. If `id` is used, `scheme_id` and `scheme` may be omitted.  Flag `_destroy` is used to unlink a classification node from a slot or the item.  Example payload classifications:  ``` classification_nodes_attributes: [   {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"},   {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"},   {scheme: \"region\", name: \"france\", \"_destroy\": true},   {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", name: \"netherlands\"},   {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", id: \"16557bff-21fe-4bb1-8b0a-0a7847dfc7d6\"},   {scheme: \"tag\", name: \"my-own-cool-tag\"} ] ```  If node `france` is missing in scheme region, the service will return an error, because scheme `region` is a global scheme. `(owned_by_user=false)`. If node `my-own-cool-tag` is missing in scheme `tag`, it will be created, because scheme `tag` is a user owned scheme.  ---
      * Update an item
      */
-    itemsIdPutRaw(requestParameters, initOverrides) {
+    itemsItemIdPutRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.id === null || requestParameters.id === undefined) {
-                throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdPut.');
+            if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
+                throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdPut.');
             }
             const queryParameters = {};
             const headerParameters = {};
@@ -941,7 +941,7 @@ class ItemsApi extends runtime.BaseAPI {
                 }
             }
             const response = yield this.request({
-                path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
+                path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
                 method: 'PUT',
                 headers: headerParameters,
                 query: queryParameters,
@@ -951,12 +951,12 @@ class ItemsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * Update an Item specified by `id` with fields provided in the JSON body.  --- ### Classifications  In this endpoint it is possible to link the item and its slots to classification nodes, unlink the item and its slots from classification nodes, and to create classification nodes in user-owned classification schemes if they do not exist yet.  There are 2 types of classification schemes:  * owned by users - each user can create their own classification nodes * global - nodes are created by the system  There are 5 parameters for classification of slots and items in `POST /items`: * `node_id` * `node_name` * `scheme_id` * `scheme_name` * `_destroy`  Both a classification scheme and a classification node can be referred to by their name or their ID. If `id` is used, `scheme_id` and `scheme` may be omitted.  Flag `_destroy` is used to unlink a classification node from a slot or the item.  Example payload classifications:  ``` classification_nodes_attributes: [   {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"},   {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"},   {scheme: \"region\", name: \"france\", \"_destroy\": true},   {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", name: \"netherlands\"},   {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", id: \"16557bff-21fe-4bb1-8b0a-0a7847dfc7d6\"},   {scheme: \"tag\", name: \"my-own-cool-tag\"} ] ```  If node `france` is missing in scheme region, the service will return an error, because scheme `region` is a global scheme. `(owned_by_user=false)`. If node `my-own-cool-tag` is missing in scheme `tag`, it will be created, because scheme `tag` is a user owned scheme.  ---
+     * Update an item specified by `item_id` with fields provided in the JSON body.  --- ### Classifications  In this endpoint it is possible to link the item and its slots to classification nodes, unlink the item and its slots from classification nodes, and to create classification nodes in user-owned classification schemes if they do not exist yet.  There are 2 types of classification schemes:  * owned by users - each user can create their own classification nodes * global - nodes are created by the system  There are 5 parameters for classification of slots and items in `POST /items`: * `node_id` * `node_name` * `scheme_id` * `scheme_name` * `_destroy`  Both a classification scheme and a classification node can be referred to by their name or their ID. If `id` is used, `scheme_id` and `scheme` may be omitted.  Flag `_destroy` is used to unlink a classification node from a slot or the item.  Example payload classifications:  ``` classification_nodes_attributes: [   {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"},   {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"},   {scheme: \"region\", name: \"france\", \"_destroy\": true},   {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", name: \"netherlands\"},   {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", id: \"16557bff-21fe-4bb1-8b0a-0a7847dfc7d6\"},   {scheme: \"tag\", name: \"my-own-cool-tag\"} ] ```  If node `france` is missing in scheme region, the service will return an error, because scheme `region` is a global scheme. `(owned_by_user=false)`. If node `my-own-cool-tag` is missing in scheme `tag`, it will be created, because scheme `tag` is a user owned scheme.  ---
      * Update an item
      */
-    itemsIdPut(id, meecoDelegationId, meecoOrganisationId, putItemsRequest, initOverrides) {
+    itemsItemIdPut(itemId, meecoDelegationId, meecoOrganisationId, putItemsRequest, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.itemsIdPutRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, putItemsRequest: putItemsRequest }, initOverrides);
+            const response = yield this.itemsItemIdPutRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, putItemsRequest: putItemsRequest }, initOverrides);
             return yield response.value();
         });
     }

package/lib/umd/apis/KeysApi.js

@@ -5,7 +5,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 1.3.5
+ * The version of the OpenAPI document: 1.3.6
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/lib/umd/apis/MetricsApi.js

@@ -5,7 +5,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 1.3.5
+ * The version of the OpenAPI document: 1.3.6
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).