@meeco/svx-api-sdk 1.0.0-develop.20250108183718.7fc3d67 → 1.0.0-develop.20250304125747.40d9c59

package/.openapi-generator/FILES

@@ -222,13 +222,10 @@ models/UtilitiesBlobPublicInfo.ts
 models/UtilitiesBlobPublicInfoResponse.ts
 models/UtilitiesBlobUploadUrlRequest.ts
 models/UtilitiesError.ts
-models/VCClaimsDto.ts
 models/VCCnfDto.ts
 models/VCConstraintsDto.ts
 models/VCCreateCredentialTypeConfigDto.ts
-models/VCCreateCredentialTypeConfigDtoExpiry.ts
 models/VCCreateCredentialTypeDto.ts
-models/VCCreateCredentialTypeExpiryDto.ts
 models/VCCreateCredentialTypePayloadDto.ts
 models/VCCreateCredentialTypeStyleDto.ts
 models/VCCreatePresentationDefinitionDto.ts
@@ -242,12 +239,7 @@ models/VCCredentialJSONSchemaPayloadDto.ts
 models/VCCredentialModelDto.ts
 models/VCCredentialResponseDto.ts
 models/VCCredentialTypeConfigDto.ts
-models/VCCredentialTypeConfigDtoExpiry.ts
-models/VCCredentialTypeExpiryDto.ts
 models/VCCredentialTypeModelDto.ts
-models/VCCredentialTypeModelDtoConfig.ts
-models/VCCredentialTypeModelDtoSchema.ts
-models/VCCredentialTypeModelDtoStyle.ts
 models/VCCredentialTypeResponseDto.ts
 models/VCCredentialTypeSchemaDto.ts
 models/VCCredentialTypeStyleDto.ts
@@ -256,14 +248,16 @@ models/VCCredentialVerificationErrorResponseDto.ts
 models/VCCredentialVerificationOptionsRequestPayloadDto.ts
 models/VCCredentialVerificationResultResponseDto.ts
 models/VCCredentialVerificationWarningResponseDto.ts
+models/VCDeviceKeyInfoDto.ts
 models/VCErrorResponseDto.ts
 models/VCErrorsResponseDto.ts
 models/VCFieldsDto.ts
 models/VCFieldsDtoFilter.ts
+models/VCFilterContainsDto.ts
 models/VCFilterDto.ts
+models/VCFilterItemsDto.ts
 models/VCFilterNotPredicateDto.ts
 models/VCGenerateCredentialDto.ts
-models/VCGenerateCredentialDtoClaims.ts
 models/VCGenerateCredentialPayloadDto.ts
 models/VCGeneratePresentationDto.ts
 models/VCGeneratePresentationPayloadDto.ts

