@meeco/svx-api-sdk 1.0.0-stage.20240317174411.448e5fc → 1.0.0-stage.20240418183029.f4253a0

package/lib/umd/apis/ItemsApi.js

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

package/lib/umd/apis/KeysApi.js

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

package/lib/umd/apis/MetricsApi.js

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

package/lib/umd/apis/OrganisationsApi.js

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

package/lib/umd/apis/SecurityRightsApi.js

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

package/lib/umd/apis/SharesApi.js

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

package/lib/umd/apis/TenantsApi.js

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

package/lib/umd/apis/UsersApi.js

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

package/lib/umd/apis/VerifiableCredentialsApi.js

@@ -5,7 +5,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 1.3.3
+ * The version of the OpenAPI document: 1.3.5
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -517,7 +517,7 @@ class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <p>Verify a VC/SDVC JWT</p><p><b>Checks performed:</b><ul><li> VC/SDVC <code>format</code> </li><li> VC/SDVC <code>signature</code>. </li><li> VC/SDVC <code>expiration</code> date is validated when the <code>expirationDate</code> attribute is present. </li><li> VC/SDVC <code>issued at</code> date is validated when the <code>iat</code> attribute is present. </li><li> The SDVC <code>keyBindingJWT</code> check is optional and is only performed if it is included in the SDJWT along with disclosures.</li><li> When <code>keyBindingJWT</code> is included in the SDJWT, the <code>kb_audience</code> and <code>kb_nonce</code> must be included in the verification options.</li><li> The SDVC also support URL instead of DID as issuer. URL will be used to construct .well-known endpoint to retrieve the public key.</li><li> Verifiable credential <code>schema</code> </li><li> Verifiable credential <code>revocation</code> list status and its validity</li></ul></p><p>Credential expiration, schema and revocation status related checks are not considered critical and will be returned under <code>warnings</code> attribute. It is up for the client application to decide how these should be handled. All other failed checks will be served under <code>errors</code> attribute.</p><p><b>Verification options</b><br /> <br />You can optionally specify checks for the provided <code>VC/SDVC JWT</code>. If specified, only these checks will run. <br />By default, <code>format</code>, <code>signature</code>, <code>expiration</code> checks are mandatory and can not be taken out from checks list. <br/> No further checks will be performed if <code>JWT Token Format</code> is invalid.</p><pre><code>{ <br />  \"credential\": { ... }, <br />  \"options\": { <br />      \"checks\": [\"format\", \"signature\", \"expiration\", \"schema\", \"revocation_status\"], <br />      \"kb_audience\": \"verifier DID or URL\", <br />      \"kb_nounce\": \"nonce\", <br />  }, <br />} <br /></code></pre><p></p>
+     * <p>Verify a VC/SDVC JWT</p><p><b>Checks performed:</b><ul><li> VC/SDVC <code>format</code> </li><li> VC/SDVC <code>signature</code>. </li><li> VC/SDVC <code>expiration</code> date is validated when the <code>expirationDate</code> attribute is present. </li><li> VC/SDVC <code>issued at</code> date is validated when the <code>iat</code> attribute is present. </li><li> The SDVC <code>keyBindingJWT</code> check is optional and is only performed if it is included in the SDJWT along with disclosures.</li><li> When <code>keyBindingJWT</code> is included in the SDJWT, the <code>kb_audience</code> and <code>kb_nonce</code> must be included in the verification options.</li><li> The SDVC also support URL instead of DID as issuer. URL will be used to construct .well-known endpoint to retrieve the public key.</li><li> Verifiable credential <code>schema</code> </li><li> Verifiable credential <code>revocation</code> list status and its validity</li></ul></p><p>Credential expiration, schema and revocation status related checks are not considered critical and will be returned under <code>warnings</code> attribute. It is up for the client application to decide how these should be handled. All other failed checks will be served under <code>errors</code> attribute.</p><p><b>Verification options</b><br /> <br />You can optionally specify checks for the provided <code>VC/SDVC JWT</code>. If specified, only these checks will run. <br />By default, <code>format</code>, <code>signature</code>, <code>expiration</code> checks are mandatory and can not be taken out from checks list. <br/> No further checks will be performed if <code>JWT Token Format</code> is invalid.</p><pre><code>{ <br />  \"credential\": { ... }, <br />  \"options\": { <br />      \"checks\": [\"format\", \"signature\", \"expiration\", \"schema\", \"revocation_status\"], <br />      \"kb_audience\": \"verifier DID or URL\", <br />      \"kb_nounce\": \"nonce\", <br />  }, <br />} <br /></code></pre><p><code>failed_to_verify_jwt</code> error might appear in both: errors and warnings list. <br />In case of SD JWT VC it wraps any error that <code>@meeco/sd-jwt-vc</code> might throw. <br />In case of JWT VC it wraps any error that <code>did-jwt-vc</code> might throw. <br />So far, the only case when <code>failed_to_verify_jwt</code> appears in the warnings list is when credential is expired.</p>
      * Verify a VC/SDVC JWT
      */
     credentialsVerifyPostRaw(requestParameters, initOverrides) {
@@ -549,7 +549,7 @@ class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <p>Verify a VC/SDVC JWT</p><p><b>Checks performed:</b><ul><li> VC/SDVC <code>format</code> </li><li> VC/SDVC <code>signature</code>. </li><li> VC/SDVC <code>expiration</code> date is validated when the <code>expirationDate</code> attribute is present. </li><li> VC/SDVC <code>issued at</code> date is validated when the <code>iat</code> attribute is present. </li><li> The SDVC <code>keyBindingJWT</code> check is optional and is only performed if it is included in the SDJWT along with disclosures.</li><li> When <code>keyBindingJWT</code> is included in the SDJWT, the <code>kb_audience</code> and <code>kb_nonce</code> must be included in the verification options.</li><li> The SDVC also support URL instead of DID as issuer. URL will be used to construct .well-known endpoint to retrieve the public key.</li><li> Verifiable credential <code>schema</code> </li><li> Verifiable credential <code>revocation</code> list status and its validity</li></ul></p><p>Credential expiration, schema and revocation status related checks are not considered critical and will be returned under <code>warnings</code> attribute. It is up for the client application to decide how these should be handled. All other failed checks will be served under <code>errors</code> attribute.</p><p><b>Verification options</b><br /> <br />You can optionally specify checks for the provided <code>VC/SDVC JWT</code>. If specified, only these checks will run. <br />By default, <code>format</code>, <code>signature</code>, <code>expiration</code> checks are mandatory and can not be taken out from checks list. <br/> No further checks will be performed if <code>JWT Token Format</code> is invalid.</p><pre><code>{ <br />  \"credential\": { ... }, <br />  \"options\": { <br />      \"checks\": [\"format\", \"signature\", \"expiration\", \"schema\", \"revocation_status\"], <br />      \"kb_audience\": \"verifier DID or URL\", <br />      \"kb_nounce\": \"nonce\", <br />  }, <br />} <br /></code></pre><p></p>
+     * <p>Verify a VC/SDVC JWT</p><p><b>Checks performed:</b><ul><li> VC/SDVC <code>format</code> </li><li> VC/SDVC <code>signature</code>. </li><li> VC/SDVC <code>expiration</code> date is validated when the <code>expirationDate</code> attribute is present. </li><li> VC/SDVC <code>issued at</code> date is validated when the <code>iat</code> attribute is present. </li><li> The SDVC <code>keyBindingJWT</code> check is optional and is only performed if it is included in the SDJWT along with disclosures.</li><li> When <code>keyBindingJWT</code> is included in the SDJWT, the <code>kb_audience</code> and <code>kb_nonce</code> must be included in the verification options.</li><li> The SDVC also support URL instead of DID as issuer. URL will be used to construct .well-known endpoint to retrieve the public key.</li><li> Verifiable credential <code>schema</code> </li><li> Verifiable credential <code>revocation</code> list status and its validity</li></ul></p><p>Credential expiration, schema and revocation status related checks are not considered critical and will be returned under <code>warnings</code> attribute. It is up for the client application to decide how these should be handled. All other failed checks will be served under <code>errors</code> attribute.</p><p><b>Verification options</b><br /> <br />You can optionally specify checks for the provided <code>VC/SDVC JWT</code>. If specified, only these checks will run. <br />By default, <code>format</code>, <code>signature</code>, <code>expiration</code> checks are mandatory and can not be taken out from checks list. <br/> No further checks will be performed if <code>JWT Token Format</code> is invalid.</p><pre><code>{ <br />  \"credential\": { ... }, <br />  \"options\": { <br />      \"checks\": [\"format\", \"signature\", \"expiration\", \"schema\", \"revocation_status\"], <br />      \"kb_audience\": \"verifier DID or URL\", <br />      \"kb_nounce\": \"nonce\", <br />  }, <br />} <br /></code></pre><p><code>failed_to_verify_jwt</code> error might appear in both: errors and warnings list. <br />In case of SD JWT VC it wraps any error that <code>@meeco/sd-jwt-vc</code> might throw. <br />In case of JWT VC it wraps any error that <code>did-jwt-vc</code> might throw. <br />So far, the only case when <code>failed_to_verify_jwt</code> appears in the warnings list is when credential is expired.</p>
      * Verify a VC/SDVC JWT
      */
     credentialsVerifyPost(vCVerifySignedCredentialRequestPayloadDto, meecoOrganisationID, initOverrides) {

package/lib/umd/apis/VerifiablePresentationsApi.js

@@ -5,7 +5,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 1.3.3
+ * The version of the OpenAPI document: 1.3.5
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -531,7 +531,7 @@ class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <p>Verify a Presentation Request</p><p><b>Checks performed:</b><ul><li>Presentation Request signature</li><li>Presentation Request format and required attributes</li><li>Presentation Request expiration if present</li></ul></p>
+     * <p>Verify a Presentation Request</p><p><b>Checks performed:</b><ul><li>Presentation Request signature</li><li>Presentation Request format and required attributes</li><li>Presentation Request expiration if present</li></ul></p><p><code>failed_to_verify_jwt</code> error might appear in both: errors and warnings list. <br />So far, the only case when <code>failed_to_verify_jwt</code> appears in the warnings list is when request is expired. <br /></p>
      * Verify a verifiable Presentation Request
      */
     oidcPresentationsRequestsVerifyPostRaw(requestParameters, initOverrides) {
@@ -560,7 +560,7 @@ class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <p>Verify a Presentation Request</p><p><b>Checks performed:</b><ul><li>Presentation Request signature</li><li>Presentation Request format and required attributes</li><li>Presentation Request expiration if present</li></ul></p>
+     * <p>Verify a Presentation Request</p><p><b>Checks performed:</b><ul><li>Presentation Request signature</li><li>Presentation Request format and required attributes</li><li>Presentation Request expiration if present</li></ul></p><p><code>failed_to_verify_jwt</code> error might appear in both: errors and warnings list. <br />So far, the only case when <code>failed_to_verify_jwt</code> appears in the warnings list is when request is expired. <br /></p>
      * Verify a verifiable Presentation Request
      */
     oidcPresentationsRequestsVerifyPost(vCVerifyPresentationRequestPayloadDto, initOverrides) {
@@ -570,7 +570,7 @@ class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a Presentation Request Submission</p><p><b>Checks performed:</b><ul><li>Presentation Request Submission Presentation Request</li><li>Presentation Request Submission Id Token</li><li>Presentation Request Submission VP Token</li><li>Signature for all of the above</li><li>Format for all of the above</li><li>Expiration for all of the above</li><li>Revocation status for credentials within vp token</li><li>Presentation_definition uri match credential schema uri within vp token</li></ul></p><p><b>Verification options</b></p><p>Certain set of checks is executed against each presentation request response attribute separately. Depending on the use-case some of those checks might not be necessary and could be disabled. To see the list of available check options - look at the schema of the verification options. If verification options were not provided all available checks will be executed. </p><p>Imagine expiration of the verifiable presentation is not relevant to our use-case. We can skip that check so no errors or wranings related to it would appear. Here is verification options payload example:</p><pre><code>{ <br />  \"presentation_request_response\": { ... }, <br />  \"options\": { <br />    \"vp_token\": { <br />      \"checks\": [\"format\", \"signature\", \"nonce\"], <br />    } <br />  }, <br />} <br /></code></pre><p>However, <b>some of the checks are mandatory</b>. If checks list includes <b>format</b> or <b>signature</b> option - it cannnot be taken out. Every other check is optional.</p>
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a Presentation Request Submission</p><p><b>Checks performed:</b><ul><li>Presentation Request Submission Presentation Request</li><li>Presentation Request Submission Id Token</li><li>Presentation Request Submission VP Token</li><li>Signature for all of the above</li><li>Format for all of the above</li><li>Expiration for all of the above</li><li>Revocation status for credentials within vp token</li><li>Presentation_definition uri match credential schema uri within vp token</li></ul></p><p><b>Verification options</b></p><p>Certain set of checks is executed against each presentation request response attribute separately. Depending on the use-case some of those checks might not be necessary and could be disabled. To see the list of available check options - look at the schema of the verification options. If verification options were not provided all available checks will be executed. </p><p>Imagine expiration of the verifiable presentation is not relevant to our use-case. We can skip that check so no errors or wranings related to it would appear. Here is verification options payload example:</p><pre><code>{ <br />  \"presentation_request_response\": { ... }, <br />  \"options\": { <br />    \"vp_token\": { <br />      \"checks\": [\"format\", \"signature\", \"nonce\"], <br />    } <br />  }, <br />} <br /></code></pre><p>However, <b>some of the checks are mandatory</b>. If checks list includes <b>format</b> or <b>signature</b> option - it cannnot be taken out. Every other check is optional.</p><p>In case of <code>id_token</code>, <code>failed_to_verify_jwt</code> error might appear in both: errors and warnings list. <br />So far, the only case when <code>failed_to_verify_jwt</code> appears in the warnings list is when <code>id_token</code> is expired. <br /></p>
      * Verify a Presentation Request Submission
      */
     oidcPresentationsResponseVerifyPostRaw(requestParameters, initOverrides) {
@@ -602,7 +602,7 @@ class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a Presentation Request Submission</p><p><b>Checks performed:</b><ul><li>Presentation Request Submission Presentation Request</li><li>Presentation Request Submission Id Token</li><li>Presentation Request Submission VP Token</li><li>Signature for all of the above</li><li>Format for all of the above</li><li>Expiration for all of the above</li><li>Revocation status for credentials within vp token</li><li>Presentation_definition uri match credential schema uri within vp token</li></ul></p><p><b>Verification options</b></p><p>Certain set of checks is executed against each presentation request response attribute separately. Depending on the use-case some of those checks might not be necessary and could be disabled. To see the list of available check options - look at the schema of the verification options. If verification options were not provided all available checks will be executed. </p><p>Imagine expiration of the verifiable presentation is not relevant to our use-case. We can skip that check so no errors or wranings related to it would appear. Here is verification options payload example:</p><pre><code>{ <br />  \"presentation_request_response\": { ... }, <br />  \"options\": { <br />    \"vp_token\": { <br />      \"checks\": [\"format\", \"signature\", \"nonce\"], <br />    } <br />  }, <br />} <br /></code></pre><p>However, <b>some of the checks are mandatory</b>. If checks list includes <b>format</b> or <b>signature</b> option - it cannnot be taken out. Every other check is optional.</p>
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a Presentation Request Submission</p><p><b>Checks performed:</b><ul><li>Presentation Request Submission Presentation Request</li><li>Presentation Request Submission Id Token</li><li>Presentation Request Submission VP Token</li><li>Signature for all of the above</li><li>Format for all of the above</li><li>Expiration for all of the above</li><li>Revocation status for credentials within vp token</li><li>Presentation_definition uri match credential schema uri within vp token</li></ul></p><p><b>Verification options</b></p><p>Certain set of checks is executed against each presentation request response attribute separately. Depending on the use-case some of those checks might not be necessary and could be disabled. To see the list of available check options - look at the schema of the verification options. If verification options were not provided all available checks will be executed. </p><p>Imagine expiration of the verifiable presentation is not relevant to our use-case. We can skip that check so no errors or wranings related to it would appear. Here is verification options payload example:</p><pre><code>{ <br />  \"presentation_request_response\": { ... }, <br />  \"options\": { <br />    \"vp_token\": { <br />      \"checks\": [\"format\", \"signature\", \"nonce\"], <br />    } <br />  }, <br />} <br /></code></pre><p>However, <b>some of the checks are mandatory</b>. If checks list includes <b>format</b> or <b>signature</b> option - it cannnot be taken out. Every other check is optional.</p><p>In case of <code>id_token</code>, <code>failed_to_verify_jwt</code> error might appear in both: errors and warnings list. <br />So far, the only case when <code>failed_to_verify_jwt</code> appears in the warnings list is when <code>id_token</code> is expired. <br /></p>
      * Verify a Presentation Request Submission
      */
     oidcPresentationsResponseVerifyPost(vCVerifyPresentationRequestResponsePayloadDto, meecoOrganisationID, initOverrides) {
@@ -875,7 +875,7 @@ class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Register Presentation Definitions for organisation<br /><p>When <code>format</code> of the Presentation Definition is set to <code>vc+sd-jwt</code>, then <code>vp_formats</code> of the Generated Presentation Request <code>registration</code> will be set to <code>sd+jwt-vc</code> with algo <code>ES256</code>, and <code>subject_syntax_types_supported</code> will be set to <code>urn:ietf:params:oauth:jwk-thumbprint</code>.</p><br />
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Register Presentation Definitions for organisation     <br />     <p>When <code>format</code> of the Presentation Definition is set to <code>vc+sd-jwt</code>, then <code>vp_formats</code> of the Generated Presentation Request <code>registration</code> will be set to</p>     <pre>     <code>      {       \"vc+sd-jwt\": {         \"sd-jwt_alg_values\": [           \"ES256\", \"EdDSA\"         ],         \"kb-jwt_alg_values\": [           \"ES256\", \"EdDSA\"         ]       }     }     </code>     </pre>     <p>and <code>subject_syntax_types_supported</code> will be set to <code>urn:ietf:params:oauth:jwk-thumbprint</code>.</p>     <br />
      * Create a Presentation Definition
      */
     presentationDefinitionsPostRaw(requestParameters, initOverrides) {
@@ -910,7 +910,7 @@ class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Register Presentation Definitions for organisation<br /><p>When <code>format</code> of the Presentation Definition is set to <code>vc+sd-jwt</code>, then <code>vp_formats</code> of the Generated Presentation Request <code>registration</code> will be set to <code>sd+jwt-vc</code> with algo <code>ES256</code>, and <code>subject_syntax_types_supported</code> will be set to <code>urn:ietf:params:oauth:jwk-thumbprint</code>.</p><br />
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Register Presentation Definitions for organisation     <br />     <p>When <code>format</code> of the Presentation Definition is set to <code>vc+sd-jwt</code>, then <code>vp_formats</code> of the Generated Presentation Request <code>registration</code> will be set to</p>     <pre>     <code>      {       \"vc+sd-jwt\": {         \"sd-jwt_alg_values\": [           \"ES256\", \"EdDSA\"         ],         \"kb-jwt_alg_values\": [           \"ES256\", \"EdDSA\"         ]       }     }     </code>     </pre>     <p>and <code>subject_syntax_types_supported</code> will be set to <code>urn:ietf:params:oauth:jwk-thumbprint</code>.</p>     <br />
      * Create a Presentation Definition
      */
     presentationDefinitionsPost(meecoOrganisationID, vCCreatePresentationDefinitionPayloadDto, initOverrides) {
@@ -962,7 +962,7 @@ class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a verifiable presentation</p><p><b>Checks performed:</b><ul><li>Verifiable presentation signature</li><li>Verifiable presentation format and required attributes</li><li>Verifiable presentation expiration if present</li><li>Verifiable presentation credentials if present <em>(check <code>POST /credentials/verify</code> for more information)</em></li></ul></p><p>Presentation expiration check is not considered critical and will be returned under <code>warnings</code> attribute. It is up for the client application to decide how it should be handled. All other failed checks will be served under <code>errors</code> attribute.</p>
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a verifiable presentation</p><p><b>Checks performed:</b><ul><li>Verifiable presentation signature</li><li>Verifiable presentation format and required attributes</li><li>Verifiable presentation expiration if present</li><li>Verifiable presentation credentials if present <em>(check <code>POST /credentials/verify</code> for more information)</em></li></ul></p><p>Presentation expiration check is not considered critical and will be returned under <code>warnings</code> attribute. It is up for the client application to decide how it should be handled. All other failed checks will be served under <code>errors</code> attribute.</p><p><code>failed_to_verify_jwt</code> error might appear in both: errors and warnings list. <br />So far, the only case when <code>failed_to_verify_jwt</code> appears in the warnings list is when presentation is expired. <br /></p>
      * Verify a verifiable presentation
      */
     presentationsVerifyPostRaw(requestParameters, initOverrides) {
@@ -997,7 +997,7 @@ class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a verifiable presentation</p><p><b>Checks performed:</b><ul><li>Verifiable presentation signature</li><li>Verifiable presentation format and required attributes</li><li>Verifiable presentation expiration if present</li><li>Verifiable presentation credentials if present <em>(check <code>POST /credentials/verify</code> for more information)</em></li></ul></p><p>Presentation expiration check is not considered critical and will be returned under <code>warnings</code> attribute. It is up for the client application to decide how it should be handled. All other failed checks will be served under <code>errors</code> attribute.</p>
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a verifiable presentation</p><p><b>Checks performed:</b><ul><li>Verifiable presentation signature</li><li>Verifiable presentation format and required attributes</li><li>Verifiable presentation expiration if present</li><li>Verifiable presentation credentials if present <em>(check <code>POST /credentials/verify</code> for more information)</em></li></ul></p><p>Presentation expiration check is not considered critical and will be returned under <code>warnings</code> attribute. It is up for the client application to decide how it should be handled. All other failed checks will be served under <code>errors</code> attribute.</p><p><code>failed_to_verify_jwt</code> error might appear in both: errors and warnings list. <br />So far, the only case when <code>failed_to_verify_jwt</code> appears in the warnings list is when presentation is expired. <br /></p>
      * Verify a verifiable presentation
      */
     presentationsVerifyPost(meecoOrganisationID, vCVerifySignedPresentationRequestPayloadDto, initOverrides) {

package/lib/umd/models/ATOMActiveAndArchivedOrgList.js

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

package/lib/umd/models/ATOMAdmin.js

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

package/lib/umd/models/ATOMAdministeredArchivedOrg.js

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

package/lib/umd/models/ATOMAdministeredOrg.js

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

package/lib/umd/models/ATOMAgentList.js

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

package/lib/umd/models/ATOMAgentToken.js

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

package/lib/umd/models/ATOMApplicationVersion.js

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

package/lib/umd/models/ATOMAssignSecurityRightsRequest.js

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

package/lib/umd/models/ATOMAuthorizationResponse.js

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

package/lib/umd/models/ATOMBlobInfo.js

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

package/lib/umd/models/ATOMBlobInfoResponse.js

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

package/lib/umd/models/ATOMBlobPublicInfo.js

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

package/lib/umd/models/ATOMBlobPublicInfoResponse.js

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

package/lib/umd/models/ATOMBlobUploadUrlRequest.js

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

package/lib/umd/models/ATOMComponent.js

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

package/lib/umd/models/ATOMCreateOrUpdateOrgRequest.js

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

package/lib/umd/models/ATOMCreateOrUpdateTenantRequest.js

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

package/lib/umd/models/ATOMError.js

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

package/lib/umd/models/ATOMGenesisRequest.js

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

package/lib/umd/models/ATOMNewAgentRequest.js

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

package/lib/umd/models/ATOMOneAgent.js

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

package/lib/umd/models/ATOMOneOrg.js

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

package/lib/umd/models/ATOMOneTenant.js

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

package/lib/umd/models/ATOMOneUser.js

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

package/lib/umd/models/ATOMOrg.js

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

package/lib/umd/models/ATOMOrgAgent.js

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

package/lib/umd/models/ATOMOrgDescription.js

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

package/lib/umd/models/ATOMOrgList.js

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

package/lib/umd/models/ATOMPaginatedAdminList.js

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

package/lib/umd/models/ATOMPaginatedOrgList.js

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

package/lib/umd/models/ATOMPaginatedTenantList.js

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

package/lib/umd/models/ATOMPublicKey.js

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

package/lib/umd/models/ATOMRebuildableProjectors.js

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

package/lib/umd/models/ATOMRedeemInvitationRequest.js

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

package/lib/umd/models/ATOMSecurityRightGroupSpec.js

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

package/lib/umd/models/ATOMSecurityRightInRegistry.js

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