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

package/lib/esm/models/VaultUserAttachmentsReportResponse.js

@@ -4,7 +4,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/esm/models/VaultUserConnectionsReport.js

@@ -4,7 +4,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/esm/models/VaultUserConnectionsReportConnectionsGrantingDelegationAccessToYourAccount.js

@@ -4,7 +4,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/esm/models/VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsers.js

@@ -4,7 +4,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/esm/models/VaultUserConnectionsReportResponse.js

@@ -4,7 +4,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/esm/models/VaultUserQueuedForDeletion.js

@@ -4,7 +4,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/esm/models/index.js

@@ -18,6 +18,8 @@ export * from './ATOMComponent';
 export * from './ATOMCreateOrUpdateOrgRequest';
 export * from './ATOMCreateOrUpdateTenantRequest';
 export * from './ATOMError';
+export * from './ATOMFileStorageBackend';
+export * from './ATOMFileStorageConfiguration';
 export * from './ATOMGenesisRequest';
 export * from './ATOMNewAgentRequest';
 export * from './ATOMOneAgent';

package/lib/esm/runtime.js

@@ -4,7 +4,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/types/apis/ClassificationsApi.d.ts

@@ -2,7 +2,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/types/apis/ConnectionsApi.d.ts

@@ -2,7 +2,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).
@@ -42,15 +42,11 @@ export interface InvitationsGetRequest {
     meecoDelegationId?: string;
     meecoOrganisationId?: string;
 }
