@meeco/svx-api-sdk 1.0.0-stage.20241122171806.f5ccdca → 1.0.0-stage.20250304125747.40d9c59

package/lib/esm/apis/VerifiableCredentialsApi.js

@@ -4,7 +4,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 2.0.0
+ * The version of the OpenAPI document: 2.1.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -307,7 +307,7 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><hr /><p>Generates unsigned verifiable credential token in JWT format. Client is expected to sign it with a private key.</p><hr /><p>An example of how credential signing in Javascript:</p><pre><code>import { Ed25519 } from \'@meeco/sdk\'; <br />import { EdDSASigner, hexToBytes } from \'did-jwt\'; <br /><br />const key = new Ed25519(hexToBytes(SEED_HEX)); <br />const signerFn = EdDSASigner(key.getSecretKey()); <br /><br />const signature = await signerFn(unsignedJwt); <br />const vcJwt = [unsignedJwt, signature].join(\'.\');</code></pre><hr /><br /><h4>Issuer property caveat</h4><p>We use <b>openapi-generator</b> to generate Typescript SDK for the given API swagger definition. However, <b>openapi-generator</b> does not support <b>oneOf</b> configuration properly and generates an invalid Typescript SDK. To avoid the problem, swagger defines <b>issuer</b> property only as string for the moment. While in fact, endpoint accepts issuer as an object in format of <code>{id: string; name: string;}</code> as well.</p><br /><h4>Type property caveat</h4><p> <code>Type</code> is required for <code>vc+sd-jwt</code> format and must be a string <br /> however, endpoint accepts <code>Type</code> as an Array of string for <code>JWT VC</code> in format of <code>[\"VerifiableCredential\", \"AlumniCredential\"]</code> as well. <br /></p>
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><hr /><p>Generates unsigned verifiable credential token in JWT format. Client is expected to sign it with a private key.</p><hr /><p>An example of credential signing in Javascript:</p><pre><code>import { Ed25519 } from \'@meeco/sdk\'; <br />import { EdDSASigner, hexToBytes } from \'did-jwt\'; <br /><br />const key = new Ed25519(hexToBytes(SEED_HEX)); <br />const signerFn = EdDSASigner(key.getSecretKey()); <br /><br />const signature = await signerFn(unsignedJwt); <br />const vcJwt = [unsignedJwt, signature].join(\'.\');</code></pre><hr /><br /><h4>Issuer property caveat</h4><p>We use <b>openapi-generator</b> to generate Typescript SDK for the given API swagger definition. However, <b>openapi-generator</b> does not support <b>oneOf</b> configuration properly and generates an invalid Typescript SDK. To avoid the problem, swagger defines <b>issuer</b> property only as string for the moment. While in fact, endpoint accepts issuer as an object in format of <code>{id: string; name: string;}</code> as well.</p><br /><h4>Type property caveat</h4><p><code>type</code> is required for <code>vc+sd-jwt</code> format and must be a string.<br />However, endpoint accepts <code>type</code> as an array of string for <code>JWT VC</code> in format of <code>[\"VerifiableCredential\", \"AlumniCredential\"]</code> as well. <br /></p>
      * Generate credential based on type and claims provided
      */
     credentialsGeneratePostRaw(requestParameters, initOverrides) {
@@ -342,7 +342,7 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><hr /><p>Generates unsigned verifiable credential token in JWT format. Client is expected to sign it with a private key.</p><hr /><p>An example of how credential signing in Javascript:</p><pre><code>import { Ed25519 } from \'@meeco/sdk\'; <br />import { EdDSASigner, hexToBytes } from \'did-jwt\'; <br /><br />const key = new Ed25519(hexToBytes(SEED_HEX)); <br />const signerFn = EdDSASigner(key.getSecretKey()); <br /><br />const signature = await signerFn(unsignedJwt); <br />const vcJwt = [unsignedJwt, signature].join(\'.\');</code></pre><hr /><br /><h4>Issuer property caveat</h4><p>We use <b>openapi-generator</b> to generate Typescript SDK for the given API swagger definition. However, <b>openapi-generator</b> does not support <b>oneOf</b> configuration properly and generates an invalid Typescript SDK. To avoid the problem, swagger defines <b>issuer</b> property only as string for the moment. While in fact, endpoint accepts issuer as an object in format of <code>{id: string; name: string;}</code> as well.</p><br /><h4>Type property caveat</h4><p> <code>Type</code> is required for <code>vc+sd-jwt</code> format and must be a string <br /> however, endpoint accepts <code>Type</code> as an Array of string for <code>JWT VC</code> in format of <code>[\"VerifiableCredential\", \"AlumniCredential\"]</code> as well. <br /></p>
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><hr /><p>Generates unsigned verifiable credential token in JWT format. Client is expected to sign it with a private key.</p><hr /><p>An example of credential signing in Javascript:</p><pre><code>import { Ed25519 } from \'@meeco/sdk\'; <br />import { EdDSASigner, hexToBytes } from \'did-jwt\'; <br /><br />const key = new Ed25519(hexToBytes(SEED_HEX)); <br />const signerFn = EdDSASigner(key.getSecretKey()); <br /><br />const signature = await signerFn(unsignedJwt); <br />const vcJwt = [unsignedJwt, signature].join(\'.\');</code></pre><hr /><br /><h4>Issuer property caveat</h4><p>We use <b>openapi-generator</b> to generate Typescript SDK for the given API swagger definition. However, <b>openapi-generator</b> does not support <b>oneOf</b> configuration properly and generates an invalid Typescript SDK. To avoid the problem, swagger defines <b>issuer</b> property only as string for the moment. While in fact, endpoint accepts issuer as an object in format of <code>{id: string; name: string;}</code> as well.</p><br /><h4>Type property caveat</h4><p><code>type</code> is required for <code>vc+sd-jwt</code> format and must be a string.<br />However, endpoint accepts <code>type</code> as an array of string for <code>JWT VC</code> in format of <code>[\"VerifiableCredential\", \"AlumniCredential\"]</code> as well. <br /></p>
      * Generate credential based on type and claims provided
      */
     credentialsGeneratePost(meecoOrganisationID, vCGenerateCredentialPayloadDto, initOverrides) {
@@ -396,7 +396,7 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Lists credentials that selected organisation has issued.
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Lists credentials that selected organisation has issued.</p>
      * Get a list of credentials organisation has issued
      */
     credentialsGetRaw(requestParameters, initOverrides) {
@@ -438,7 +438,7 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Lists credentials that selected organisation has issued.
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Lists credentials that selected organisation has issued.</p>
      * Get a list of credentials organisation has issued
      */
     credentialsGet(meecoOrganisationID, order, orderBy, perPage, page, initOverrides) {
@@ -448,7 +448,7 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Fetch information about a credential organisation has issued by credential ID.
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Fetch information about a credential organisation has issued by credential ID.</p>
      * Fetch information about a credential organistaion has issued
      */
     credentialsIdGetRaw(requestParameters, initOverrides) {
@@ -481,7 +481,7 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Fetch information about a credential organisation has issued by credential ID.
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Fetch information about a credential organisation has issued by credential ID.</p>
      * Fetch information about a credential organistaion has issued
      */
     credentialsIdGet(id, meecoOrganisationID, initOverrides) {
@@ -535,8 +535,8 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <p>Verify a Verifiable Credential JWT</p><p>Current supports the following formats</p><ul><li><code>jwt_vc_json</code></li><li><code>vc+sd-jwt</code></li></ul><p><b>Checks performed:</b><ul><li> <code>format</code> </li><li> <code>signature</code>. </li><li> <code>expiration</code> date is validated when the <code>expirationDate</code> attribute is present. </li><li> <code>issued at</code> date is validated when the <code>iat</code> attribute is present. </li><li> The <code>keyBindingJWT</code> check is optional and is only performed if it is included in the <code>vc+sd-jwt</code> along with disclosures.</li><li> When <code>keyBindingJWT</code> is included in the <code>vc+sd-jwt</code>, the <code>kb_audience</code> and <code>kb_nonce</code> must be included in the verification options.</li><li> In the case of <code>vc+sd-jwt</code> if the iss is a URL. The public key will be retrieved from the .well-known endpoint according to the <a target=\"_blank\" href=\"https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-04.html\"><code>vc+sd-jwt</code> specification</a></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 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_nonce\": \"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 <code>vc+sd-jwt</code> it wraps any error that <code>@meeco/sd-jwt-vc</code> might throw. <br />In case of <code>jwt_vc_json</code> 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 Verifiable Credential (VC) JWT
+     * <p>Verify a Verifiable Credential</p><p>Current supports the following formats</p><ul><li><code>jwt_vc_json</code></li><li><code>vc+sd-jwt</code></li><li><code>mso_mdoc</code></li></ul><p>If credential.format is not provided, the credential token is assumed to be a JWT.</p><p><b>Checks performed:</b><ul><li> <code>format</code> </li><li> <code>signature</code>. </li><li> <code>expiration</code> date is validated when the <code>expirationDate</code> attribute is present. </li><li> <code>issued at</code> date is validated when the <code>iat</code> attribute is present. </li><li> The <code>keyBindingJWT</code> check is optional and is only performed if it is included in the <code>vc+sd-jwt</code> along with disclosures.</li><li> When <code>keyBindingJWT</code> is included in the <code>vc+sd-jwt</code>, the <code>kb_audience</code> and <code>kb_nonce</code> must be included in the verification options.</li><li> In the case of <code>vc+sd-jwt</code> if the iss is a URL. The public key will be retrieved from the .well-known endpoint according to the <a target=\"_blank\" href=\"https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-04.html\"><code>vc+sd-jwt</code> specification</a></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 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_nonce\": \"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 <code>vc+sd-jwt</code> it wraps any error that <code>@meeco/sd-jwt-vc</code> might throw. <br />In case of <code>jwt_vc_json</code> 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 Verifiable Credential (VC)
      */
     credentialsVerifyPostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -567,8 +567,8 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <p>Verify a Verifiable Credential JWT</p><p>Current supports the following formats</p><ul><li><code>jwt_vc_json</code></li><li><code>vc+sd-jwt</code></li></ul><p><b>Checks performed:</b><ul><li> <code>format</code> </li><li> <code>signature</code>. </li><li> <code>expiration</code> date is validated when the <code>expirationDate</code> attribute is present. </li><li> <code>issued at</code> date is validated when the <code>iat</code> attribute is present. </li><li> The <code>keyBindingJWT</code> check is optional and is only performed if it is included in the <code>vc+sd-jwt</code> along with disclosures.</li><li> When <code>keyBindingJWT</code> is included in the <code>vc+sd-jwt</code>, the <code>kb_audience</code> and <code>kb_nonce</code> must be included in the verification options.</li><li> In the case of <code>vc+sd-jwt</code> if the iss is a URL. The public key will be retrieved from the .well-known endpoint according to the <a target=\"_blank\" href=\"https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-04.html\"><code>vc+sd-jwt</code> specification</a></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 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_nonce\": \"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 <code>vc+sd-jwt</code> it wraps any error that <code>@meeco/sd-jwt-vc</code> might throw. <br />In case of <code>jwt_vc_json</code> 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 Verifiable Credential (VC) JWT
+     * <p>Verify a Verifiable Credential</p><p>Current supports the following formats</p><ul><li><code>jwt_vc_json</code></li><li><code>vc+sd-jwt</code></li><li><code>mso_mdoc</code></li></ul><p>If credential.format is not provided, the credential token is assumed to be a JWT.</p><p><b>Checks performed:</b><ul><li> <code>format</code> </li><li> <code>signature</code>. </li><li> <code>expiration</code> date is validated when the <code>expirationDate</code> attribute is present. </li><li> <code>issued at</code> date is validated when the <code>iat</code> attribute is present. </li><li> The <code>keyBindingJWT</code> check is optional and is only performed if it is included in the <code>vc+sd-jwt</code> along with disclosures.</li><li> When <code>keyBindingJWT</code> is included in the <code>vc+sd-jwt</code>, the <code>kb_audience</code> and <code>kb_nonce</code> must be included in the verification options.</li><li> In the case of <code>vc+sd-jwt</code> if the iss is a URL. The public key will be retrieved from the .well-known endpoint according to the <a target=\"_blank\" href=\"https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-04.html\"><code>vc+sd-jwt</code> specification</a></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 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_nonce\": \"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 <code>vc+sd-jwt</code> it wraps any error that <code>@meeco/sd-jwt-vc</code> might throw. <br />In case of <code>jwt_vc_json</code> 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 Verifiable Credential (VC)
      */
     credentialsVerifyPost(vCVerifySignedCredentialRequestPayloadDto, meecoOrganisationID, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -821,7 +821,7 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:tenant:manage</code></li></ul><br /><p><b>schema_json</b> property must comply with <a target=\"_blank\" href=\"https://www.w3.org/TR/vc-json-schema/\">specification<a>.</p><p>Schema validity can be checked by using one of the Web (Online) validators listed at <a target=\"_blank\" href=\"https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupBy=toolingTypes&licenses=&languages=&drafts=&toolingTypes=validator\">JSON schema specification site</a>.</p><p><b>schema_json.$id</b> attribute is not expected in the payload. API is going to assign its own internal version of it even if one is being passed.</p><hr /><p>Example (the most minimal set of attributes schema should contain):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"title\": \"EmailCredential\", <br />  \"description\": \"EmailCredential using JsonSchema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"credentialSubject\": { <br />      \"type\": \"object\", <br />      \"properties\": { <br />        \"emailAddress\": { <br />          \"type\": \"string\", <br />          \"format\": \"email\" <br />        } <br />      }, <br />      \"required\": [ <br />        \"emailAddress\" <br />      ] <br />    } <br />  } <br />} <br /></code></pre><hr /><p>Example (vc+sd-jwt credential format):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"vct\": { <br />      \"type\": \"string\" <br />    }, <br />    \"iss\": { <br />      \"type\": \"string\" <br />    }, <br />    \"cnf\": { <br />      \"type\": \"object\" <br />    }, <br />    \"email\": { <br />      \"type\": \"string\" <br />    }, <br />    \"is_over_18\": { <br />      \"type\": \"boolean\" <br />    } <br />  }, <br />  \"required\": [ <br />    \"iss\", <br />    \"vct\", <br />    \"cnf\", <br />    \"email\", <br />    \"is_over_18\" <br />  ] <br />} <br /></code></pre>
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:tenant:manage</code></li></ul><br /><p><b>schema_json</b> property must comply with <a target=\"_blank\" href=\"https://www.w3.org/TR/vc-json-schema/\">specification<a>.</p><p>Schema validity can be checked by using one of the Web (Online) validators listed at <a target=\"_blank\" href=\"https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupBy=toolingTypes&licenses=&languages=&drafts=&toolingTypes=validator\">JSON schema specification site</a>.</p><p><b>schema_json.$id</b> attribute is not expected in the payload. API is going to assign its own internal version of it even if one is being passed.</p><hr /><p>Example (the most minimal set of attributes schema should contain):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"title\": \"EmailCredential\", <br />  \"description\": \"EmailCredential using JsonSchema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"credentialSubject\": { <br />      \"type\": \"object\", <br />      \"properties\": { <br />        \"emailAddress\": { <br />          \"type\": \"string\", <br />          \"format\": \"email\" <br />        } <br />      }, <br />      \"required\": [ <br />        \"emailAddress\" <br />      ] <br />    } <br />  } <br />} <br /></code></pre><hr /><p>Example (vc+sd-jwt credential format):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"vct\": { <br />      \"type\": \"string\" <br />    }, <br />    \"iss\": { <br />      \"type\": \"string\" <br />    }, <br />    \"cnf\": { <br />      \"type\": \"object\" <br />    }, <br />    \"email\": { <br />      \"type\": \"string\" <br />    }, <br />    \"is_over_18\": { <br />      \"type\": \"boolean\" <br />    } <br />  }, <br />  \"required\": [ <br />    \"iss\", <br />    \"vct\", <br />    \"cnf\", <br />    \"email\", <br />    \"is_over_18\" <br />  ] <br />} <br /></code></pre><hr /><p>Example (mso_mdoc credential format):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"org.iso.18013.5.1\": { <br />      \"type\": \"object\" <br />      \"properties\": { <br />        \"email\": { <br />          \"type\": \"string\" <br />        }, <br />        \"portrait\": { <br />          \"type\": \"string\" <br />          \"description\": \"jpeg as base64url encoded\" <br />          \"x-cbor-encoding\": \"bstr\" <br />        }, <br />      } <br />    }, <br />  }, <br />  \"required\": [ <br />    \"email\", <br />    \"portrait\" <br />  ] <br />} <br /></code></pre>
      * Create schema
      */
     schemasPostRaw(requestParameters, initOverrides) {
@@ -850,7 +850,7 @@ export class VerifiableCredentialsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:tenant:manage</code></li></ul><br /><p><b>schema_json</b> property must comply with <a target=\"_blank\" href=\"https://www.w3.org/TR/vc-json-schema/\">specification<a>.</p><p>Schema validity can be checked by using one of the Web (Online) validators listed at <a target=\"_blank\" href=\"https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupBy=toolingTypes&licenses=&languages=&drafts=&toolingTypes=validator\">JSON schema specification site</a>.</p><p><b>schema_json.$id</b> attribute is not expected in the payload. API is going to assign its own internal version of it even if one is being passed.</p><hr /><p>Example (the most minimal set of attributes schema should contain):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"title\": \"EmailCredential\", <br />  \"description\": \"EmailCredential using JsonSchema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"credentialSubject\": { <br />      \"type\": \"object\", <br />      \"properties\": { <br />        \"emailAddress\": { <br />          \"type\": \"string\", <br />          \"format\": \"email\" <br />        } <br />      }, <br />      \"required\": [ <br />        \"emailAddress\" <br />      ] <br />    } <br />  } <br />} <br /></code></pre><hr /><p>Example (vc+sd-jwt credential format):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"vct\": { <br />      \"type\": \"string\" <br />    }, <br />    \"iss\": { <br />      \"type\": \"string\" <br />    }, <br />    \"cnf\": { <br />      \"type\": \"object\" <br />    }, <br />    \"email\": { <br />      \"type\": \"string\" <br />    }, <br />    \"is_over_18\": { <br />      \"type\": \"boolean\" <br />    } <br />  }, <br />  \"required\": [ <br />    \"iss\", <br />    \"vct\", <br />    \"cnf\", <br />    \"email\", <br />    \"is_over_18\" <br />  ] <br />} <br /></code></pre>
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:tenant:manage</code></li></ul><br /><p><b>schema_json</b> property must comply with <a target=\"_blank\" href=\"https://www.w3.org/TR/vc-json-schema/\">specification<a>.</p><p>Schema validity can be checked by using one of the Web (Online) validators listed at <a target=\"_blank\" href=\"https://json-schema.org/tools?query=&sortBy=name&sortOrder=ascending&groupBy=toolingTypes&licenses=&languages=&drafts=&toolingTypes=validator\">JSON schema specification site</a>.</p><p><b>schema_json.$id</b> attribute is not expected in the payload. API is going to assign its own internal version of it even if one is being passed.</p><hr /><p>Example (the most minimal set of attributes schema should contain):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"title\": \"EmailCredential\", <br />  \"description\": \"EmailCredential using JsonSchema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"credentialSubject\": { <br />      \"type\": \"object\", <br />      \"properties\": { <br />        \"emailAddress\": { <br />          \"type\": \"string\", <br />          \"format\": \"email\" <br />        } <br />      }, <br />      \"required\": [ <br />        \"emailAddress\" <br />      ] <br />    } <br />  } <br />} <br /></code></pre><hr /><p>Example (vc+sd-jwt credential format):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"vct\": { <br />      \"type\": \"string\" <br />    }, <br />    \"iss\": { <br />      \"type\": \"string\" <br />    }, <br />    \"cnf\": { <br />      \"type\": \"object\" <br />    }, <br />    \"email\": { <br />      \"type\": \"string\" <br />    }, <br />    \"is_over_18\": { <br />      \"type\": \"boolean\" <br />    } <br />  }, <br />  \"required\": [ <br />    \"iss\", <br />    \"vct\", <br />    \"cnf\", <br />    \"email\", <br />    \"is_over_18\" <br />  ] <br />} <br /></code></pre><hr /><p>Example (mso_mdoc credential format):<p><pre><code>{ <br />  \"$schema\": \"https://json-schema.org/draft/2020-12/schema\", <br />  \"type\": \"object\", <br />  \"properties\": { <br />    \"org.iso.18013.5.1\": { <br />      \"type\": \"object\" <br />      \"properties\": { <br />        \"email\": { <br />          \"type\": \"string\" <br />        }, <br />        \"portrait\": { <br />          \"type\": \"string\" <br />          \"description\": \"jpeg as base64url encoded\" <br />          \"x-cbor-encoding\": \"bstr\" <br />        }, <br />      } <br />    }, <br />  }, <br />  \"required\": [ <br />    \"email\", <br />    \"portrait\" <br />  ] <br />} <br /></code></pre>
      * Create schema
      */
     schemasPost(vCCreateSchemaPayloadDto, initOverrides) {
@@ -908,7 +908,8 @@ export const CredentialTypesGetStatusEnum = {
  */
 export const CredentialTypesGetFormatEnum = {
     VcsdJwt: 'vc+sd-jwt',
-    JwtVcJson: 'jwt_vc_json'
+    JwtVcJson: 'jwt_vc_json',
+    MsoMdoc: 'mso_mdoc'
 };
 /**
  * @export

package/lib/esm/apis/VerifiablePresentationsApi.js

@@ -4,7 +4,7 @@
  * SVX API
  * No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
  *
- * The version of the OpenAPI document: 2.0.0
+ * The version of the OpenAPI document: 2.1.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -27,7 +27,7 @@ import { IDPJwtIssuerResponseDtoFromJSON, VCCreatePresentationDefinitionPayloadD
  */
 export class VerifiablePresentationsApi extends runtime.BaseAPI {
     /**
-     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br />It gets registered Presentation Requests own by organisation
+     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br /><p>It gets registered Presentation Requests own by a tenancy or an organisation.</p>
      * Get a list of Presentation Requests registered for organisation
      */
     openidPresentationsRequestsGetRaw(requestParameters, initOverrides) {
@@ -72,7 +72,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br />It gets registered Presentation Requests own by organisation
+     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br /><p>It gets registered Presentation Requests own by a tenancy or an organisation.</p>
      * Get a list of Presentation Requests registered for organisation
      */
     openidPresentationsRequestsGet(status, search, meecoOrganisationID, order, orderBy, perPage, page, initOverrides) {
@@ -122,7 +122,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br />Get Presentation Request for organisation by ID
+     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br /><p>Get a Presentation Request for a tenant or an organisation by ID.</p>
      * Get Presentation Request
      */
     openidPresentationsRequestsIdGetRaw(requestParameters, initOverrides) {
@@ -152,7 +152,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br />Get Presentation Request for organisation by ID
+     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br /><p>Get a Presentation Request for a tenant or an organisation by ID.</p>
      * Get Presentation Request
      */
     openidPresentationsRequestsIdGet(id, meecoOrganisationID, initOverrides) {
@@ -202,7 +202,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br />Register Presentation Request for organisation<br /><p>When using a Presentation Definition with a <code>format</code> of <code>vc+sd-jwt</code>,the <code>vp_formats</code> of the Generated Presentation Request <code>registration</code> will be set to <pre><code>\"vc+sd-jwt\": { <br />   \"sd-jwt_alg_values\": [ <br />       \"ES256\", \"EdDSA\"  <br />     ], <br />     \"sd-jwt_alg_values\": [ <br />       \"ES256\", \"EdDSA\" <br />     ] <br /> } </code>, </pre>and <code>subject_syntax_types_supported</code> will be set to <code>urn:ietf:params:oauth:jwk-thumbprint</code>.</p><br /><br /><pre><code>\"registration\": { <br /> ... <br /> \"subject_syntax_types_supported\": [ <br />    \"urn:ietf:params:oauth:jwk-thumbprint\" <br />  ], <br />  \"vp_formats\": { <br />    \"vc+sd-jwt\": { <br />     \"sd-jwt_alg_values\": [ <br />        \"ES256\", \"EdDSA\" <br />      ], <br />     \"sd-jwt_alg_values\": [ <br />        \"ES256\", \"EdDSA\" <br />      ] <br />    }, <br /> ... <br />} <br /></code></pre>
+     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br /><p>Register a Presentation Request for organisation.</p>
      * Create a Presentation Request
      */
     openidPresentationsRequestsPostRaw(requestParameters, initOverrides) {
@@ -234,7 +234,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br />Register Presentation Request for organisation<br /><p>When using a Presentation Definition with a <code>format</code> of <code>vc+sd-jwt</code>,the <code>vp_formats</code> of the Generated Presentation Request <code>registration</code> will be set to <pre><code>\"vc+sd-jwt\": { <br />   \"sd-jwt_alg_values\": [ <br />       \"ES256\", \"EdDSA\"  <br />     ], <br />     \"sd-jwt_alg_values\": [ <br />       \"ES256\", \"EdDSA\" <br />     ] <br /> } </code>, </pre>and <code>subject_syntax_types_supported</code> will be set to <code>urn:ietf:params:oauth:jwk-thumbprint</code>.</p><br /><br /><pre><code>\"registration\": { <br /> ... <br /> \"subject_syntax_types_supported\": [ <br />    \"urn:ietf:params:oauth:jwk-thumbprint\" <br />  ], <br />  \"vp_formats\": { <br />    \"vc+sd-jwt\": { <br />     \"sd-jwt_alg_values\": [ <br />        \"ES256\", \"EdDSA\" <br />      ], <br />     \"sd-jwt_alg_values\": [ <br />        \"ES256\", \"EdDSA\" <br />      ] <br />    }, <br /> ... <br />} <br /></code></pre>
+     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</li></ul><br /><p>Register a Presentation Request for organisation.</p>
      * Create a Presentation Request
      */
     openidPresentationsRequestsPost(vCCreatePresentationRequestPayloadDto, meecoOrganisationID, initOverrides) {
@@ -244,8 +244,8 @@ export 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 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
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a Presentation Request Response</p><p><b>Checks performed:</b><ul><li>Presentation Request Response <code>id_token</code></li><li>Presentation Request Response <code>vp_token</code></li><li>Presentation Request Response <code>presentation_submission</code> data</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 <code>vp_token</code></li><li>Presentation Definition constraints for the provided <code>vp_token</code></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 nonce value check 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\", \"expiration\"], <br />    } <br />  }, <br />} <br /></code></pre><p>However, <b>some of the checks are mandatory</b>. Please check each option schema separately to find this information.</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 Response
      */
     openidPresentationsResponseVerifyPostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -276,8 +276,8 @@ export 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 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
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Verify a Presentation Request Response</p><p><b>Checks performed:</b><ul><li>Presentation Request Response <code>id_token</code></li><li>Presentation Request Response <code>vp_token</code></li><li>Presentation Request Response <code>presentation_submission</code> data</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 <code>vp_token</code></li><li>Presentation Definition constraints for the provided <code>vp_token</code></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 nonce value check 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\", \"expiration\"], <br />    } <br />  }, <br />} <br /></code></pre><p>However, <b>some of the checks are mandatory</b>. Please check each option schema separately to find this information.</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 Response
      */
     openidPresentationsResponseVerifyPost(vCVerifyPresentationRequestResponsePayloadDto, meecoOrganisationID, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -286,7 +286,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />It gets registered Presentation Definitions own by organisation
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>It gets registered Presentation Definitions own by organisation.</p>
      * Get a list of Presentation Definitions registered for organisation
      */
     presentationDefinitionsGetRaw(requestParameters, initOverrides) {
@@ -334,7 +334,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />It gets registered Presentation Definitions own by organisation
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>It gets registered Presentation Definitions own by organisation.</p>
      * Get a list of Presentation Definitions registered for organisation
      */
     presentationDefinitionsGet(meecoOrganisationID, status, search, order, orderBy, perPage, page, initOverrides) {
@@ -345,7 +345,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
     }
     /**
      * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />
-     * Archive presentation definition
+     * Archive a Presentation Definition
      */
     presentationDefinitionsIdArchivePostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -378,7 +378,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
     }
     /**
      * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />
-     * Archive presentation definition
+     * Archive a Presentation Definition
      */
     presentationDefinitionsIdArchivePost(id, meecoOrganisationID, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -387,7 +387,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * Get JSON representation of Presentation Definition
+     * Get a JSON representation of Presentation Definition
      * Get Presentation Definition JSON representation
      */
     presentationDefinitionsIdDefinitionJsonGetRaw(requestParameters, initOverrides) {
@@ -414,7 +414,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * Get JSON representation of Presentation Definition
+     * Get a JSON representation of Presentation Definition
      * Get Presentation Definition JSON representation
      */
     presentationDefinitionsIdDefinitionJsonGet(id, initOverrides) {
@@ -424,7 +424,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Get Presentation Definition for organisation by ID
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Get Presentation Definition for organisation by ID.</p>
      * Get Presentation Definition
      */
     presentationDefinitionsIdGetRaw(requestParameters, initOverrides) {
@@ -457,7 +457,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />Get Presentation Definition for organisation by ID
+     * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br /><p>Get Presentation Definition for organisation by ID.</p>
      * Get Presentation Definition
      */
     presentationDefinitionsIdGet(id, meecoOrganisationID, initOverrides) {
@@ -468,7 +468,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
     }
     /**
      * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />
-     * restore presentation definition from archive
+     * Restore an archived Presentation Definition
      */
     presentationDefinitionsIdRestorePostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -501,7 +501,7 @@ export class VerifiablePresentationsApi extends runtime.BaseAPI {
     }
     /**
      * <h4>Requires the following security rights:</h4><ul><li><code>vc:org:manage</code></li></ul><br />
-     * restore presentation definition from archive
+     * Restore an archived Presentation Definition
      */
     presentationDefinitionsIdRestorePost(id, meecoOrganisationID, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -510,7 +510,7 @@ export 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><code>input_descriptors</code> property MUST follow the <a target=\"_blank\" href=\"https://identity.foundation/presentation-exchange/spec/v2.1.1/#input-descriptor\">DIF Presentation Exchange Specification</a></p><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>{ <br /> \"vc+sd-jwt\": { <br />    \"sd-jwt_alg_values\": [ <br />      \"ES256\", <br />      \"EdDSA\" <br />    ], <br />    \"kb-jwt_alg_values\": [ <br />      \"ES256\", <br />      \"EdDSA\" <br />    ] <br />  } <br />} <br /></code></pre><p>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 /><p>Register Presentation Definitions for organisation.</p><p><code>input_descriptors</code> property MUST follow the <a target=\"_blank\" href=\"https://identity.foundation/presentation-exchange/spec/v2.1.1/#input-descriptor\">DIF Presentation Exchange Specification</a></p>
      * Create a Presentation Definition
      */
     presentationDefinitionsPostRaw(requestParameters, initOverrides) {
@@ -545,7 +545,7 @@ export 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><code>input_descriptors</code> property MUST follow the <a target=\"_blank\" href=\"https://identity.foundation/presentation-exchange/spec/v2.1.1/#input-descriptor\">DIF Presentation Exchange Specification</a></p><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>{ <br /> \"vc+sd-jwt\": { <br />    \"sd-jwt_alg_values\": [ <br />      \"ES256\", <br />      \"EdDSA\" <br />    ], <br />    \"kb-jwt_alg_values\": [ <br />      \"ES256\", <br />      \"EdDSA\" <br />    ] <br />  } <br />} <br /></code></pre><p>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 /><p>Register Presentation Definitions for organisation.</p><p><code>input_descriptors</code> property MUST follow the <a target=\"_blank\" href=\"https://identity.foundation/presentation-exchange/spec/v2.1.1/#input-descriptor\">DIF Presentation Exchange Specification</a></p>
      * Create a Presentation Definition
      */
     presentationDefinitionsPost(meecoOrganisationID, vCCreatePresentationDefinitionPayloadDto, initOverrides) {
@@ -597,14 +597,11 @@ export 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><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>
+     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</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) {
         return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.meecoOrganisationID === null || requestParameters.meecoOrganisationID === undefined) {
-                throw new runtime.RequiredError('meecoOrganisationID', 'Required parameter requestParameters.meecoOrganisationID was null or undefined when calling presentationsVerifyPost.');
-            }
             if (requestParameters.vCVerifySignedPresentationRequestPayloadDto === null || requestParameters.vCVerifySignedPresentationRequestPayloadDto === undefined) {
                 throw new runtime.RequiredError('vCVerifySignedPresentationRequestPayloadDto', 'Required parameter requestParameters.vCVerifySignedPresentationRequestPayloadDto was null or undefined when calling presentationsVerifyPost.');
             }
@@ -632,12 +629,12 @@ export 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><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>
+     * <h4>Depending on the presence of the <code>Meeco-Organisation-ID</code> header, endpoint requires one of the following security rights:</h4><ul><li><code>vc:tenant:manage</code> if <code>Meeco-Organisation-ID</code> is not specified</li><li><code>vc:org:manage</code> if <code>Meeco-Organisation-ID</code> is specified</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) {
+    presentationsVerifyPost(vCVerifySignedPresentationRequestPayloadDto, meecoOrganisationID, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.presentationsVerifyPostRaw({ meecoOrganisationID: meecoOrganisationID, vCVerifySignedPresentationRequestPayloadDto: vCVerifySignedPresentationRequestPayloadDto }, initOverrides);
+            const response = yield this.presentationsVerifyPostRaw({ vCVerifySignedPresentationRequestPayloadDto: vCVerifySignedPresentationRequestPayloadDto, meecoOrganisationID: meecoOrganisationID }, initOverrides);
             return yield response.value();
         });
     }

package/lib/esm/models/ATOMActiveAndArchivedOrgList.js

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

package/lib/esm/models/ATOMAdmin.js

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

package/lib/esm/models/ATOMAdministeredArchivedOrg.js

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

package/lib/esm/models/ATOMAdministeredOrg.js

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

package/lib/esm/models/ATOMAssignSecurityRightsRequest.js

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

package/lib/esm/models/ATOMCreateOrUpdateOrgRequest.js

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

package/lib/esm/models/ATOMCreateOrUpdateTenantRequest.js

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

package/lib/esm/models/ATOMError.js

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

package/lib/esm/models/ATOMOneOrg.js

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

package/lib/esm/models/ATOMOneTenant.js

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

package/lib/esm/models/ATOMOrg.js

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

package/lib/esm/models/ATOMOrgDescription.js

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

package/lib/esm/models/ATOMOrgList.js

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

package/lib/esm/models/ATOMPaginatedAdminList.js

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