@meeco/svx-api-sdk 1.0.0-develop.20251009115620.9b58090 → 1.0.0-develop.20251014160718.b02efb1

package/.openapi-generator/FILES

@@ -214,13 +214,13 @@ models/PutTasksRequest.ts
 models/ReconfigureShareParamsInner.ts
 models/ReconfigureSharesResponse.ts
 models/SchemasIdVersionSchemaJsonGet200Response.ts
+models/ShareIntentListResponse.ts
 models/ShareIntentParam.ts
 models/ShareIntentRequest.ts
 models/ShareIntentResponse.ts
 models/ShareIntentsResponse.ts
 models/SharesIncomingResponse.ts
 models/SharesOutgoingResponse.ts
-models/ShreIntentListResponse.ts
 models/UpdateDelegationsRequest.ts
 models/UtilitiesApplicationVersion.ts
 models/UtilitiesBlobInfo.ts

package/lib/esm/apis/ConnectionsApi.js

@@ -515,7 +515,7 @@ export class ConnectionsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * 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.
+     * 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 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
      */
     invitationsPostRaw(requestParameters, initOverrides) {
@@ -547,7 +547,7 @@ export class ConnectionsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * 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.
+     * 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 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
      */
     invitationsPost(meecoDelegationId, meecoOrganisationId, postInvitationsRequest, initOverrides) {

package/lib/esm/apis/SharesApi.js

@@ -21,7 +21,7 @@ var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, ge
     });
 };
 import * as runtime from '../runtime';
-import { CreateDeleteReconfigureSharesRequestToJSON, CreateDeleteReconfigureSharesServiceResponseFromJSON, GetItemSharesResponseFromJSON, ItemSharesUpdateResponseFromJSON, ListOfReconfigureShareParamsToJSON, PostItemEncryptRequestToJSON, PostItemSharesRequestToJSON, PutItemSharesRequestToJSON, ReconfigureSharesResponseFromJSON, ShareIntentRequestToJSON, ShareIntentResponseFromJSON, ShareIntentsResponseFromJSON, SharesIncomingResponseFromJSON, SharesOutgoingResponseFromJSON, ShreIntentListResponseFromJSON, VaultGetShareResponseFromJSON, VaultItemResponseFromJSON, VaultShareWithItemDataFromJSON, VaultSharesCreateResponseFromJSON, } from '../models';
+import { CreateDeleteReconfigureSharesRequestToJSON, CreateDeleteReconfigureSharesServiceResponseFromJSON, GetItemSharesResponseFromJSON, ItemSharesUpdateResponseFromJSON, ListOfReconfigureShareParamsToJSON, PostItemEncryptRequestToJSON, PostItemSharesRequestToJSON, PutItemSharesRequestToJSON, ReconfigureSharesResponseFromJSON, ShareIntentListResponseFromJSON, ShareIntentRequestToJSON, ShareIntentResponseFromJSON, ShareIntentsResponseFromJSON, SharesIncomingResponseFromJSON, SharesOutgoingResponseFromJSON, VaultGetShareResponseFromJSON, VaultItemResponseFromJSON, VaultShareWithItemDataFromJSON, VaultSharesCreateResponseFromJSON, } from '../models';
 /**
  *
  */
@@ -561,7 +561,7 @@ export class SharesApi extends runtime.BaseAPI {
                 headers: headerParameters,
                 query: queryParameters,
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => ShreIntentListResponseFromJSON(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => ShareIntentListResponseFromJSON(jsonValue));
         });
     }
     /**

package/lib/esm/models/{ShreIntentListResponse.js → ShareIntentListResponse.js}

@@ -14,19 +14,19 @@
 import { VaultCollectionReportFromJSON, VaultCollectionReportToJSON, } from './VaultCollectionReport';
 import { VaultShareIntentFromJSON, VaultShareIntentToJSON, } from './VaultShareIntent';
 /**
- * Check if a given object implements the ShreIntentListResponse interface.
+ * Check if a given object implements the ShareIntentListResponse interface.
  */