package/lib/esm/apis/ClassificationsApi.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/apis/ConnectionsApi.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/apis/DIDsApi.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/apis/DelegationsApi.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/apis/EventsApi.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/apis/HelpersApi.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/apis/ItemsApi.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/apis/KeysApi.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/apis/MetricsApi.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/apis/OrganisationsApi.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/apis/SecurityRightsApi.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/apis/SharesApi.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/apis/TenantsApi.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/apis/UsersApi.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).
@@ -690,9 +690,6 @@ export class UsersApi extends runtime.BaseAPI {
             if (requestParameters.status !== undefined) {
                 queryParameters['status'] = requestParameters.status;
             }
-            if (requestParameters.invitedVia !== undefined) {
-                queryParameters['invited_via'] = requestParameters.invitedVia;
-            }
             if (requestParameters.order !== undefined) {
                 queryParameters['order'] = requestParameters.order;
             }
@@ -729,9 +726,9 @@ export class UsersApi extends runtime.BaseAPI {
      * <h4>Requires no security rights</h4><br /><p>Endpoint works for a tenant and organisation user based on the <b>Meeco-Organisation-ID</b> header.</p><p>Returns a list of invitations available to the caller.</p><p>In case of tenant context, endpoint returns all invitations available in the tenancy.</p><p>In case of organization context, endpoint returns all invitations available in the organisations.</p>
      * List invitations
      */
-    usersInvitationsGet(status, invitedVia, meecoOrganisationID, order, orderBy, perPage, page, initOverrides) {
+    usersInvitationsGet(status, meecoOrganisationID, order, orderBy, perPage, page, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.usersInvitationsGetRaw({ status: status, invitedVia: invitedVia, meecoOrganisationID: meecoOrganisationID, order: order, orderBy: orderBy, perPage: perPage, page: page }, initOverrides);
+            const response = yield this.usersInvitationsGetRaw({ status: status, meecoOrganisationID: meecoOrganisationID, order: order, orderBy: orderBy, perPage: perPage, page: page }, initOverrides);
             return yield response.value();
         });
     }
@@ -855,8 +852,8 @@ export class UsersApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <p>Creates an invitation for user to join the platform. If user already exists, he/she will be added to the target organisation or tenant.</p><p>Payload example to invite an end user: <em>(DEPRECATED: use <code>/end_users/invitations</code> API instead)</em></p><pre><code>{ <br />  \"invitation\": { <br />    \"via\": \"did\" <br />  } <br />} <br /></code></pre><p>Tenant end user will be invited to is determined by the <code>tid</code> attribute value inside the JWT token.</p><br /><p>Payload example to invite an admin:</p><pre><code>{ <br />  \"invitation\": { <br />    \"via\": \"email\", <br />    \"email\": \"email@meeco.me\", <br />    \"given_name\": \"Peter\", <br />    \"family_name\": \"Peterson\", <br />  } <br />} <br /></code></pre><p> Tenant admin will be invited to is determined by the <code>tid</code> attribute value inside the JWT token & empty the <code>Meeco-Organisation-ID</code> query param value in request. </p><p> Org admin will be invited to is determined by the <code>tid</code> attribute value inside the JWT token & <code>Meeco-Organisation-ID</code> query param value in request. </p><p> Global admin will be invited to is determined by the empty value in <code>tid</code> attribute value inside the JWT token & <code>Meeco-Organisation-ID</code> query param value in request. </p><p> The user who is sending the invitations can only invite other users within the tenant or organization they have selected. </p><p> For example, if the user is in the tenant context, they can only manage tenant users and invitations. Similarly, in the org context, they can only manage org users and invitations, and in the global context, they can only manage global users and invitations. </p>
-     * Invite user to join the platform
+     * <p>Creates an invitation for user to join the platform. If user already exists, he/she will be added to the target organisation or tenant.</p><p>Payload example to invite an admin:</p><pre><code>{ <br />  \"invitation\": { <br />    \"email\": \"email@meeco.me\", <br />    \"given_name\": \"Peter\", <br />    \"family_name\": \"Peterson\", <br />  } <br />} <br /></code></pre><p> Tenant admin will be invited to is determined by the <code>tid</code> attribute value inside the JWT token & empty the <code>Meeco-Organisation-ID</code> query param value in request. </p><p> Org admin will be invited to is determined by the <code>tid</code> attribute value inside the JWT token & <code>Meeco-Organisation-ID</code> query param value in request. </p><p> Global admin will be invited to is determined by the empty value in <code>tid</code> attribute value inside the JWT token & <code>Meeco-Organisation-ID</code> query param value in request. </p><p> The user who is sending the invitations can only invite other users within the tenant or organization they have selected. </p><p> For example, if the user is in the tenant context, they can only manage tenant users and invitations. Similarly, in the org context, they can only manage org users and invitations, and in the global context, they can only manage global users and invitations. </p>
+     * Invite admin to join the platform
      */
     usersInvitationsPostRaw(requestParameters, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -887,8 +884,8 @@ export class UsersApi extends runtime.BaseAPI {
         });
     }
     /**
-     * <p>Creates an invitation for user to join the platform. If user already exists, he/she will be added to the target organisation or tenant.</p><p>Payload example to invite an end user: <em>(DEPRECATED: use <code>/end_users/invitations</code> API instead)</em></p><pre><code>{ <br />  \"invitation\": { <br />    \"via\": \"did\" <br />  } <br />} <br /></code></pre><p>Tenant end user will be invited to is determined by the <code>tid</code> attribute value inside the JWT token.</p><br /><p>Payload example to invite an admin:</p><pre><code>{ <br />  \"invitation\": { <br />    \"via\": \"email\", <br />    \"email\": \"email@meeco.me\", <br />    \"given_name\": \"Peter\", <br />    \"family_name\": \"Peterson\", <br />  } <br />} <br /></code></pre><p> Tenant admin will be invited to is determined by the <code>tid</code> attribute value inside the JWT token & empty the <code>Meeco-Organisation-ID</code> query param value in request. </p><p> Org admin will be invited to is determined by the <code>tid</code> attribute value inside the JWT token & <code>Meeco-Organisation-ID</code> query param value in request. </p><p> Global admin will be invited to is determined by the empty value in <code>tid</code> attribute value inside the JWT token & <code>Meeco-Organisation-ID</code> query param value in request. </p><p> The user who is sending the invitations can only invite other users within the tenant or organization they have selected. </p><p> For example, if the user is in the tenant context, they can only manage tenant users and invitations. Similarly, in the org context, they can only manage org users and invitations, and in the global context, they can only manage global users and invitations. </p>
-     * Invite user to join the platform
+     * <p>Creates an invitation for user to join the platform. If user already exists, he/she will be added to the target organisation or tenant.</p><p>Payload example to invite an admin:</p><pre><code>{ <br />  \"invitation\": { <br />    \"email\": \"email@meeco.me\", <br />    \"given_name\": \"Peter\", <br />    \"family_name\": \"Peterson\", <br />  } <br />} <br /></code></pre><p> Tenant admin will be invited to is determined by the <code>tid</code> attribute value inside the JWT token & empty the <code>Meeco-Organisation-ID</code> query param value in request. </p><p> Org admin will be invited to is determined by the <code>tid</code> attribute value inside the JWT token & <code>Meeco-Organisation-ID</code> query param value in request. </p><p> Global admin will be invited to is determined by the empty value in <code>tid</code> attribute value inside the JWT token & <code>Meeco-Organisation-ID</code> query param value in request. </p><p> The user who is sending the invitations can only invite other users within the tenant or organization they have selected. </p><p> For example, if the user is in the tenant context, they can only manage tenant users and invitations. Similarly, in the org context, they can only manage org users and invitations, and in the global context, they can only manage global users and invitations. </p>
+     * Invite admin to join the platform
      */
     usersInvitationsPost(iDPCreateInvitationPayloadDto, meecoOrganisationID, initOverrides) {
         return __awaiter(this, void 0, void 0, function* () {
@@ -896,90 +893,6 @@ export class UsersApi extends runtime.BaseAPI {
             return yield response.value();
         });
     }
-    /**
-     * <p>Exchange invitation token for a short lived access token that allows Wallet to complete registration flow.</p><p>Short lived access token is valid for a minute and can be used to:<ul><li>verify the request via <code>POST /oidc/presentations/requests/verify</code></li><li>generate a verifiable presentation via <code>POST /presentations/generate</code></li><li>generate an ID Token via <code>POST /oidc/presentations/token</code></li><li>acccept an invitation and get a longer lasting access token to use in the joined tenancy via <code>POST /invitations/{token}/accept</code></li></ul></p>
-     * Exchange invitation token with a short lived access token
-     */
-    usersInvitationsShortLivedAccessTokenPostRaw(requestParameters, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.iDPGenerateShortLivedAccessTokenPayloadDto === null || requestParameters.iDPGenerateShortLivedAccessTokenPayloadDto === undefined) {
-                throw new runtime.RequiredError('iDPGenerateShortLivedAccessTokenPayloadDto', 'Required parameter requestParameters.iDPGenerateShortLivedAccessTokenPayloadDto was null or undefined when calling usersInvitationsShortLivedAccessTokenPost.');
-            }
-            const queryParameters = {};
-            const headerParameters = {};
-            headerParameters['Content-Type'] = 'application/json';
-            const response = yield this.request({
-                path: `/users/invitations/short_lived_access_token`,
-                method: 'POST',
-                headers: headerParameters,
-                query: queryParameters,
-                body: IDPGenerateShortLivedAccessTokenPayloadDtoToJSON(requestParameters.iDPGenerateShortLivedAccessTokenPayloadDto),
-            }, initOverrides);
-            if (this.isJsonMime(response.headers.get('content-type'))) {
-                return new runtime.JSONApiResponse(response);
-            }
-            else {
-                return new runtime.TextApiResponse(response);
-            }
-        });
-    }
-    /**
-     * <p>Exchange invitation token for a short lived access token that allows Wallet to complete registration flow.</p><p>Short lived access token is valid for a minute and can be used to:<ul><li>verify the request via <code>POST /oidc/presentations/requests/verify</code></li><li>generate a verifiable presentation via <code>POST /presentations/generate</code></li><li>generate an ID Token via <code>POST /oidc/presentations/token</code></li><li>acccept an invitation and get a longer lasting access token to use in the joined tenancy via <code>POST /invitations/{token}/accept</code></li></ul></p>
-     * Exchange invitation token with a short lived access token
-     */
-    usersInvitationsShortLivedAccessTokenPost(iDPGenerateShortLivedAccessTokenPayloadDto, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.usersInvitationsShortLivedAccessTokenPostRaw({ iDPGenerateShortLivedAccessTokenPayloadDto: iDPGenerateShortLivedAccessTokenPayloadDto }, initOverrides);
-            return yield response.value();
-        });
-    }
-    /**
-     * <p>Accept invitation by submitting presentation request response. Works for invitation with <code>invited_via</code> attribute set to <code>did</code>.</p><p>If user is already a member of a tenant, invitation status will not change and only access token will returned.</p>
-     * Accept invitation by submitting presentation request response
-     */
-    usersInvitationsTokenAcceptPostRaw(requestParameters, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            if (requestParameters.token === null || requestParameters.token === undefined) {
-                throw new runtime.RequiredError('token', 'Required parameter requestParameters.token was null or undefined when calling usersInvitationsTokenAcceptPost.');
-            }
-            if (requestParameters.iDPAcceptEndUserInvitationPayloadDto === null || requestParameters.iDPAcceptEndUserInvitationPayloadDto === undefined) {
-                throw new runtime.RequiredError('iDPAcceptEndUserInvitationPayloadDto', 'Required parameter requestParameters.iDPAcceptEndUserInvitationPayloadDto was null or undefined when calling usersInvitationsTokenAcceptPost.');
-            }
-            const queryParameters = {};
-            const headerParameters = {};
-            headerParameters['Content-Type'] = 'application/json';
-            if (this.configuration && this.configuration.accessToken) {
-                const token = this.configuration.accessToken;
-                const tokenString = yield token("SVX-JWT", []);
-                if (tokenString) {
-                    headerParameters["Authorization"] = `Bearer ${tokenString}`;
-                }
-            }
-            const response = yield this.request({
-                path: `/users/invitations/{token}/accept`.replace(`{${"token"}}`, encodeURIComponent(String(requestParameters.token))),
-                method: 'POST',
-                headers: headerParameters,
-                query: queryParameters,
-                body: IDPAcceptEndUserInvitationPayloadDtoToJSON(requestParameters.iDPAcceptEndUserInvitationPayloadDto),
-            }, initOverrides);
-            if (this.isJsonMime(response.headers.get('content-type'))) {
-                return new runtime.JSONApiResponse(response);
-            }
-            else {
-                return new runtime.TextApiResponse(response);
-            }
-        });
-    }
-    /**
-     * <p>Accept invitation by submitting presentation request response. Works for invitation with <code>invited_via</code> attribute set to <code>did</code>.</p><p>If user is already a member of a tenant, invitation status will not change and only access token will returned.</p>
-     * Accept invitation by submitting presentation request response
-     */
-    usersInvitationsTokenAcceptPost(token, iDPAcceptEndUserInvitationPayloadDto, initOverrides) {
-        return __awaiter(this, void 0, void 0, function* () {
-            const response = yield this.usersInvitationsTokenAcceptPostRaw({ token: token, iDPAcceptEndUserInvitationPayloadDto: iDPAcceptEndUserInvitationPayloadDto }, initOverrides);
-            return yield response.value();
-        });
-    }
     /**
      * This endpoint updates a user password
      * Change user password
@@ -1100,13 +1013,6 @@ export const EndUsersGetStatusEnum = {
     Deleted: 'deleted',
     All: 'all'
 };
-/**
- * @export
- */
-export const UsersInvitationsGetInvitedViaEnum = {
-    Email: 'email',
-    Did: 'did'
-};
 /**
  * @export
  */

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