-export interface InvitationsIdDeleteRequest {
-    id: string;
-    meecoDelegationId?: string;
-    meecoOrganisationId?: string;
-}
-export interface InvitationsIdGetRequest {
-    id: string;
+export interface InvitationsInvitationIdAcceptPostRequest {
+    invitationId: string;
     meecoDelegationId?: string;
     meecoOrganisationId?: string;
+    acceptInvitationsRequest?: AcceptInvitationsRequest;
 }
 export interface InvitationsInvitationIdCancelDeleteRequest {
     invitationId: string;
@@ -63,14 +59,18 @@ export interface InvitationsInvitationIdConfirmPostRequest {
     meecoOrganisationId?: string;
     acceptInvitationsRequest1?: AcceptInvitationsRequest1;
 }
-export interface InvitationsInvitationTokenAcceptPostRequest {
-    invitationToken: string;
+export interface InvitationsInvitationIdDeleteRequest {
+    invitationId: string;
     meecoDelegationId?: string;
     meecoOrganisationId?: string;
-    acceptInvitationsRequest?: AcceptInvitationsRequest;
 }
-export interface InvitationsInvitationTokenRejectDeleteRequest {
-    invitationToken: string;
+export interface InvitationsInvitationIdGetRequest {
+    invitationId: string;
+    meecoDelegationId?: string;
+    meecoOrganisationId?: string;
+}
+export interface InvitationsInvitationIdRejectDeleteRequest {
+    invitationId: string;
     meecoDelegationId?: string;
     meecoOrganisationId?: string;
 }
@@ -130,25 +130,15 @@ export declare class ConnectionsApi extends runtime.BaseAPI {
      */
     invitationsGet(state?: string, nextPageAfter?: string, perPage?: number, page?: number, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<InvitationsResponse>;
     /**
-     * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
-     * Delete an invitation
-     */
-    invitationsIdDeleteRaw(requestParameters: InvitationsIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
-    /**
-     * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
-     * Delete an invitation
-     */
-    invitationsIdDelete(id: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
-    /**
-     * Read an invitation by its token or ID.   Can be used by both the invitation sender, and someone with an invitation token.Fields `id` and `keypair_external_id` are NULL if the current user is not the sender of the invitation
-     * Read an invitation
+     * Accept an invitation.   This endpoint is only available if the multistep invitation flow is enabled. Accepting an endpoint does not create a connection. After an invitation is accepted, the sender of the invitation needs to confirm it.   ---  If there is already a connection between these two users, then  * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
+     * Accept an invitation
      */
-    invitationsIdGetRaw(requestParameters: InvitationsIdGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<InvitationWithShareIntentsResponse>>;
+    invitationsInvitationIdAcceptPostRaw(requestParameters: InvitationsInvitationIdAcceptPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<VaultInvitationAcceptedResponse>>;
     /**
-     * Read an invitation by its token or ID.   Can be used by both the invitation sender, and someone with an invitation token.Fields `id` and `keypair_external_id` are NULL if the current user is not the sender of the invitation
-     * Read an invitation
+     * Accept an invitation.   This endpoint is only available if the multistep invitation flow is enabled. Accepting an endpoint does not create a connection. After an invitation is accepted, the sender of the invitation needs to confirm it.   ---  If there is already a connection between these two users, then  * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
+     * Accept an invitation
      */
-    invitationsIdGet(id: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<InvitationWithShareIntentsResponse>;
+    invitationsInvitationIdAcceptPost(invitationId: string, meecoDelegationId?: string, meecoOrganisationId?: string, acceptInvitationsRequest?: AcceptInvitationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<VaultInvitationAcceptedResponse>;
     /**
      * Reject an accepted invitation.  This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an  an invitation is accepted, and then the sender of the invitation can reject it using this endpoint. Only the sender of the invitation can call this endpoint.
      * Reject an accepted invitation
@@ -170,25 +160,35 @@ export declare class ConnectionsApi extends runtime.BaseAPI {
      */
     invitationsInvitationIdConfirmPost(invitationId: string, meecoDelegationId?: string, meecoOrganisationId?: string, acceptInvitationsRequest1?: AcceptInvitationsRequest1, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<VaultInvitationAcceptedResponse>;
     /**
-     * Accept an invitation.   This endpoint is only available if the multistep invitation flow is enabled. Accepting an endpoint does not create a connection. After an invitation is accepted, the sender of the invitation needs to confirm it.   ---  If there is already a connection between these two users, then  * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
-     * Accept an invitation
+     * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
+     * Delete an invitation
      */
-    invitationsInvitationTokenAcceptPostRaw(requestParameters: InvitationsInvitationTokenAcceptPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<VaultInvitationAcceptedResponse>>;
+    invitationsInvitationIdDeleteRaw(requestParameters: InvitationsInvitationIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
     /**
-     * Accept an invitation.   This endpoint is only available if the multistep invitation flow is enabled. Accepting an endpoint does not create a connection. After an invitation is accepted, the sender of the invitation needs to confirm it.   ---  If there is already a connection between these two users, then  * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
-     * Accept an invitation
+     * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
+     * Delete an invitation
+     */
+    invitationsInvitationIdDelete(invitationId: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
+    /**
+     * Read an invitation by its token or ID.   Can be used by both the invitation sender, and someone with an invitation token.Fields `id` and `keypair_external_id` are NULL if the current user is not the sender of the invitation
+     * Read an invitation
+     */
+    invitationsInvitationIdGetRaw(requestParameters: InvitationsInvitationIdGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<InvitationWithShareIntentsResponse>>;
+    /**
+     * Read an invitation by its token or ID.   Can be used by both the invitation sender, and someone with an invitation token.Fields `id` and `keypair_external_id` are NULL if the current user is not the sender of the invitation
+     * Read an invitation
      */
-    invitationsInvitationTokenAcceptPost(invitationToken: string, meecoDelegationId?: string, meecoOrganisationId?: string, acceptInvitationsRequest?: AcceptInvitationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<VaultInvitationAcceptedResponse>;
+    invitationsInvitationIdGet(invitationId: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<InvitationWithShareIntentsResponse>;
     /**
      * Reject an invitation. This endpoint is only available if the multistep invitation flow is enabled.
      * Reject an invitation
      */
-    invitationsInvitationTokenRejectDeleteRaw(requestParameters: InvitationsInvitationTokenRejectDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<InvitationRejectedResponse>>;
+    invitationsInvitationIdRejectDeleteRaw(requestParameters: InvitationsInvitationIdRejectDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<InvitationRejectedResponse>>;
     /**
      * Reject an invitation. This endpoint is only available if the multistep invitation flow is enabled.
      * Reject an invitation
      */
-    invitationsInvitationTokenRejectDelete(invitationToken: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<InvitationRejectedResponse>;
+    invitationsInvitationIdRejectDelete(invitationId: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<InvitationRejectedResponse>;
     /**
      * Invite another user to connect.  An invitation does not specify a recipient directly, instead the result of this operation is  an invitation token which can then be sent to a recipient by a client application or some other means, mand the recipient can create a connection using this token and endpoint `POST /connections` --- Invitations and connections have 3 special use-cases: 1. a connection between an organization agent and an organization member 2. a connection between a service agent and a user of the service 3. a connection between a user and a delegate user who has been granted permissions to act on behalf of the user  Blindly accepting an invitation by submitting an invitation token to `POST /connections` might have serious consequences, so client applications are advised to first read the invitation with `GET /invitations/{token}`before creating a connection. The intent of an invitation is in JSON field `integration_data`.  --- For the membership invitation parameter `organization_member_role` is used to specify the role we are inviting the user with. There are currently 2 organization member roles: * `owner` - can do everything * `admin` (default) - can only manage organization services If param `organization_member_role` is not provided then role `admin` will be assigned to the invited member. --- For the delegation connection parameters `delegate_role` and `delegation_token` are mandatory. `delegation_token` should be obtained by running `POST /delegations` in the keystore.   If `delegate_role` and `delegation_token` are present, a recipient is invited to become a delegate user who has rights to perform actions on behalf of the user who has created the invitation.  Currently there are three delegate roles: * `owner` * `admin` * `reader` --- The vault supports two invitations workflows:  * Simple - a sender creates an invitation. A recipient then accepts the invitation, and a connection is created.  * Multistep - a sender creates an invitation. A recipient then accepts the invitation, no connection is created yet. The recipient then confirms the invitation, and a connection is created.  An invitation is marked as belonging to one of these two workflows when created, boolean parameter `multistep_workflow` can be used for this. Values \'1\' and \'true\' are interpreted as true, as multistep invitation workflow.  Each vault instance is configured to have a default invitation workflow. In case `multistep_workflow` is not submitted or is `null`, the default workflow is used.
      * Create an invitation

package/lib/types/apis/DIDsApi.d.ts

@@ -2,7 +2,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/types/apis/DelegationsApi.d.ts

@@ -2,7 +2,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/types/apis/EventsApi.d.ts

@@ -2,7 +2,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/types/apis/HelpersApi.d.ts

@@ -2,7 +2,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).
@@ -24,6 +24,7 @@ export interface BlobsIdPutRequest {
     id: string;
 }
 export interface BlobsPostRequest {
+    storageName: string;
     aTOMBlobUploadUrlRequest: ATOMBlobUploadUrlRequest;
 }
 export interface TenantsTenantIdLogoGetRequest {
@@ -34,13 +35,13 @@ export interface TenantsTenantIdLogoGetRequest {
  */
 export declare 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: BlobsIdGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
     /**
-     *   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: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
     /**
@@ -74,15 +75,15 @@ export declare class HelpersApi extends runtime.BaseAPI {
      */
     blobsIdPut(id: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ATOMBlobInfoResponse>;
     /**
-     *   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: BlobsPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ATOMBlobInfoResponse>>;
     /**
-     *   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: ATOMBlobUploadUrlRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ATOMBlobInfoResponse>;
+    blobsPost(storageName: string, aTOMBlobUploadUrlRequest: ATOMBlobUploadUrlRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ATOMBlobInfoResponse>;
     /**
      * Redirect to the logo of a tenant.    This endpoint is public and it only requires the tenant ID in the URL.
      * Redirect to the logo of a tenant

package/lib/types/apis/ItemsApi.d.ts

@@ -2,7 +2,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).
@@ -116,18 +116,18 @@ export interface ItemsGetRequest {
     meecoDelegationId?: string;
     meecoOrganisationId?: string;
 }
-export interface ItemsIdDeleteRequest {
-    id: string;
+export interface ItemsItemIdDeleteRequest {
+    itemId: string;
     meecoDelegationId?: string;
     meecoOrganisationId?: string;
 }
-export interface ItemsIdGetRequest {
-    id: string;
+export interface ItemsItemIdGetRequest {
+    itemId: string;
     meecoDelegationId?: string;
     meecoOrganisationId?: string;
 }
-export interface ItemsIdPutRequest {
-    id: string;
+export interface ItemsItemIdPutRequest {
+    itemId: string;
     meecoDelegationId?: string;
     meecoOrganisationId?: string;
     putItemsRequest?: PutItemsRequest;
@@ -316,32 +316,32 @@ export declare 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: ItemsIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
+    itemsItemIdDeleteRaw(requestParameters: ItemsItemIdDeleteRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<void>>;
     /**
      * 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: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
+    itemsItemIdDelete(itemId: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<void>;
     /**
-     * Retrieve a specific Item by `id`.
-     * Get Item
+     * Retrieve a specific Item by `item_id`.
+     * Get item
      */
-    itemsIdGetRaw(requestParameters: ItemsIdGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<VaultItemResponse>>;
+    itemsItemIdGetRaw(requestParameters: ItemsItemIdGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<VaultItemResponse>>;
     /**
-     * Retrieve a specific Item by `id`.
-     * Get Item
+     * Retrieve a specific Item by `item_id`.
+     * Get item
      */
-    itemsIdGet(id: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<VaultItemResponse>;
+    itemsItemIdGet(itemId: string, meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<VaultItemResponse>;
     /**
-     * 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: ItemsIdPutRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<VaultItemResponse>>;
+    itemsItemIdPutRaw(requestParameters: ItemsItemIdPutRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<VaultItemResponse>>;
     /**
-     * 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: string, meecoDelegationId?: string, meecoOrganisationId?: string, putItemsRequest?: PutItemsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<VaultItemResponse>;
+    itemsItemIdPut(itemId: string, meecoDelegationId?: string, meecoOrganisationId?: string, putItemsRequest?: PutItemsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<VaultItemResponse>;
     /**
      * Create an item populated with slots. There are 3 top-level parameters:  * `item` - input data to create an item and its slots.   * `template_name`. Each item is cloned from an item template. The name of the item template must be present in this field. In addition to data copied from the item template, template slots become item slots.   * `skip_empty_template_slots`. If true, then only those template slots will be created for which incoming parameters are present. Otherwise all template slots become item slots.  The parameters in `item` are as follows:  * `label` is a human-readable name. `label` is mandatory  * `name` is a machine reference. It can be skipped, in that case `name` from the template will be used  * `description` can be skipped, in that case `description` from the template will be used  * `slots_attributes`. Parameters in `slots_attributes` can be used either to create new slots or update slots cloned from the template slots. `slots_attributes` can be empty, in this case the newly created item will only contain slots cloned from the template  * `classification_nodes_attributes`  ---  ### Matching incoming slot parameters to slots cloned from the template  There are 2 cases when slot parameters are used to update an already existing slot cloned from the template: 1. If `slot_type_id` inside parameters for a slot matches `slot_type_id` of a cloned slot, the parameters will be used to update the matched slot. 2. If `name` inside parameters for a slot matches `name` of a cloned slot, the parameters will be used to update the matched slot.  In all other cases slot parameters will be used to create a new slot.  --- ### Classifications  In this endpoint it is possible to link the item and its slots to 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`: * `id` * `name` * `scheme` * `scheme_name`  * `label` 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.  Example payload classifications:  ``` classification_nodes_attributes: [   {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"},   {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"},   {scheme: \"region\", name: \"france\"},   {scheme: \"tag\", name: \"Holiday Locations\"},   {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.  --- Here is an example of a minimalistic POST request to this endpoint:  ``` {   \"template_name\": \"template-name\",   \"item\": {     \"label\": \"new-item-label\"   } } ``` With one slot:  ``` {   \"template_name\": \"template-name\",   \"item\": {     \"label\": \"new-item-label\",       \"slots_attributes\": [         \"label\": \"a label\",         \"encrypted_value\": \"user-encrypted-value\"       ]   } } ```
      * Create an item

package/lib/types/apis/KeysApi.d.ts

@@ -2,7 +2,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/types/apis/MetricsApi.d.ts

@@ -2,7 +2,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).