-export function instanceOfShreIntentListResponse(value) {
+export function instanceOfShareIntentListResponse(value) {
     let isInstance = true;
     isInstance = isInstance && "next_page_after" in value;
     isInstance = isInstance && "share_intents" in value;
     isInstance = isInstance && "meta" in value;
     return isInstance;
 }
-export function ShreIntentListResponseFromJSON(json) {
-    return ShreIntentListResponseFromJSONTyped(json, false);
+export function ShareIntentListResponseFromJSON(json) {
+    return ShareIntentListResponseFromJSONTyped(json, false);
 }
-export function ShreIntentListResponseFromJSONTyped(json, ignoreDiscriminator) {
+export function ShareIntentListResponseFromJSONTyped(json, ignoreDiscriminator) {
     if ((json === undefined) || (json === null)) {
         return json;
     }
@@ -36,7 +36,7 @@ export function ShreIntentListResponseFromJSONTyped(json, ignoreDiscriminator) {
         'meta': VaultCollectionReportFromJSON(json['meta']),
     };
 }
-export function ShreIntentListResponseToJSON(value) {
+export function ShareIntentListResponseToJSON(value) {
     if (value === undefined) {
         return undefined;
     }

package/lib/esm/models/UtilitiesOwDeploymentRequestOw.js

@@ -19,6 +19,7 @@ export function instanceOfUtilitiesOwDeploymentRequestOw(value) {
     isInstance = isInstance && "app_client_id" in value;
     isInstance = isInstance && "app_client_secret" in value;
     isInstance = isInstance && "org_id" in value;
+    isInstance = isInstance && "org_name" in value;
     isInstance = isInstance && "org_passphrase" in value;
     return isInstance;
 }
@@ -33,6 +34,7 @@ export function UtilitiesOwDeploymentRequestOwFromJSONTyped(json, ignoreDiscrimi
         'app_client_id': json['app_client_id'],
         'app_client_secret': json['app_client_secret'],
         'org_id': json['org_id'],
+        'org_name': json['org_name'],
         'org_passphrase': json['org_passphrase'],
     };
 }
@@ -47,6 +49,7 @@ export function UtilitiesOwDeploymentRequestOwToJSON(value) {
         'app_client_id': value.app_client_id,
         'app_client_secret': value.app_client_secret,
         'org_id': value.org_id,
+        'org_name': value.org_name,
         'org_passphrase': value.org_passphrase,
     };
 }

package/lib/esm/models/VaultInvitation.js

@@ -16,8 +16,6 @@ import { exists } from '../runtime';
  * @export
  */
 export const VaultInvitationConnectionTypeEnum = {
-    Member: 'member',
-    Service: 'service',
     Delegate: 'delegate',
     Null: 'null'
 };
@@ -41,9 +39,6 @@ export function instanceOfVaultInvitation(value) {
     isInstance = isInstance && "token" in value;
     isInstance = isInstance && "delegation_role" in value;
     isInstance = isInstance && "delegation_token" in value;
-    isInstance = isInstance && "organization_id" in value;
-    isInstance = isInstance && "organization_member_role" in value;
-    isInstance = isInstance && "service_id" in value;
     isInstance = isInstance && "sender_did" in value;
     isInstance = isInstance && "recipient_did" in value;
     isInstance = isInstance && "expire_at" in value;
@@ -74,9 +69,6 @@ export function VaultInvitationFromJSONTyped(json, ignoreDiscriminator) {
         'token': json['token'],
         'delegation_role': json['delegation_role'],
         'delegation_token': json['delegation_token'],
-        'organization_id': json['organization_id'],
-        'organization_member_role': json['organization_member_role'],
-        'service_id': json['service_id'],
         'sender_did': json['sender_did'],
         'recipient_did': json['recipient_did'],
         'expire_at': (new Date(json['expire_at'])),
@@ -108,9 +100,6 @@ export function VaultInvitationToJSON(value) {
         'token': value.token,
         'delegation_role': value.delegation_role,
         'delegation_token': value.delegation_token,
-        'organization_id': value.organization_id,
-        'organization_member_role': value.organization_member_role,
-        'service_id': value.service_id,
         'sender_did': value.sender_did,
         'recipient_did': value.recipient_did,
         'expire_at': (value.expire_at.toISOString()),

package/lib/esm/models/VaultOwnConnectionData.js

@@ -24,8 +24,6 @@ export const VaultOwnConnectionDataDelegationRoleEnum = {
  * @export
  */
 export const VaultOwnConnectionDataConnectionTypeEnum = {
-    Member: 'member',
-    Service: 'service',
     Delegate: 'delegate',
     Null: 'null'
 };
@@ -34,8 +32,7 @@ export const VaultOwnConnectionDataConnectionTypeEnum = {
  */
 export const VaultOwnConnectionDataUserTypeEnum = {
     Human: 'human',
-    OrganizationAgent: 'organization_agent',
-    ServiceAgent: 'service_agent'
+    Org: 'org'
 };
 /**
  * Check if a given object implements the VaultOwnConnectionData interface.
@@ -46,7 +43,6 @@ export function instanceOfVaultOwnConnectionData(value) {
     isInstance = isInstance && "encrypted_recipient_name" in value;
     isInstance = isInstance && "delegation_token" in value;
     isInstance = isInstance && "delegation_role" in value;
-    isInstance = isInstance && "organization_member_id" in value;
     isInstance = isInstance && "connection_type" in value;
     isInstance = isInstance && "user_id" in value;
     isInstance = isInstance && "user_type" in value;
@@ -68,7 +64,6 @@ export function VaultOwnConnectionDataFromJSONTyped(json, ignoreDiscriminator) {
         'encrypted_recipient_name': json['encrypted_recipient_name'],
         'delegation_token': json['delegation_token'],
         'delegation_role': json['delegation_role'],
-        'organization_member_id': json['organization_member_id'],
         'connection_type': json['connection_type'],
         'user_id': json['user_id'],
         'user_type': json['user_type'],
@@ -90,7 +85,6 @@ export function VaultOwnConnectionDataToJSON(value) {
         'encrypted_recipient_name': value.encrypted_recipient_name,
         'delegation_token': value.delegation_token,
         'delegation_role': value.delegation_role,
-        'organization_member_id': value.organization_member_id,
         'connection_type': value.connection_type,
         'user_id': value.user_id,
         'user_type': value.user_type,

package/lib/esm/models/VaultTheOtherConnectedUserData.js

@@ -24,8 +24,6 @@ export const VaultTheOtherConnectedUserDataDelegationRoleEnum = {
  * @export
  */
 export const VaultTheOtherConnectedUserDataConnectionTypeEnum = {
-    Member: 'member',
-    Service: 'service',
     Delegate: 'delegate',
     Null: 'null'
 };
@@ -34,8 +32,7 @@ export const VaultTheOtherConnectedUserDataConnectionTypeEnum = {
  */
 export const VaultTheOtherConnectedUserDataUserTypeEnum = {
     Human: 'human',
-    OrganizationAgent: 'organization_agent',
-    ServiceAgent: 'service_agent'
+    Org: 'org'
 };
 /**
  * Check if a given object implements the VaultTheOtherConnectedUserData interface.
@@ -45,7 +42,6 @@ export function instanceOfVaultTheOtherConnectedUserData(value) {
     isInstance = isInstance && "id" in value;
     isInstance = isInstance && "delegation_token" in value;
     isInstance = isInstance && "delegation_role" in value;
-    isInstance = isInstance && "organization_member_id" in value;
     isInstance = isInstance && "connection_type" in value;
     isInstance = isInstance && "user_id" in value;
     isInstance = isInstance && "user_type" in value;
@@ -65,7 +61,6 @@ export function VaultTheOtherConnectedUserDataFromJSONTyped(json, ignoreDiscrimi
         'id': json['id'],
         'delegation_token': json['delegation_token'],
         'delegation_role': json['delegation_role'],
-        'organization_member_id': json['organization_member_id'],
         'connection_type': json['connection_type'],
         'user_id': json['user_id'],
         'user_type': json['user_type'],
@@ -85,7 +80,6 @@ export function VaultTheOtherConnectedUserDataToJSON(value) {
         'id': value.id,
         'delegation_token': value.delegation_token,
         'delegation_role': value.delegation_role,
-        'organization_member_id': value.organization_member_id,
         'connection_type': value.connection_type,
         'user_id': value.user_id,
         'user_type': value.user_type,

package/lib/esm/models/VaultUser.js

@@ -16,8 +16,7 @@
  */
 export const VaultUserUserTypeEnum = {
     Human: 'human',
-    OrganizationAgent: 'organization_agent',
-    ServiceAgent: 'service_agent'
+    Org: 'org'
 };
 /**
  * Check if a given object implements the VaultUser interface.

package/lib/esm/models/VaultUserConnectionsReport.js

@@ -19,8 +19,6 @@ import { VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsersFr
 export function instanceOfVaultUserConnectionsReport(value) {
     let isInstance = true;
     isInstance = isInstance && "all_connections" in value;
-    isInstance = isInstance && "member_connections" in value;
-    isInstance = isInstance && "service_connections" in value;
     isInstance = isInstance && "connections_granting_delegation_access_to_your_account" in value;
     isInstance = isInstance && "connections_with_delegation_access_to_other_users" in value;
     return isInstance;
@@ -34,8 +32,6 @@ export function VaultUserConnectionsReportFromJSONTyped(json, ignoreDiscriminato
     }
     return {
         'all_connections': json['all_connections'],
-        'member_connections': json['member_connections'],
-        'service_connections': json['service_connections'],
         'connections_granting_delegation_access_to_your_account': VaultUserConnectionsReportConnectionsGrantingDelegationAccessToYourAccountFromJSON(json['connections_granting_delegation_access_to_your_account']),
         'connections_with_delegation_access_to_other_users': VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsersFromJSON(json['connections_with_delegation_access_to_other_users']),
     };
@@ -49,8 +45,6 @@ export function VaultUserConnectionsReportToJSON(value) {
     }
     return {
         'all_connections': value.all_connections,
-        'member_connections': value.member_connections,
-        'service_connections': value.service_connections,
         'connections_granting_delegation_access_to_your_account': VaultUserConnectionsReportConnectionsGrantingDelegationAccessToYourAccountToJSON(value.connections_granting_delegation_access_to_your_account),
         'connections_with_delegation_access_to_other_users': VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsersToJSON(value.connections_with_delegation_access_to_other_users),
     };

package/lib/esm/models/index.js

@@ -196,13 +196,13 @@ export * from './PutTasksRequest';
 export * from './ReconfigureShareParamsInner';
 export * from './ReconfigureSharesResponse';
 export * from './SchemasIdVersionSchemaJsonGet200Response';
+export * from './ShareIntentListResponse';
 export * from './ShareIntentParam';
 export * from './ShareIntentRequest';
 export * from './ShareIntentResponse';
 export * from './ShareIntentsResponse';
 export * from './SharesIncomingResponse';
 export * from './SharesOutgoingResponse';
-export * from './ShreIntentListResponse';
 export * from './UpdateDelegationsRequest';
 export * from './UtilitiesApplicationVersion';
 export * from './UtilitiesBlobInfo';

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

@@ -190,12 +190,12 @@ export declare class ConnectionsApi extends runtime.BaseAPI {
      */
     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.
+     * 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 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
      */
     invitationsPostRaw(requestParameters: InvitationsPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<InvitationResponse>>;
     /**
-     * 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.
+     * 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 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
      */
     invitationsPost(meecoDelegationId?: string, meecoOrganisationId?: string, postInvitationsRequest?: PostInvitationsRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<InvitationResponse>;

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

@@ -10,7 +10,7 @@
  * Do not edit the class manually.
  */
 import * as runtime from '../runtime';
-import type { CreateDeleteReconfigureSharesRequest, CreateDeleteReconfigureSharesServiceResponse, GetItemSharesResponse, ItemSharesUpdateResponse, ListOfReconfigureShareParams, PostItemEncryptRequest, PostItemSharesRequest, PutItemSharesRequest, ReconfigureSharesResponse, ShareIntentRequest, ShareIntentResponse, ShareIntentsResponse, SharesIncomingResponse, SharesOutgoingResponse, ShreIntentListResponse, VaultGetShareResponse, VaultItemResponse, VaultShareWithItemData, VaultSharesCreateResponse } from '../models';
+import type { CreateDeleteReconfigureSharesRequest, CreateDeleteReconfigureSharesServiceResponse, GetItemSharesResponse, ItemSharesUpdateResponse, ListOfReconfigureShareParams, PostItemEncryptRequest, PostItemSharesRequest, PutItemSharesRequest, ReconfigureSharesResponse, ShareIntentListResponse, ShareIntentRequest, ShareIntentResponse, ShareIntentsResponse, SharesIncomingResponse, SharesOutgoingResponse, VaultGetShareResponse, VaultItemResponse, VaultShareWithItemData, VaultSharesCreateResponse } from '../models';
 export interface IncomingSharesGetRequest {
     nextPageAfter?: string;
     perPage?: number;
@@ -226,12 +226,12 @@ export declare class SharesApi extends runtime.BaseAPI {
      * share intents the user has created
      * View share intents the user has created
      */
-    shareIntentsGetRaw(requestParameters: ShareIntentsGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ShreIntentListResponse>>;
+    shareIntentsGetRaw(requestParameters: ShareIntentsGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ShareIntentListResponse>>;
     /**
      * share intents the user has created
      * View share intents the user has created
      */
-    shareIntentsGet(meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ShreIntentListResponse>;
+    shareIntentsGet(meecoDelegationId?: string, meecoOrganisationId?: string, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ShareIntentListResponse>;
     /**
      * Delete a share intent
      * Delete a share intent

package/lib/types/models/{ShreIntentListResponse.d.ts → ShareIntentListResponse.d.ts}

@@ -14,32 +14,32 @@ import type { VaultShareIntent } from './VaultShareIntent';
 /**
  *
  * @export
- * @interface ShreIntentListResponse
+ * @interface ShareIntentListResponse
  */
-export interface ShreIntentListResponse {
+export interface ShareIntentListResponse {
     /**
      *
      * @type {string}
-     * @memberof ShreIntentListResponse
+     * @memberof ShareIntentListResponse
      */
     next_page_after: string | null;
     /**
      *
      * @type {Array<VaultShareIntent>}
-     * @memberof ShreIntentListResponse
+     * @memberof ShareIntentListResponse
      */
     share_intents: Array<VaultShareIntent>;
     /**
      *
      * @type {VaultCollectionReport}
-     * @memberof ShreIntentListResponse
+     * @memberof ShareIntentListResponse
      */
     meta: VaultCollectionReport;
 }
 /**
- * Check if a given object implements the ShreIntentListResponse interface.
+ * Check if a given object implements the ShareIntentListResponse interface.
  */
-export declare function instanceOfShreIntentListResponse(value: object): boolean;
-export declare function ShreIntentListResponseFromJSON(json: any): ShreIntentListResponse;
-export declare function ShreIntentListResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): ShreIntentListResponse;
-export declare function ShreIntentListResponseToJSON(value?: ShreIntentListResponse | null): any;
+export declare function instanceOfShareIntentListResponse(value: object): boolean;
+export declare function ShareIntentListResponseFromJSON(json: any): ShareIntentListResponse;
+export declare function ShareIntentListResponseFromJSONTyped(json: any, ignoreDiscriminator: boolean): ShareIntentListResponse;
+export declare function ShareIntentListResponseToJSON(value?: ShareIntentListResponse | null): any;

package/lib/types/models/UtilitiesOwDeploymentRequestOw.d.ts

@@ -33,6 +33,12 @@ export interface UtilitiesOwDeploymentRequestOw {
      * @memberof UtilitiesOwDeploymentRequestOw
      */
     org_id: string;
+    /**
+     * Organization name
+     * @type {string}
+     * @memberof UtilitiesOwDeploymentRequestOw
+     */
+    org_name: string;
     /**
      * Organization passphrase
      * @type {string}

package/lib/types/models/VaultInvitation.d.ts

@@ -17,8 +17,6 @@
 export interface VaultInvitation {
     /**
      * Type of the connection. Currently it can be
-     * * `member` - a connection between an organization agent and a member
-     * * `service`- a connection between a service user and a user of the service
      * * `delegate`- a connection between users where current user acts as delegate of a resource owner
      * * `NULL` - a connection between two human users
      * @type {string}
@@ -58,24 +56,6 @@ export interface VaultInvitation {
      * @memberof VaultInvitation
      */
     delegation_token: string | null;
-    /**
-     * In the invitation is a membership invitation from an organisation, this field contains the ID of the organisation
-     * @type {string}
-     * @memberof VaultInvitation
-     */
-    organization_id: string | null;
-    /**
-     * In the invitation is a membership invitation from an organisation, this field contains the membership role, it can be `admin` or `owner`
-     * @type {string}
-     * @memberof VaultInvitation
-     */
-    organization_member_role: string | null;
-    /**
-     * In the invitation is from an organisation service, this field contains the ID of the service
-     * @type {string}
-     * @memberof VaultInvitation
-     */
-    service_id: string | null;
     /**
      * Decentralized identifier of the invitation sender
      * @type {string}
@@ -171,8 +151,6 @@ export interface VaultInvitation {
  * @export
  */
 export declare const VaultInvitationConnectionTypeEnum: {
-    readonly Member: "member";
-    readonly Service: "service";
     readonly Delegate: "delegate";
     readonly Null: "null";
 };

package/lib/types/models/VaultOwnConnectionData.d.ts

@@ -42,16 +42,8 @@ export interface VaultOwnConnectionData {
      * @memberof VaultOwnConnectionData
      */
     delegation_role: VaultOwnConnectionDataDelegationRoleEnum;
-    /**
-     * In a membership connection `organization_member_id` contains an ID of an `organization_members` record
-     * @type {string}
-     * @memberof VaultOwnConnectionData
-     */
-    organization_member_id: string | null;
     /**
      * Type of the connection. Currently it can be
-     * * `member` - a connection between an organization agent and a member
-     * * `service`- a connection between a service user and a user of the service
      * * `delegate`- a connection between users where current user acts as delegate of a resource owner
      * * `NULL` - a connection between two human users
      * @type {string}
@@ -65,7 +57,7 @@ export interface VaultOwnConnectionData {
      */
     user_id: string;
     /**
-     * Type of the user. Currently can be `human`, `service_agent`, `organization_user`
+     * Type of the user. Currently can be `human`, `org`
      * @type {string}
      * @memberof VaultOwnConnectionData
      */
@@ -109,8 +101,6 @@ export type VaultOwnConnectionDataDelegationRoleEnum = typeof VaultOwnConnection
  * @export
  */
 export declare const VaultOwnConnectionDataConnectionTypeEnum: {
-    readonly Member: "member";
-    readonly Service: "service";
     readonly Delegate: "delegate";
     readonly Null: "null";
 };
@@ -120,8 +110,7 @@ export type VaultOwnConnectionDataConnectionTypeEnum = typeof VaultOwnConnection
  */
 export declare const VaultOwnConnectionDataUserTypeEnum: {
     readonly Human: "human";
-    readonly OrganizationAgent: "organization_agent";
-    readonly ServiceAgent: "service_agent";
+    readonly Org: "org";
 };
 export type VaultOwnConnectionDataUserTypeEnum = typeof VaultOwnConnectionDataUserTypeEnum[keyof typeof VaultOwnConnectionDataUserTypeEnum];
 /**

package/lib/types/models/VaultTheOtherConnectedUserData.d.ts

@@ -36,16 +36,8 @@ export interface VaultTheOtherConnectedUserData {
      * @memberof VaultTheOtherConnectedUserData
      */
     delegation_role: VaultTheOtherConnectedUserDataDelegationRoleEnum;
-    /**
-     * In a membership connection `organization_member_id` contains an ID of an `organization_members` record
-     * @type {string}
-     * @memberof VaultTheOtherConnectedUserData
-     */
-    organization_member_id: string | null;
     /**
      * Type of the connection. Currently it can be
-     * * `member` - a connection between an organization agent and a member
-     * * `service`- a connection between a service user and a user of the service
      * * `delegate`- a connection between users where the user on the other side of a connection is a delegate of a resource owner
      * * `NULL` - a connection between two human users
      * @type {string}
@@ -59,7 +51,7 @@ export interface VaultTheOtherConnectedUserData {
      */
     user_id: string;
     /**
-     * Type of the user on the other side of the connection. Currently can be `human`, `service_agent`, `organization_user`
+     * Type of the user on the other side of the connection. Currently can be `human`, `org`
      * @type {string}
      * @memberof VaultTheOtherConnectedUserData
      */
@@ -97,8 +89,6 @@ export type VaultTheOtherConnectedUserDataDelegationRoleEnum = typeof VaultTheOt
  * @export
  */
 export declare const VaultTheOtherConnectedUserDataConnectionTypeEnum: {
-    readonly Member: "member";
-    readonly Service: "service";
     readonly Delegate: "delegate";
     readonly Null: "null";
 };
@@ -108,8 +98,7 @@ export type VaultTheOtherConnectedUserDataConnectionTypeEnum = typeof VaultTheOt
  */
 export declare const VaultTheOtherConnectedUserDataUserTypeEnum: {
     readonly Human: "human";
-    readonly OrganizationAgent: "organization_agent";
-    readonly ServiceAgent: "service_agent";
+    readonly Org: "org";
 };
 export type VaultTheOtherConnectedUserDataUserTypeEnum = typeof VaultTheOtherConnectedUserDataUserTypeEnum[keyof typeof VaultTheOtherConnectedUserDataUserTypeEnum];
 /**

package/lib/types/models/VaultUser.d.ts

@@ -82,7 +82,7 @@ export interface VaultUser {
      */
     broken_attachments_present: boolean;
     /**
-     * Type of the user currently can be `human`, `service_agent`, `organization_user`. Defaults to `human`
+     * Type of the user currently can be `human`, `org`. Defaults to `human`
      * @type {string}
      * @memberof VaultUser
      */
@@ -93,8 +93,7 @@ export interface VaultUser {
  */
 export declare const VaultUserUserTypeEnum: {
     readonly Human: "human";
-    readonly OrganizationAgent: "organization_agent";
-    readonly ServiceAgent: "service_agent";
+    readonly Org: "org";
 };
 export type VaultUserUserTypeEnum = typeof VaultUserUserTypeEnum[keyof typeof VaultUserUserTypeEnum];
 /**

package/lib/types/models/VaultUserConnectionsReport.d.ts

@@ -23,18 +23,6 @@ export interface VaultUserConnectionsReport {
      * @memberof VaultUserConnectionsReport
      */
     all_connections: number;
-    /**
-     * number of member connections
-     * @type {number}
-     * @memberof VaultUserConnectionsReport
-     */
-    member_connections: number;
-    /**
-     * number of service connections
-     * @type {number}
-     * @memberof VaultUserConnectionsReport
-     */
-    service_connections: number;
     /**
      *
      * @type {VaultUserConnectionsReportConnectionsGrantingDelegationAccessToYourAccount}

package/lib/types/models/index.d.ts

@@ -194,13 +194,13 @@ export * from './PutTasksRequest';
 export * from './ReconfigureShareParamsInner';
 export * from './ReconfigureSharesResponse';
 export * from './SchemasIdVersionSchemaJsonGet200Response';
+export * from './ShareIntentListResponse';
 export * from './ShareIntentParam';
 export * from './ShareIntentRequest';
 export * from './ShareIntentResponse';
 export * from './ShareIntentsResponse';
 export * from './SharesIncomingResponse';
 export * from './SharesOutgoingResponse';
-export * from './ShreIntentListResponse';
 export * from './UpdateDelegationsRequest';
 export * from './UtilitiesApplicationVersion';
 export * from './UtilitiesBlobInfo';

package/lib/umd/apis/ConnectionsApi.js

@@ -541,7 +541,7 @@ class ConnectionsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * 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.
+     * 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 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
      */
     invitationsPostRaw(requestParameters, initOverrides) {
@@ -573,7 +573,7 @@ class ConnectionsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * 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.
+     * 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 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
      */
     invitationsPost(meecoDelegationId, meecoOrganisationId, postInvitationsRequest, initOverrides) {

package/lib/umd/apis/SharesApi.js

@@ -587,7 +587,7 @@ class SharesApi extends runtime.BaseAPI {
                 headers: headerParameters,
                 query: queryParameters,
             }, initOverrides);
-            return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.ShreIntentListResponseFromJSON)(jsonValue));
+            return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.ShareIntentListResponseFromJSON)(jsonValue));
         });
     }
     /**

package/lib/umd/models/{ShreIntentListResponse.js → ShareIntentListResponse.js}

@@ -13,25 +13,25 @@
  * Do not edit the class manually.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.ShreIntentListResponseToJSON = exports.ShreIntentListResponseFromJSONTyped = exports.ShreIntentListResponseFromJSON = exports.instanceOfShreIntentListResponse = void 0;
+exports.ShareIntentListResponseToJSON = exports.ShareIntentListResponseFromJSONTyped = exports.ShareIntentListResponseFromJSON = exports.instanceOfShareIntentListResponse = void 0;
 const VaultCollectionReport_1 = require("./VaultCollectionReport");
 const VaultShareIntent_1 = require("./VaultShareIntent");
 /**
- * Check if a given object implements the ShreIntentListResponse interface.
+ * Check if a given object implements the ShareIntentListResponse interface.
  */
-function instanceOfShreIntentListResponse(value) {
+function instanceOfShareIntentListResponse(value) {
     let isInstance = true;
     isInstance = isInstance && "next_page_after" in value;
     isInstance = isInstance && "share_intents" in value;
     isInstance = isInstance && "meta" in value;
     return isInstance;
 }
-exports.instanceOfShreIntentListResponse = instanceOfShreIntentListResponse;
-function ShreIntentListResponseFromJSON(json) {
-    return ShreIntentListResponseFromJSONTyped(json, false);
+exports.instanceOfShareIntentListResponse = instanceOfShareIntentListResponse;
+function ShareIntentListResponseFromJSON(json) {
+    return ShareIntentListResponseFromJSONTyped(json, false);
 }
-exports.ShreIntentListResponseFromJSON = ShreIntentListResponseFromJSON;
-function ShreIntentListResponseFromJSONTyped(json, ignoreDiscriminator) {
+exports.ShareIntentListResponseFromJSON = ShareIntentListResponseFromJSON;
+function ShareIntentListResponseFromJSONTyped(json, ignoreDiscriminator) {
     if ((json === undefined) || (json === null)) {
         return json;
     }
@@ -41,8 +41,8 @@ function ShreIntentListResponseFromJSONTyped(json, ignoreDiscriminator) {
         'meta': (0, VaultCollectionReport_1.VaultCollectionReportFromJSON)(json['meta']),
     };
 }
-exports.ShreIntentListResponseFromJSONTyped = ShreIntentListResponseFromJSONTyped;
-function ShreIntentListResponseToJSON(value) {
+exports.ShareIntentListResponseFromJSONTyped = ShareIntentListResponseFromJSONTyped;
+function ShareIntentListResponseToJSON(value) {
     if (value === undefined) {
         return undefined;
     }
@@ -55,4 +55,4 @@ function ShreIntentListResponseToJSON(value) {
         'meta': (0, VaultCollectionReport_1.VaultCollectionReportToJSON)(value.meta),
     };
 }
-exports.ShreIntentListResponseToJSON = ShreIntentListResponseToJSON;
+exports.ShareIntentListResponseToJSON = ShareIntentListResponseToJSON;

package/lib/umd/models/UtilitiesOwDeploymentRequestOw.js

@@ -22,6 +22,7 @@ function instanceOfUtilitiesOwDeploymentRequestOw(value) {
     isInstance = isInstance && "app_client_id" in value;
     isInstance = isInstance && "app_client_secret" in value;
     isInstance = isInstance && "org_id" in value;
+    isInstance = isInstance && "org_name" in value;
     isInstance = isInstance && "org_passphrase" in value;
     return isInstance;
 }
@@ -38,6 +39,7 @@ function UtilitiesOwDeploymentRequestOwFromJSONTyped(json, ignoreDiscriminator)
         'app_client_id': json['app_client_id'],
         'app_client_secret': json['app_client_secret'],
         'org_id': json['org_id'],
+        'org_name': json['org_name'],
         'org_passphrase': json['org_passphrase'],
     };
 }
@@ -53,6 +55,7 @@ function UtilitiesOwDeploymentRequestOwToJSON(value) {
         'app_client_id': value.app_client_id,
         'app_client_secret': value.app_client_secret,
         'org_id': value.org_id,
+        'org_name': value.org_name,
         'org_passphrase': value.org_passphrase,
     };
 }

package/lib/umd/models/VaultInvitation.js

@@ -19,8 +19,6 @@ const runtime_1 = require("../runtime");
  * @export
  */
 exports.VaultInvitationConnectionTypeEnum = {
-    Member: 'member',
-    Service: 'service',
     Delegate: 'delegate',
     Null: 'null'
 };
@@ -44,9 +42,6 @@ function instanceOfVaultInvitation(value) {
     isInstance = isInstance && "token" in value;
     isInstance = isInstance && "delegation_role" in value;
     isInstance = isInstance && "delegation_token" in value;
-    isInstance = isInstance && "organization_id" in value;
-    isInstance = isInstance && "organization_member_role" in value;
-    isInstance = isInstance && "service_id" in value;
     isInstance = isInstance && "sender_did" in value;
     isInstance = isInstance && "recipient_did" in value;
     isInstance = isInstance && "expire_at" in value;
@@ -79,9 +74,6 @@ function VaultInvitationFromJSONTyped(json, ignoreDiscriminator) {
         'token': json['token'],
         'delegation_role': json['delegation_role'],
         'delegation_token': json['delegation_token'],
-        'organization_id': json['organization_id'],
-        'organization_member_role': json['organization_member_role'],
-        'service_id': json['service_id'],
         'sender_did': json['sender_did'],
         'recipient_did': json['recipient_did'],
         'expire_at': (new Date(json['expire_at'])),
@@ -114,9 +106,6 @@ function VaultInvitationToJSON(value) {
         'token': value.token,
         'delegation_role': value.delegation_role,
         'delegation_token': value.delegation_token,
-        'organization_id': value.organization_id,
-        'organization_member_role': value.organization_member_role,
-        'service_id': value.service_id,
         'sender_did': value.sender_did,
         'recipient_did': value.recipient_did,
         'expire_at': (value.expire_at.toISOString()),

package/lib/umd/models/VaultOwnConnectionData.js

@@ -27,8 +27,6 @@ exports.VaultOwnConnectionDataDelegationRoleEnum = {
  * @export
  */
 exports.VaultOwnConnectionDataConnectionTypeEnum = {
-    Member: 'member',
-    Service: 'service',
     Delegate: 'delegate',
     Null: 'null'
 };
@@ -37,8 +35,7 @@ exports.VaultOwnConnectionDataConnectionTypeEnum = {
  */
 exports.VaultOwnConnectionDataUserTypeEnum = {
     Human: 'human',
-    OrganizationAgent: 'organization_agent',
-    ServiceAgent: 'service_agent'
+    Org: 'org'
 };
 /**
  * Check if a given object implements the VaultOwnConnectionData interface.
@@ -49,7 +46,6 @@ function instanceOfVaultOwnConnectionData(value) {
     isInstance = isInstance && "encrypted_recipient_name" in value;
     isInstance = isInstance && "delegation_token" in value;
     isInstance = isInstance && "delegation_role" in value;
-    isInstance = isInstance && "organization_member_id" in value;
     isInstance = isInstance && "connection_type" in value;
     isInstance = isInstance && "user_id" in value;
     isInstance = isInstance && "user_type" in value;
@@ -73,7 +69,6 @@ function VaultOwnConnectionDataFromJSONTyped(json, ignoreDiscriminator) {
         'encrypted_recipient_name': json['encrypted_recipient_name'],
         'delegation_token': json['delegation_token'],
         'delegation_role': json['delegation_role'],
-        'organization_member_id': json['organization_member_id'],
         'connection_type': json['connection_type'],
         'user_id': json['user_id'],
         'user_type': json['user_type'],
@@ -96,7 +91,6 @@ function VaultOwnConnectionDataToJSON(value) {
         'encrypted_recipient_name': value.encrypted_recipient_name,
         'delegation_token': value.delegation_token,
         'delegation_role': value.delegation_role,
-        'organization_member_id': value.organization_member_id,
         'connection_type': value.connection_type,
         'user_id': value.user_id,
         'user_type': value.user_type,

package/lib/umd/models/VaultTheOtherConnectedUserData.js

@@ -27,8 +27,6 @@ exports.VaultTheOtherConnectedUserDataDelegationRoleEnum = {
  * @export
  */
 exports.VaultTheOtherConnectedUserDataConnectionTypeEnum = {
-    Member: 'member',
-    Service: 'service',
     Delegate: 'delegate',
     Null: 'null'
 };
@@ -37,8 +35,7 @@ exports.VaultTheOtherConnectedUserDataConnectionTypeEnum = {
  */
 exports.VaultTheOtherConnectedUserDataUserTypeEnum = {
     Human: 'human',
-    OrganizationAgent: 'organization_agent',
-    ServiceAgent: 'service_agent'
+    Org: 'org'
 };
 /**
  * Check if a given object implements the VaultTheOtherConnectedUserData interface.
@@ -48,7 +45,6 @@ function instanceOfVaultTheOtherConnectedUserData(value) {
     isInstance = isInstance && "id" in value;
     isInstance = isInstance && "delegation_token" in value;
     isInstance = isInstance && "delegation_role" in value;
-    isInstance = isInstance && "organization_member_id" in value;
     isInstance = isInstance && "connection_type" in value;
     isInstance = isInstance && "user_id" in value;
     isInstance = isInstance && "user_type" in value;
@@ -70,7 +66,6 @@ function VaultTheOtherConnectedUserDataFromJSONTyped(json, ignoreDiscriminator)
         'id': json['id'],
         'delegation_token': json['delegation_token'],
         'delegation_role': json['delegation_role'],
-        'organization_member_id': json['organization_member_id'],
         'connection_type': json['connection_type'],
         'user_id': json['user_id'],
         'user_type': json['user_type'],
@@ -91,7 +86,6 @@ function VaultTheOtherConnectedUserDataToJSON(value) {
         'id': value.id,
         'delegation_token': value.delegation_token,
         'delegation_role': value.delegation_role,
-        'organization_member_id': value.organization_member_id,
         'connection_type': value.connection_type,
         'user_id': value.user_id,
         'user_type': value.user_type,

package/lib/umd/models/VaultUser.js

@@ -19,8 +19,7 @@ exports.VaultUserToJSON = exports.VaultUserFromJSONTyped = exports.VaultUserFrom
  */
 exports.VaultUserUserTypeEnum = {
     Human: 'human',
-    OrganizationAgent: 'organization_agent',
-    ServiceAgent: 'service_agent'
+    Org: 'org'
 };
 /**
  * Check if a given object implements the VaultUser interface.

package/lib/umd/models/VaultUserConnectionsReport.js

@@ -22,8 +22,6 @@ const VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsers_1 =
 function instanceOfVaultUserConnectionsReport(value) {
     let isInstance = true;
     isInstance = isInstance && "all_connections" in value;
-    isInstance = isInstance && "member_connections" in value;
-    isInstance = isInstance && "service_connections" in value;
     isInstance = isInstance && "connections_granting_delegation_access_to_your_account" in value;
     isInstance = isInstance && "connections_with_delegation_access_to_other_users" in value;
     return isInstance;
@@ -39,8 +37,6 @@ function VaultUserConnectionsReportFromJSONTyped(json, ignoreDiscriminator) {
     }
     return {
         'all_connections': json['all_connections'],
-        'member_connections': json['member_connections'],
-        'service_connections': json['service_connections'],
         'connections_granting_delegation_access_to_your_account': (0, VaultUserConnectionsReportConnectionsGrantingDelegationAccessToYourAccount_1.VaultUserConnectionsReportConnectionsGrantingDelegationAccessToYourAccountFromJSON)(json['connections_granting_delegation_access_to_your_account']),
         'connections_with_delegation_access_to_other_users': (0, VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsers_1.VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsersFromJSON)(json['connections_with_delegation_access_to_other_users']),
     };
@@ -55,8 +51,6 @@ function VaultUserConnectionsReportToJSON(value) {
     }
     return {
         'all_connections': value.all_connections,
-        'member_connections': value.member_connections,
-        'service_connections': value.service_connections,
         'connections_granting_delegation_access_to_your_account': (0, VaultUserConnectionsReportConnectionsGrantingDelegationAccessToYourAccount_1.VaultUserConnectionsReportConnectionsGrantingDelegationAccessToYourAccountToJSON)(value.connections_granting_delegation_access_to_your_account),
         'connections_with_delegation_access_to_other_users': (0, VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsers_1.VaultUserConnectionsReportConnectionsWithDelegationAccessToOtherUsersToJSON)(value.connections_with_delegation_access_to_other_users),
     };

package/lib/umd/models/index.js

@@ -212,13 +212,13 @@ __exportStar(require("./PutTasksRequest"), exports);
 __exportStar(require("./ReconfigureShareParamsInner"), exports);
 __exportStar(require("./ReconfigureSharesResponse"), exports);
 __exportStar(require("./SchemasIdVersionSchemaJsonGet200Response"), exports);
+__exportStar(require("./ShareIntentListResponse"), exports);
 __exportStar(require("./ShareIntentParam"), exports);
 __exportStar(require("./ShareIntentRequest"), exports);
 __exportStar(require("./ShareIntentResponse"), exports);
 __exportStar(require("./ShareIntentsResponse"), exports);
 __exportStar(require("./SharesIncomingResponse"), exports);
 __exportStar(require("./SharesOutgoingResponse"), exports);
-__exportStar(require("./ShreIntentListResponse"), exports);
 __exportStar(require("./UpdateDelegationsRequest"), exports);
 __exportStar(require("./UtilitiesApplicationVersion"), exports);
 __exportStar(require("./UtilitiesBlobInfo"), exports);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meeco/svx-api-sdk",
-  "version": "1.0.0-develop.20251009115620.9b58090",
+  "version": "1.0.0-develop.20251014160718.b02efb1",
   "description": "Meeco SVX API SDK",
   "types": "./lib/types/index.d.ts",
   "browser": "./lib/esm/index.js",