# MATTR Learn > Technical documentation for MATTR's digital trust platforms. MATTR provides infrastructure for issuing, holding, and verifying digital credentials using open standards like mDocs, OID4VCI, and OID4VP. MATTR offers three main platforms: - **MATTR VII**: Cloud-based APIs for credential issuance, verification, and ecosystem management - **MATTR Pi**: Mobile SDKs for building holder and verifier applications - **MATTR GO**: White-label applications (GO Hold wallet and GO Verify) Supported credential formats include mDocs (ISO 18013-5), CWT (CBOR Web Token), Semantic CWT, and JSON credentials. - MATTR Platform APIs: Create, manage, and deliver credentials - **MATTR VII Platform API** - [Overview](/docs/api-reference.md) - API Reference - **πŸͺͺ CREDENTIAL ISSUANCE** - **Establishing Trust** - IACA - [Create an IACA](/docs/api-reference/platform/iaca/create-mobile-credential-iaca.md): Creates a new IACA that can be used to sign certificates for Document and Status List signers. - IACAs are always created as inactive. You must manually [update](#operation/update-mobile-credential-iaca) the IACA to [`active: true`](#operation/update-mobile-credential-iaca!path=active&t=request) before it can be used to sign mDocs. - A maximum of three IACAs can be created per tenant. - [Retrieve all IACAs](/docs/api-reference/platform/iaca/list-mobile-credential-iaca.md): Retrieves all existing IACAs from the tenant. - [Retrieve an IACA](/docs/api-reference/platform/iaca/get-mobile-credential-iaca.md): Retrieves an existing IACA by providing its ID. - [Update an IACA](/docs/api-reference/platform/iaca/update-mobile-credential-iaca.md): Update the status of an IACA. Only active IACAs can be used for signing mDocs. Creating an IACA with `active` set to `false` enables distributing the IACA's PEM to relying parties in advance, before it is being used to sign any mDocs. - [Delete an IACA](/docs/api-reference/platform/iaca/delete-mobile-credential-iaca.md): Deletes an existing IACA by providing its ID. - [Retrieve IACA CRL](/docs/api-reference/platform/iaca/get-mobile-credential-iaca-crl.md): Retrieves the Certificate Revocation List (CRL) for the specified IACA in DER binary format. This endpoint is public and does not require authentication. CRLs must be publicly accessible so relying parties can validate certificates. - Document signers - [Create a Document Signer](/docs/api-reference/platform/document-signers/create-mobile-credential-document-signer.md): Creates a new Document Signer that can be used to sign new mDocs. - Only available in implementations using unmanaged (external) IACAs. - A maximum of five Document Signers can be created per tenant. - [Revoke a Document Signer](/docs/api-reference/platform/document-signers/revokeDocumentSigner.md): Revokes an existing Document Signer, making it unusable for signing new mDocs. If the verifier checks the CRL referenced in the IACA certificate, it must treat revoked Document Signers and any mDocs they signed as untrusted. Only available in implementations using managed IACAs. When using unmanaged (external) IACAs, you must revoke the Document Signer certificate directly with the CA that issued it. - [Retrieve all Document Signers](/docs/api-reference/platform/document-signers/list-mobile-credential-document-signers.md): Retrieves all existing Document Signers from the tenant. - [Retrieve a Document Signer](/docs/api-reference/platform/document-signers/retrieve-mobile-credential-document-signer.md): Retrieves an existing Document Signer by providing its ID. - [Update a Document Signer](/docs/api-reference/platform/document-signers/update-mobile-credential-document-signer.md): Updates an existing Document Signer by providing its ID and `active` parameter. Only available in implementations using unmanaged (external) IACAs. - [Delete a Document Signer](/docs/api-reference/platform/document-signers/remove-mobile-credential-document-signer.md): Deletes an existing Document Signer by providing its ID. Only available in implementations using unmanaged (external) IACAs. - Status list signers - [Create a new status list signer](/docs/api-reference/platform/status-list-signers/createStatusListSigner.md): Uses an existing IACA to sign a status list signer (intermediate certificate) that can be used to sign status list tokens. - Only available in implementations using unmanaged (external) IACAs. - A maximum of three Status List Signers can be created per tenant. - [Revoke a status list signer](/docs/api-reference/platform/status-list-signers/revokeStatusListSigner.md): Revokes an existing status list signer, making it unusable for signing new status lists. If the verifier checks the CRL referenced in the IACA certificate, it must treat revoked status list signers and any status list they signed as untrusted. Only available in implementations using managed IACAs. When using unmanaged (external) IACAs, you must revoke the status list signer certificate directly with the CA that issued it. - [Retrieve all status list signers](/docs/api-reference/platform/status-list-signers/getStatusListSigners.md): Retrieves all existing status list signers. - [Retrieve a status list signer](/docs/api-reference/platform/status-list-signers/getStatusListSigner.md): Retrieves an existing status list signer. Status list signer operations are only available in implementations using unmanaged (external) IACAs. - [Update a status list signer](/docs/api-reference/platform/status-list-signers/updateStatusListSigner.md): Updates the status of an existing status list signer. Only available in implementations using unmanaged (external) IACAs. - [Delete a status list signer](/docs/api-reference/platform/status-list-signers/deleteStatusListSigner.md): Deletes an existing status list signer. Only available in implementations using unmanaged (external) IACAs. - **OID4VCI** - Authentication provider - [Configure an Authentication Provider](/docs/api-reference/platform/authentication-provider/createAuthenticationProvider.md): Configures an Authentication Provider on the tenant. An authentication or identity provider (IdP) is a platform that is typically used to store and manage user accounts on behalf of an organization or a service provider. MATTR VII uses the authentication provider to authenticate end users before issuing them credentials. Only one authentication provider can be configured on a tenant. The `/.well-known/openid-configuration` endpoint of the Authentication Provider must contain values for the `authorization_endpoint`, `token_endpoint` and `scopes_supported`. - [Retrieve all Authentication Providers](/docs/api-reference/platform/authentication-provider/getAuthenticationProviders.md): Returns a list of all Authentication Providers on your tenant. - [Retrieve an Authentication Provider](/docs/api-reference/platform/authentication-provider/getAuthenticationProvider.md): Retrieve an existing Authentication Provider by providing its ID. - [Update an Authentication Provider](/docs/api-reference/platform/authentication-provider/updateAuthenticationProvider.md): Updates an existing Authentication Provider by providing its ID. - [Delete an Authentication Provider](/docs/api-reference/platform/authentication-provider/deleteAuthenticationProvider.md): Deletes an existing Authentication Provider by providing its ID. - Interaction hook - [Configure Interaction Hook](/docs/api-reference/platform/interaction-hook/updateOpenIdConfiguration.md): Configure the Interaction Hook for the OID4VCI protocol on your tenant. Many credential issuance journeys require the issuer to perform custom interactions with the user. This could be gathering more information, performing additional authentication steps (E.g, 2FA, MFA or biometric checks) or communicating the terms of service. To facilitate this requirement, you can configure MATTR VII to invoke an interaction hook which will redirect the user to a custom component during the credential issuance journey. This redirect happens **after** the user is authenticated with your configured identity provider but **before** the credential is issued to the user. Upon successful completion of the interaction hook, your custom component will redirect the user back to their digital wallet to complete the credential issuance flow. Your interaction hook component can be either a web or native application. We recommend using a web interface because it's more compatible with most scenarios. You can only configure one interaction hook on your MATTR VII tenant. If you require several custom interactions as part of the credential issuance workflow, they should all be linked into a single interaction hook component. - [Retrieve Interaction Hook](/docs/api-reference/platform/interaction-hook/getOpenIdConfiguration.md): Retrieves the Interaction Hook configuration from your tenant. - Claim source - [Configure a claims source](/docs/api-reference/platform/claims-source/createClaimSource.md): Configures a new claims source for your tenant. When issuing a new credential, MATTR VII will make either a GET or a POST request to the claims source using the configured request parameters and fetch available data. This fetched data can then be included in the issued credential. - [Retrieve all claims sources](/docs/api-reference/platform/claims-source/getClaimSources.md): Returns a list of all claims sources configured on your tenant. - [Retrieve a claims source](/docs/api-reference/platform/claims-source/getClaimSource.md): Retrieves an existing claims source by providing its `claimSourceID`. - [Update a claims source](/docs/api-reference/platform/claims-source/updateClaimSource.md): Updates an existing claim source by providing its `claimSourceID`. - [Delete a claims source](/docs/api-reference/platform/claims-source/deleteClaimSource.md): Deletes an existing claims source by providing its `claimSourceID`. - CWT credential configuration - [Create a CWT credential configuration](/docs/api-reference/platform/cwt-credentials-configuration/createCompactCredentialConfiguration.md): Creates a new CWT credential configuration, a specific set of rules and parameters that are used to create and validate a particular type of verifiable credential. These rules and parameters define how the credential is structured and what data it contains when issued. - [Retrieve all CWT credential configurations](/docs/api-reference/platform/cwt-credentials-configuration/getCompactCredentialConfigurations.md): Returns a list of all CWT credential configurations from your tenant. - [Retrieve a CWT credential configuration](/docs/api-reference/platform/cwt-credentials-configuration/getCompactCredentialConfiguration.md): Returns a CWT credential configuration by providing its ID. - [Update a CWT credential configuration](/docs/api-reference/platform/cwt-credentials-configuration/updateCompactCredentialConfiguration.md): Updates an existing CWT credential configuration by providing its ID. - [Delete a CWT credential configuration](/docs/api-reference/platform/cwt-credentials-configuration/deleteCompactCredentialConfiguration.md): Deletes an existing CWT credential configuration by providing its ID. - S-CWT credential configuration - [Create a Semantic CWT credentials configuration](/docs/api-reference/platform/semantic-cwt-credentials-configuration/createCompactSemanticCredentialConfiguration.md): Creates a new Semantic CWT credentials configuration, a specific set of rules and parameters that are used to create and validate a particular type of verifiable credential. These rules and parameters define how the credential is structured and what data it contains when issued. - [Retrieve all Semantic CWT credentials configurations](/docs/api-reference/platform/semantic-cwt-credentials-configuration/getCompactSemanticCredentialConfigurations.md): Returns a list of all Compact Semantic Credential configurations from your tenant. - [Retrieve a Semantic CWT credentials configuration](/docs/api-reference/platform/semantic-cwt-credentials-configuration/getCompactSemanticCredentialConfiguration.md): Returns a Semantic CWT credentials configuration by providing its ID. - [Update a Semantic CWT credentials configuration](/docs/api-reference/platform/semantic-cwt-credentials-configuration/updateCompactSemanticCredentialConfiguration.md): Updates an existing Semantic CWT credentials configuration by providing its ID. - [Delete a Semantic CWT credentials configuration](/docs/api-reference/platform/semantic-cwt-credentials-configuration/deleteCompactSemanticCredentialConfiguration.md): Deletes an existing Semantic CWT credentials configuration by providing its ID. - JSON credential configuration - [Create a JSON credentials configuration](/docs/api-reference/platform/json-credentials-configuration/createWebSemanticCredentialConfiguration.md): Creates a new JSON credentials configuration, a specific set of rules and parameters that are used to create and validate a particular type of verifiable credential. These rules and parameters define how the credential is structured and what data it contains when issued. - [Retrieve all JSON credentials configurations](/docs/api-reference/platform/json-credentials-configuration/getWebSemanticCredentialConfigurations.md): Returns a list of all JSON credential configurations on your tenant. - [Retrieve a JSON credentials configuration](/docs/api-reference/platform/json-credentials-configuration/getWebSemanticCredentialConfiguration.md): Retrieve a JSON credentials configuration by providing its ID. - [Update a JSON credentials configuration](/docs/api-reference/platform/json-credentials-configuration/updateWebSemanticCredentialConfiguration.md): Updates an existing JSON credentials configuration by providing its ID. - [Delete a JSON credentials configuration](/docs/api-reference/platform/json-credentials-configuration/deleteWebSemanticCredentialConfiguration.md): Deletes an existing JSON credentials configuration by providing its ID. - mDocs credential configuration - [Create an mDocs configuration](/docs/api-reference/platform/mdoc-credentials-configuration/createMobileCredentialConfiguration.md): Creates a new mDocs configuration, a specific set of rules and parameters that are used to create and validate a particular type of verifiable credential. These rules and parameters define how the credential is structured and what data it contains when issued. - [Retrieve all mDocs configurations](/docs/api-reference/platform/mdoc-credentials-configuration/getMobileCredentialConfigurations.md): Retrieves all mDocs configurations from your tenant. - [Retrieve an mDocs configuration](/docs/api-reference/platform/mdoc-credentials-configuration/getMobileCredentialConfiguration.md): Retrieves an existing mDocs configuration by providing its ID. - [Update an mDocs configuration](/docs/api-reference/platform/mdoc-credentials-configuration/updateMobileCredentialConfiguration.md): Updates an existing mDocs configuration by providing its ID. - [Delete an mDocs configuration](/docs/api-reference/platform/mdoc-credentials-configuration/deleteMobileCredentialConfiguration.md): Deletes an existing mDocs configuration by providing its ID. - Credential offers - [Create an Authorization Code credential offer](/docs/api-reference/platform/credential-offers/postOpenIdOffers.md): Returns an OID4VCI credential offer URI. See [https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-10.1](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-10.1) This offer can be used more than once, and can be shared with multiple users. Each user will authenticate independently during the credential issuance workflow, allowing the same offer URI to issue credentials with different user-specific data to multiple holders. - [Create a Pre-Authorized Code credential offer](/docs/api-reference/platform/credential-offers/postOpenIdPreAuthorizedOffers.md): Generate a new [OID4VCI Pre-Authorized Code](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-4.1) credential offer. This offer can only be used once. Once the offer is successfully claimed and the credential is issued, the pre-authorized code is consumed and the offer becomes invalid. The offer cannot be claimed again, even if the same user attempts to claim it. This is a security measure to prevent unauthorized credential duplication. If you need to issue another credential to the same user, you must generate a new credential offer. The Pre-authorized Code flow is only supported for the mDocs credential format. The total size of the request cannot exceed 500KB, including any claims. This is mostly relevant when including large claims such as images. When holders present credentials over Bluetooth Low Energy (BLE), keep payloads as small as practical, as large claims can degrade the transfer experience. Reserve larger payloads for remote presentation flows. - [Delete a Pre-authorized Code credential offer](/docs/api-reference/platform/credential-offers/deleteOpenIdPreAuthorizedOffers.md): Delete an [OID4VCI Pre-authorized Code](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#section-4.1) credential offer. - Issuance - [Request authorization for access to resources](/docs/api-reference/platform/credential-issuance/getOauthAuthorize.md): This endpoint is used to request authorization from the user for access to the requested resources. After the user approves the request, an authorization code is returned to the client. See [https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-authorization-endpoint](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-authorization-endpoint) See [https://www.rfc-editor.org/rfc/rfc6749.html#section-3.1](https://www.rfc-editor.org/rfc/rfc6749.html#section-3.1) - [Exchange authorization code for access token](/docs/api-reference/platform/credential-issuance/postOauthToken.md): This endpoint is used to exchange an authorization code or a pre-authorized code for an access token, which is later used to request a credential. - In an Authorization Code flow the authorization code is obtained from the authorization endpoint after the user has successfully authenticated. - In a Pre-authorized Code flow the pre-authorized code is obtained from the offer URI. See [https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-token-endpoint](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-token-endpoint) for more information. - [Issue a verifiable credential](/docs/api-reference/platform/credential-issuance/postOpenIdCredential.md): Issues a credential to a holder upon presentation of a valid access token, as per [OID4VCI](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html#name-credential-endpoint). Supports [encrypted](/docs/issuance/credential-issuance/e2e-encryption) and non-encrypted credential issuance. Encrypted credential issuance is currently in technical preview and must be enabled on a per-tenant basis. If you would like to enable this feature for your tenant, please [contact us](mailto:dev-support@mattr.global). For non-encrypted credential issuance the valid access token must be provided in one of the following header formats: **Bearer** - Authorization: `Bearer `. - Content-Type: `application/json` - Body: `` OR **DPoP** Only required when using DPoP-bound access tokens. - Authorization: `DPoP `. - DPoP: `` - Content-Type: `application/json` - Body: `` For encrypted credential issuance, [contact us](mailto:dev-support@mattr.global) to configure how your MATTR VII enforces request and/or response encryption, and then: - For **request** encryption, `Content-Type` must be set to `application/jwt` and the payload must be JWE formatted. - For **response** encryption, include the [`credential_response_encryption`](/docs/issuance/credential-issuance/e2e-encryption#encryption-key-provisioning) property in the raw request payload to specify encryption details. - Issuer metadata - [Retrieve OID4VCI issuer metadata](/docs/api-reference/platform/issuer-metadata/wellKnownOidcConfig.md): Returns OID4VCI issuer metadata. This is the standard OID4VCI Well Known endpoint for your tenant. This endpoint is unprotected, public facing and can be deterministically found at the root of the tenant subdomain or alias by any party wishing to discover the OID4VCI capabilities. - [Retrieve authorization server metadata](/docs/api-reference/platform/issuer-metadata/wellKnownOauthAuthorizationServer.md): Returns the OAuth 2.0 Authorization Server Metadata for your tenant. This is the standard OAuth 2.0 Well-Known endpoint, providing public metadata that describes the tenant’s OAuth 2.0 configuration and capabilities. https://www.rfc-editor.org/rfc/rfc8414.html This endpoint is intended for public consumption, and as such does not require authentication. - Users - [Create a User](/docs/api-reference/platform/users/createUser.md): Create a user. * USER_CREATE_START * USER_CREATE_SUCCESS * USER_CREATE_FAIL - [Retrieve all users](/docs/api-reference/platform/users/getUsers.md): Returns a list of all users on your tenant. - [Retrieve a user](/docs/api-reference/platform/users/getUser.md): Retrieve an existing user by providing its ID. * USER_RETRIEVE_START * USER_RETRIEVE_SUCCESS * USER_RETRIEVE_FAIL - [Update a User](/docs/api-reference/platform/users/updateUser.md): Updates an existing user by providing its ID. * USER_UPDATE_START * USER_UPDATE_SUCCESS * USER_UPDATE_FAIL - [Delete a user](/docs/api-reference/platform/users/deleteUser.md): Deletes a user and removes all data related to them by providing the user ID. Deleting a user is irreversible. All of the user's data is removed, and any credential previously issued to them is no longer valid. - [Search users](/docs/api-reference/platform/users/searchUsers.md): Returns a list of users from the tenant that match all the provided search criteria (all criteria are optional). - [Retrieve all user credentials data](/docs/api-reference/platform/users/getUserCredentials.md): Returns metadata for all the credentials issued to the provided `userId`. - **Direct Issuance** - CWT credentials - [Sign a CWT credential](/docs/api-reference/platform/cwt-credentials-issuance/sign-compact-credential.md): Returns a signed CWT credential generated from a provided valid payload. The payload can include any number of custom claims, as CWT credentials do not comply with any specific standard or specification. - [Format a CWT credential as a QR code](/docs/api-reference/platform/cwt-credentials-issuance/generateQrCodeCompactCredential.md): Returns a QR code representation of a CWT credential from a provided encoded string representation of that credential. - [Format a CWT credential as a PDF](/docs/api-reference/platform/cwt-credentials-issuance/GenCompactPdf.md): Returns a PDF representation of a provided CWT credential based on an existing PDF template. The request will fail if the provided credential isn't valid or has expired. - [Format a CWT credential as an Apple Pass](/docs/api-reference/platform/cwt-credentials-issuance/generateCCApplePass.md): Returns an Apple Pass representation of a provided CWT credential based on an existing Apple Pass template. The request will fail if the provided credential isn't valid or has expired. - [Format a CWT credential as a Google Pass](/docs/api-reference/platform/cwt-credentials-issuance/createCCDigitalPass.md): Returns a Google Pass representation of a provided CWT credential based on an existing Google Pass template. The request will fail if the provided credential isn't valid or has expired. - CWT PDF templates - [Create a PDF template](/docs/api-reference/platform/cwt-credentials-pdf-templates/createCompactPdfTemplate.md): Creates a CWT credential PDF template based on a provided `.zip` file. Refer to our [PDF template design guide](https://learn.mattr.global/docs/issuance/cwt-credential-templates/pdf-templates) for more information on how to design a template and structure the `.zip` file. - [Retrieve all PDF templates](/docs/api-reference/platform/cwt-credentials-pdf-templates/getCompactPdfTemplates.md): Retrieves a list of all CWT credentials PDF templates available on the tenant. - [Retrieve a PDF template](/docs/api-reference/platform/cwt-credentials-pdf-templates/getCompactPdfTemplate.md): Retrieves an existing CWT credentials PDF template using its ID. - [Update a PDF template](/docs/api-reference/platform/cwt-credentials-pdf-templates/updateCompactPdfTemplate.md): Update an existing CWT credential PDF template based on a provided `.zip` file. Refer to our [PDF template design guide](https://learn.mattr.global/docs/issuance/cwt-credential-templates/pdf-templates) for more information on how to design a template and structure the `.zip` file. - [Delete a PDF template](/docs/api-reference/platform/cwt-credentials-pdf-templates/deleteCompactPdfTemplate.md): Delete an existing PDF template by providing its ID - CWT Google Pass templates - [Create a Google Pass template](/docs/api-reference/platform/cwt-credentials-google-pass-templates/createCCGooglePassTemplate.md): Creates a Google Pass template based on the provided `.zip` file. Refer to our [Design a Google Pass template](https://learn.mattr.global/docs/issuance/cwt-credential-templates/google-templates) guide for more information on how to design the template and how to structure the `.zip` file. - [Retrieve all Google Pass templates](/docs/api-reference/platform/cwt-credentials-google-pass-templates/getCCGooglePassTemplates.md): Retrieves a list of all Google Pass templates available on your tenant. - [Retrieve a Google Pass template](/docs/api-reference/platform/cwt-credentials-google-pass-templates/retrieveCCGooglePassTemplate.md): Retrieves an existing Google Pass template by providing its ID. - [Update a Google Pass template](/docs/api-reference/platform/cwt-credentials-google-pass-templates/updateCCGooglePassTemplate.md): Updates a existing Google Pass template by providing its ID and a `.zip` file. Refer to our [Design a Google Pass template](https://learn.mattr.global/docs/issuance/cwt-credential-templates/google-templates) guide for more information on how to design the template and how to structure the `.zip` file. - [Delete a Google Pass template](/docs/api-reference/platform/cwt-credentials-google-pass-templates/deleteCCGooglePassTemplate.md): Deletes an existing Google Pass template by providing its ID. - CWT Apple Pass templates - [Create an Apple Pass template](/docs/api-reference/platform/cwt-credentials-apple-pass-templates/createCCApplePassTemplate.md): Creates an Apple Pass template based on the provided `.zip` file. Refer to our [Design an Apple Pass template](https://learn.mattr.global/docs/issuance/cwt-credential-templates/apple-templates) guide for more information on how to design the template and how to structure the `.zip` file. The Apple Pass template uses the official Apple Pass bundle structure. - [Retrieve all Apple Pass templates](/docs/api-reference/platform/cwt-credentials-apple-pass-templates/listCCApplePassTemplates.md): Retrieves a list of all Apple Pass template available on the tenant. - [Retrieve an Apple Pass template](/docs/api-reference/platform/cwt-credentials-apple-pass-templates/retrieveCCApplePassTemplate.md): Retrieves an existing Apple Pass template by providing its ID. - [Update an Apple Pass template](/docs/api-reference/platform/cwt-credentials-apple-pass-templates/updateCCApplePassTemplate.md): Updates an existing Apple Pass template by providing its ID and a `.zip` file. Refer to our [Design an Apple Pass template](https://learn.mattr.global/docs/issuance/cwt-credential-templates/apple-templates) guide for more information on how to design the template and how to structure the `.zip` file. - [Delete an Apple Pass template](/docs/api-reference/platform/cwt-credentials-apple-pass-templates/deleteCCApplePassTemplate.md): Deletes an existing Apple Pass template by providing its ID. - Semantic CWT credentials - [Sign a Semantic CWT credential](/docs/api-reference/platform/semantic-cwt-credentials-issuance/signCompactSemanticcredential.md): Returns a signed Semantic CWT credential generated from a provided valid payload. - [Format a Semantic CWT credential as a QR code](/docs/api-reference/platform/semantic-cwt-credentials-issuance/generateQrCodeCompactSemanticCredential.md): Returns a QR code representation of a Semantic CWT credential from a provided encoded string representation of that credential. - [Format a CWT credential as a PDF](/docs/api-reference/platform/semantic-cwt-credentials-issuance/GenCompactSemanticPdf.md): Returns a PDF representation of a provided CWT credential based on an existing PDF template. The request will fail if the provided credential isn't valid or has expired. - [Format a Semantic CWT credential as an Apple Pass](/docs/api-reference/platform/semantic-cwt-credentials-issuance/generateSCApplePass.md): Returns an Apple Pass representation of a provided Semantic CWT credential based on an existing Apple Pass template. The request will fail if the provided credential isn't valid or has expired. - [Format a Semantic CWT credential as a Google Pass](/docs/api-reference/platform/semantic-cwt-credentials-issuance/createSCDigitalPass.md): Returns a Google Pass representation of a provided CWT credential based on an existing Google Pass template. The request will fail if the provided credential isn't valid or has expired. - S-CWT PDF templates - [Create a PDF template](/docs/api-reference/platform/semantic-cwt-credentials-pdf-templates/createCompactSemanticPdfTemplate.md): Creates a Semantic CWT credential PDF template based on a provided `.zip` file. Refer to our [PDF template design guide](https://learn.mattr.global/docs/issuance/cwt-credential-templates/pdf-templates) for more information on how to design a template and structure the `.zip` file. - [Retrieve all PDF templates](/docs/api-reference/platform/semantic-cwt-credentials-pdf-templates/getCompactSemanticPdfTemplates.md): Retrieves a list of all Semantic CWT credential PDF templates available on the tenant. - [Retrieve a PDF template](/docs/api-reference/platform/semantic-cwt-credentials-pdf-templates/getCompactSemanticPdfTemplate.md): Retrieves an existing Semantic CWT credential PDF template using its ID. - [Update a PDF template](/docs/api-reference/platform/semantic-cwt-credentials-pdf-templates/updateCompactSemanticPdfTemplate.md): Update an existing CWT credential PDF template based on a provided `.zip` file. Refer to our [PDF template design guide](https://learn.mattr.global/docs/issuance/cwt-credential-templates/pdf-templates) for more information on how to design a template and structure the `.zip` file. - [Delete a PDF template](/docs/api-reference/platform/semantic-cwt-credentials-pdf-templates/deleteCompactSemanticPdfTemplate.md): Delete an existing PDF template by providing its ID - S-CWT Google Pass templates - [Create a Google Pass template](/docs/api-reference/platform/semantic-cwt-credentials-google-pass-templates/createSCGooglePassTemplate.md): Creates a Google Pass template based on the provided `.zip` file. Refer to our [Design a Google Pass template](https://learn.mattr.global/docs/issuance/cwt-credential-templates/google-templates) guide for more information on how to design the template and how to structure the `.zip` file. - [Retrieve all Google Pass templates](/docs/api-reference/platform/semantic-cwt-credentials-google-pass-templates/getSCGooglePassTemplates.md): Retrieves a list of all Google Pass templates available on your tenant. - [Retrieve a Google Pass template](/docs/api-reference/platform/semantic-cwt-credentials-google-pass-templates/retrieveSCGooglePassTemplate.md): Retrieves an existing Google Pass template by providing its ID. - [Update a Google Pass template](/docs/api-reference/platform/semantic-cwt-credentials-google-pass-templates/updateSCGooglePassTemplate.md): Updates a existing Google Pass template by providing its ID and a `.zip` file. Refer to our [Design a Google Pass template](https://learn.mattr.global/docs/issuance/cwt-credential-templates/google-templates) guide for more information on how to design the template and how to structure the `.zip` file. - [Delete a Google Pass template](/docs/api-reference/platform/semantic-cwt-credentials-google-pass-templates/deleteSCGooglePassTemplate.md): Delete a Google Pay Pass template by ID - S-CWT Apple Pass templates - [Create an Apple Pass template](/docs/api-reference/platform/semantic-cwt-credentials-apple-pass-templates/createSCApplePassTemplate.md): Creates an Apple Pass template based on the provided `.zip` file. Refer to our [Design an Apple Pass template](https://learn.mattr.global/docs/issuance/cwt-credential-templates/apple-templates) guide for more information on how to design the template and how to structure the `.zip` file. The Apple Pass template uses the official Apple Pass bundle structure. - [Retrieve all Apple Pass templates](/docs/api-reference/platform/semantic-cwt-credentials-apple-pass-templates/listSCApplePassTemplates.md): Retrieves a list of all Apple Pass template available on the tenant. - [Retrieve an Apple Pass template](/docs/api-reference/platform/semantic-cwt-credentials-apple-pass-templates/retrieveSCApplePassTemplate.md): Retrieves an existing Apple Pass template by providing its ID. - [Update an Apple Pass template](/docs/api-reference/platform/semantic-cwt-credentials-apple-pass-templates/updateSCApplePassTemplate.md): Updates an existing Apple Pass template by providing its ID and a `.zip` file. Refer to our [Design an Apple Pass template](https://learn.mattr.global/docs/issuance/cwt-credential-templates/apple-templates) guide for more information on how to design the template and how to structure the `.zip` file. - [Delete an Apple Pass template](/docs/api-reference/platform/semantic-cwt-credentials-apple-pass-templates/deleteSCApplePassTemplate.md): Deletes an existing Apple Pass template by providing its ID. - JSON credentials - [Sign a JSON credential](/docs/api-reference/platform/json-credentials-issuance/signWebSemanticCredentialV2.md): Returns a signed JSON credential generated from a provided valid payload. - **mDocs Management** - Status list configuration - [Create a Status list configuration](/docs/api-reference/platform/status-list-configuration/createStatusListConfiguration.md): Creates a Status list configuration, which defines a status list validity periods. mDocs can then be assigned to a specific Status list configuration. - [Retrieve all Status list configurations](/docs/api-reference/platform/status-list-configuration/StatusListConfigurations.md): Retrieves all Status list configurations from your tenant. - [Retrieve a Status list configuration](/docs/api-reference/platform/status-list-configuration/getStatusListConfiguration.md): Retrieves an existing Status list configuration by providing its ID. - [Update a Status list configuration](/docs/api-reference/platform/status-list-configuration/updateStatusListConfiguration.md): Updates an existing Status list configuration, allowing you to adjust the expiry and TTL (Time To Live) settings. - [Delete a Status list configuration](/docs/api-reference/platform/status-list-configuration/deleteStatusListConfiguration.md): Permanently deletes an existing Status list configuration. - Status list retrieval - [Retrieve all Status lists](/docs/api-reference/platform/status-list-retrieval/getStatusLists.md): **Deprecated.** In line with our SLA, this endpoint will be removed no earlier than 22 September 2026. To discover the Status lists available on a tenant, use the public [Status list distribution](#operation/getStatusListDistribution) endpoint (`GET /v2/credentials/mobile/status-lists/distribution`), which returns the URLs of all Status list tokens on the tenant. To retrieve an individual Status list token, use the public [Retrieve a Status list token](#operation/getStatusListToken) endpoint (`GET /v2/credentials/mobile/status-lists/{statusListId}/token`). Retrieves all existing status lists from your tenant. - [Retrieve a Status list](/docs/api-reference/platform/status-list-retrieval/getStatusList.md): **Deprecated.** In line with our SLA, this endpoint will be removed no earlier than 22 September 2026. To retrieve a Status list token, use the public [Retrieve a Status list token](#operation/getStatusListToken) endpoint (`GET /v2/credentials/mobile/status-lists/{statusListId}/token`), which returns the signed Status list token in CWT format. To discover the Status lists available on a tenant, use the public [Status list distribution](#operation/getStatusListDistribution) endpoint (`GET /v2/credentials/mobile/status-lists/distribution`). Retrieves an existing Status list and its signed token by providing its ID. - [Retrieve a Status list token](/docs/api-reference/platform/status-list-retrieval/getStatusListToken.md): Retrieves the Status list token in CWT format. This public endpoint returns a token which contains a compressed, signed list of credential statuses. Relying parties can use this token to check the revocation status of an mDoc that references this Status list. This endpoint is intended for public consumption, and as such does not require authentication. **Token Format Differences**: The token structure depends on the Status List configuration format: **Draft 14 of the IETF Token Status List specification**: - Token header `typ`: `application/statuslist+cwt` - CBOR payload claims: `65533` (status_list), `65534` (ttl) - Status encoding: 1-bit (Valid/Invalid) **Legacy format**: - Token header `typ`: `mattr-statuslist+cwt` - CBOR payload claims: `-65538` (status_list), `-65539` (ttl) - Status encoding: 2-bit (Valid/Invalid/Suspended) - [Status list distribution](/docs/api-reference/platform/status-list-retrieval/getStatusListDistribution.md): Retrieves an object that details all existing Status lists tokens on the tenant. This public endpoint allows a relying party to consume and cache status lists. Each list in the response includes a URL where its token can be retrieved. Status list tokens that were signed by expired IACAs are excluded from the response. This endpoint is intended for public consumption, and as such does not require authentication. **Response Format Differences**: The response structure depends on the Status List configuration format: **Draft 14 of the IETF Token Status List specification**: `{"status_lists": ["https://..."]}` **Legacy format**: `{"status_lists": [{"uri": "https://..."}]}` - Status update - [Update mDoc status](/docs/api-reference/platform/mdocs-status/postCredentialStatus.md): Sets the status of an existing mDoc by providing its `credentialId` and the new status. Available status values depend on the Status List configuration format: **Draft 14 of the IETF Token Status List specification (1-bit encoding)**: * **valid** - Credential is valid * **invalid** - Credential is invalid (cannot be reversed) **Deprecated Legacy format (2-bit encoding)**: * **valid** - Credential is valid * **invalid** - Credential is invalid (cannot be reversed) * **suspended** - Credential is temporarily suspended The **suspended** status is deprecated and only available in legacy format. - [Retrieve mDoc status](/docs/api-reference/platform/mdocs-status/getCredentialStatus.md): Retrieves the status of an existing mDoc by providing its `credentialId`. - Metadata - [Delete mDoc metadata](/docs/api-reference/platform/mdocs-management/remove-mobile-credential.md): Deletes all stored data for an existing mDoc that matches the provided ID. Removed credential data cannot be recovered. - **CWT Credentials Management** - CWT - [Update CWT credential revocation status](/docs/api-reference/platform/cwt-credentials-management/update-revocation-compact-credential.md): Updates the credential status as revoked (invalid) or unrevoked (valid). - [Retrieve CWT credential revocation status](/docs/api-reference/platform/cwt-credentials-management/get-revocation-compact-credential.md): Retrieve the revocation status of a CWT credential by providing its ID. - [Retrieve all CWT credential revocation lists](/docs/api-reference/platform/cwt-credentials-management/compact-credential-revocation-list-discovery.md): Returns a list of all CWT credential revocation lists on the tenant. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve CWT credential revocation list ⚠️](/docs/api-reference/platform/cwt-credentials-management/compact-credential-revocation-list.md) - [Delete CWT credential metadata](/docs/api-reference/platform/cwt-credentials-management/removeCompactCredential.md): Deletes all credential metadata from the tenant for a specific credential by providing its ID. If the credential was set to be revocable, it will be permanently revoked upon metadata deletion. Note that only metadata of revocable credentials or credentials issued via the OID4VCI flow is saved. Deleted metadata cannot be recovered. - [Retrieve CWT credential revocation list](/docs/api-reference/platform/cwt-credentials-management/compact-credential-revocation-list.md): Returns a CWT credential revocation list by providing its ID. This endpoint is intended for public consumption, and as such does not require authentication. - Semantic CWT - [Update Semantic CWT credential revocation status](/docs/api-reference/platform/semantic-cwt-credentials-management/update-revocation-compact-credential-semantic.md): Updates the credential status as revoked (invalid) or unrevoked (valid). - [Retrieve Semantic CWT credential revocation status](/docs/api-reference/platform/semantic-cwt-credentials-management/get-revocation-compact-credential-semantic.md): Retrieve the revocation status of a Semantic CWT credential by providing its ID. - [Retrieve all Semantic CWT credential revocation lists](/docs/api-reference/platform/semantic-cwt-credentials-management/compact-credential-semantic-revocation-list-discovery.md): Returns a list of all Semantic CWT credential revocation lists on the tenant. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve Semantic CWT credential revocation list](/docs/api-reference/platform/semantic-cwt-credentials-management/compact-credential-semantic-revocation-list.md): Returns a Semantic CWT credential revocation list by providing its ID. This endpoint is intended for public consumption, and as such does not require authentication. - [Delete Semantic CWT credential metadata](/docs/api-reference/platform/semantic-cwt-credentials-management/removeCompactSemanticCredential.md): Deletes all credential metadata from the tenant for a specific credential by providing its ID. If the credential was set to be revocable, it will be permanently revoked upon metadata deletion. Note that only metadata of revocable credentials or credentials issued via the OID4VCI flow is saved. Deleted metadata cannot be recovered. - **JSON Credentials Management** - JSON - [Set credential revocation status](/docs/api-reference/platform/json-credentials-management/setWebSemanticCredentialRevocationStatusV2.md): Sets the revocation status of the credential that matches the provided ID as `true` (revoked) or `false` (unrevoked). - [Retrieve credential revocation status](/docs/api-reference/platform/json-credentials-management/getWebSemanticCredentialRevocationStatusV2.md): Returns the revocation status of the credential matching the provided ID. - [Retrieve revocation list](/docs/api-reference/platform/json-credentials-management/retrieveWebSemanticCredentialRevocationListV2.md): Retrieves a JSON credential revocation list by providing its ID. This endpoint is intended for public consumption, and as such does not require authentication. - [Create a revocation message payload](/docs/api-reference/platform/json-credentials-management/createWebSemanticCredentialRevNotificationV2.md): Returns a message in JWM format that can be used to notify subjects based on their credential revocation status change. To send a notification to the Subject DID holder, use the returned payload with the [encrypt](#operation/encryptMessage) and [send](#operation/sendMessage) endpoints. - [Retrieve all credential data](/docs/api-reference/platform/json-credentials-management/retrieveWebSemanticCredentialListV2.md): Returns all available data for existing credentials: - For credentials that were created with the `persist` flag set to `true`, the response contains both the credential and its metadata. - For credentials that were created with the persist flag set to `false`, the response only contains the metadata (`id`, `tag`, `credentialStatus`, `issuanceDate`). - [Retrieve credential data](/docs/api-reference/platform/json-credentials-management/retrieveWebSemanticCredentialV2.md): Returns all available data for an existing credential that matches the provided ID: - For credentials that were created with the `persist` flag set to `true`, the response contains both the credential and its metadata. - For credentials that were created with the persist flag set to `false`, the response only contains the metadata (`id`, `tag`, `credentialStatus`, `issuanceDate`) - [Delete credential data](/docs/api-reference/platform/json-credentials-management/removeWebSemanticCredentialV2.md): Deletes all stored data for an existing credential that matches the provided ID. If the credential is revocable, it will also be permanently revoked. Removed credential data cannot be recovered. - **πŸ“± CREDENTIAL HOLDING** - Holder applications - [Create a holder application](/docs/api-reference/platform/holder-applications/postHolderApplication.md): Creates a holder application. Once created, application instances can be registered and interact with the MATTR VII platform (for example, to claim credentials). - [Retrieve all holder applications](/docs/api-reference/platform/holder-applications/getHolderApplications.md): Retrieves all configured holder applications. - [Retrieve a holder application](/docs/api-reference/platform/holder-applications/getHolderApplication.md): Retrieves an existing holder application. - [Update a holder application](/docs/api-reference/platform/holder-applications/putHolderApplication.md): Updates an existing holder application. - [Delete a holder application](/docs/api-reference/platform/holder-applications/deleteHolderApplication.md): Deletes an existing holder application. Once deleted, any associated application instances will no longer be able to interact with the MATTR VII platform. - [Retrieve all registered holder application instances](/docs/api-reference/platform/holder-applications/getHolderApplicationInstances.md): Retrieves all registered instances of a holder application. This can be used by application owners to view all registered instances for a given holder application. - [Retrieve a registered holder application instance](/docs/api-reference/platform/holder-applications/getHolderApplicationInstance.md): Retrieves a registered instance of a holder application. - [Delete a registered holder application instance](/docs/api-reference/platform/holder-applications/deleteHolderApplicationInstance.md): Deletes a registered instance of a holder application. Deleted instances will no longer be able to interact with the platform or receive tokens, and any existing tokens will be revoked. Application owners can use this endpoint to remove individual instances that are no longer needed or were registered by mistake, without affecting the entire holder application or its other instances. This is useful for cleaning up test instances or managing specific devices, rather than deleting the whole application and all its associated instances. - Holder root CA certificates - [Create a holder root CA certificate](/docs/api-reference/platform/holder-root-ca-certificates/createHolderCaCertificate.md): Creates a holder root CA certificate that is used to issue wallet attestation signer certificates. Two flows are supported: - **Managed** β€” MATTR VII generates the root certificate and manages the private key on the customer's behalf. Supply no `certificatePem` in the request body; `commonName` and `country` are optional. - **Unmanaged** β€” the customer supplies their own externally-managed root CA in PEM format. `commonName` and `country` are extracted from the certificate and must not be provided in the request. A maximum of three holder root CA certificates can be created per tenant. Only one can be active at a time. The newly-created root is always inactive. Activate it by issuing `PUT /v1/holder/certificates/ca/{certificateId}` with `{ "active": true }`, which also deactivates any previously active root for the tenant (single-active constraint). - [Retrieve all holder root CA certificates](/docs/api-reference/platform/holder-root-ca-certificates/getHolderCaCertificates.md): Retrieves all holder root CA certificates for the tenant. - [Retrieve a holder root CA certificate](/docs/api-reference/platform/holder-root-ca-certificates/getHolderCaCertificate.md): Retrieves a holder root CA certificate by ID. - [Update a holder root CA certificate](/docs/api-reference/platform/holder-root-ca-certificates/updateHolderCaCertificate.md): Updates a holder root CA certificate. The only mutable field is `active`. Setting `active: true` deactivates all other roots for the tenant (single-active constraint). - [Delete a holder root CA certificate](/docs/api-reference/platform/holder-root-ca-certificates/deleteHolderCaCertificate.md): Deletes a holder root CA certificate and cascade-deletes all associated signer certificates. For managed roots and signers, MATTR VII also removes the private key material it was holding on the customer's behalf. Deletion does not invalidate any wallet attestation JWTs that were issued under this root. Those JWTs remain cryptographically valid until their natural expiry β€” verifiers that have already cached the signer's public key may continue to accept them. CRL-based revocation of issued attestations is not supported in this release. - [Retrieve a holder root CA certificate revocation list](/docs/api-reference/platform/holder-root-ca-certificates/getHolderCaCertificateRevocationList.md): Retrieves the Certificate Revocation List (CRL) for a managed holder root CA certificate, as a DER-encoded binary document. This endpoint is only available for managed roots β€” for unmanaged roots it returns `404 NoCertificateRevocationList`. - Wallet attestation signers - [Create a wallet attestation signer](/docs/api-reference/platform/wallet-attestation-signers/createWalletAttestationSigner.md): Creates a wallet attestation signer for an unmanaged root CA and returns its Certificate Signing Request (CSR). This endpoint is only available for unmanaged roots β€” managed root signers are auto-provisioned on demand during the first wallet attestation request and never need to be created explicitly. The returned signer is created with `active: false`; use the CSR to obtain a signed certificate externally and upload it via `PUT /v1/holder/certificates/wallet-attestation-signers/{certificateId}` to activate the signer. A maximum of five wallet attestation signers can be created per root. - [Retrieve all wallet attestation signers](/docs/api-reference/platform/wallet-attestation-signers/getWalletAttestationSigners.md): Retrieves all wallet attestation signers for the tenant across all roots. The response may contain a mix of: - CSR-pending signers (unmanaged, certificate not yet uploaded) - Active signers (managed or unmanaged with an uploaded certificate) - [Retrieve a wallet attestation signer](/docs/api-reference/platform/wallet-attestation-signers/getWalletAttestationSigner.md): Retrieves a wallet attestation signer by ID. The response shape depends on the signer's state β€” CSR-pending signers return a CSR, signers with a signed certificate return the full certificate details. - [Update a wallet attestation signer](/docs/api-reference/platform/wallet-attestation-signers/updateWalletAttestationSigner.md): Updates a wallet attestation signer by: - Uploading a signed certificate PEM that matches the signer's CSR (first-time upload for CSR-pending signers only). - Activating or deactivating the signer. Only signers with a valid PEM certificate can be activated. `certificatePem` is immutable after the first upload β€” subsequent PUT requests may only toggle `active`. - [Delete a wallet attestation signer](/docs/api-reference/platform/wallet-attestation-signers/deleteWalletAttestationSigner.md): Deletes a wallet attestation signer. For managed signers, MATTR VII also removes the private key material it was holding on the customer's behalf. - **βœ… CREDENTIAL VERIFICATION** - **Establishing Trust** - Verifier root CA certificates - [Create a verifier root CA certificate](/docs/api-reference/platform/verifier-root-ca-certificates/postVerifierCACertificate.md): Creates a verifier root CA certificate to be used as part of mDocs online verification workflows. - A maximum of three Verifier root CA certificates can be created per tenant. - [Retrieve all verifier root CA certificates](/docs/api-reference/platform/verifier-root-ca-certificates/getVerifierCACertificates.md): Retrieves all existing verifier root CA certificates. - [Retrieve a verifier root CA certificate](/docs/api-reference/platform/verifier-root-ca-certificates/getVerifierCACertificate.md): Retrieves an existing verifier root CA certificate. - [Update a verifier root CA certificate](/docs/api-reference/platform/verifier-root-ca-certificates/putVerifierCACertificate.md): Updates an existing verifier root CA certificate. - [Delete a verifier root CA certificate](/docs/api-reference/platform/verifier-root-ca-certificates/deleteVerifierCACertificate.md): Deletes an existing verifier root CA certificate. - Verification request signers - [Create a Verification request signer](/docs/api-reference/platform/verification-request-signers/createVerificationRequestSigner.md): Creates a Verification request signer. - Only available in implementations using unmanaged (external) Verifier root CA certificates. - A maximum of five Verification request signers can be created per tenant. - [Retrieve all Verification request signers](/docs/api-reference/platform/verification-request-signers/getVerificationRequestSigners.md): Retrieves all Verification request signers. - [Retrieve a Verification request signer](/docs/api-reference/platform/verification-request-signers/getVerificationRequestSigner.md): Retrieves a Verification request signer. - [Update a Verification request signer](/docs/api-reference/platform/verification-request-signers/updateVerificationRequestSigner.md): Updates a Verification request signer by: - Providing a Verification Request Signer Certificate (VRSC) in PEM format that matches its Certificate Signing Request (CSR). - Activating or deactivating the VRSC signer. Only VRSC signers with a valid PEM certificate can be activated. - The `certificatePem` field becomes immutable after it's updated for the first time. Only available in implementations using unmanaged (external) Verifier root CA certificates. - [Delete a Verification request signer](/docs/api-reference/platform/verification-request-signers/deleteVerificationRequestSigner.md): Deletes a Verification request signer. Only available in implementations using unmanaged (external) Verifier root CA certificates. - Trusted issuers - [Create a trusted issuer](/docs/api-reference/platform/trusted-issuers/addMobileCredentialTrustedIssuer.md): Add a new mDocs trusted issuer, to be used in online presentation workflows. - [Retrieve all trusted issuers](/docs/api-reference/platform/trusted-issuers/getMobileCredentialTrustedIssuers.md): Retrieves all mDocs trusted issuers from your tenant. - [Retrieve all trusted issuers](/docs/api-reference/platform/trusted-issuers/getTrustedIssuers.md): Retrieves all configured trusted issuers. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve a trusted issuer](/docs/api-reference/platform/trusted-issuers/getMobileCredentialTrustedIssuer.md): Retrieves an existing trusted issuer from your tenant by providing its ID. - [Delete a trusted issuer](/docs/api-reference/platform/trusted-issuers/deleteMobileCredentialTrustedIssuer.md): Deletes an existing trusted issuer by providing its ID. - Wallet providers - [Create wallet provider](/docs/api-reference/platform/wallet-providers/postWalletProvider.md): Creates a wallet provider that can present mDocs for online verification. - [Retrieve all wallet providers](/docs/api-reference/platform/wallet-providers/getWalletProviders.md): Retrieves all existing wallet providers that can present mDocs for online verification. - [Retrieve a wallet provider](/docs/api-reference/platform/wallet-providers/getWalletProvider.md): Retrieves an existing wallet provider that can present mDocs for online verification. - [Update a wallet provider](/docs/api-reference/platform/wallet-providers/putWalletProvider.md): Updates an existing wallet provider that can present mDocs for online verification. - [Delete a wallet provider](/docs/api-reference/platform/wallet-providers/deleteWalletProvider.md): Deletes an existing wallet provider that can present mDocs for online verification. - Apple Identity Access certificates - [Create an Apple Identity Access CSR](/docs/api-reference/platform/apple-identity-access-certificates/postAppleIdentityAccessCertificates.md): Creates an Apple Identity Access Certificate Signing Request (CSR) that can be uploaded to the Apple Developer Portal. This certificate contains the public key that will be used to decrypt the response from the Apple Wallet. - [Retrieve all Apple Identity Access CSRs](/docs/api-reference/platform/apple-identity-access-certificates/getAppleIdentityAccessCertificates.md): Retrieves all Apple Identity Access CSRs created by the tenant. - [Retrieve an Apple Identity Access CSR](/docs/api-reference/platform/apple-identity-access-certificates/getAppleIdentityAccessCertificate.md): Retrieves an existing Apple Identity Access CSR. - [Delete an Apple Identity Access CSR](/docs/api-reference/platform/apple-identity-access-certificates/deleteAppleIdentityAccessCertificate.md): Deletes an existing Apple Identity Access CSR. - **mDocs Verification** - Verifier applications - [Create verifier application](/docs/api-reference/platform/verifier-applications/postVerifierApplication.md): Creates an mDocs online verifier application. Once created, application instances can be registered and interact with the MATTR VII platform (for example, to verify credential presentations). - [Retrieve all verifier applications](/docs/api-reference/platform/verifier-applications/getVerifierApplications.md): Retrieves all configured mDocs online verifier applications. - [Retrieve a verifier application](/docs/api-reference/platform/verifier-applications/getVerifierApplication.md): Retrieves an existing mDocs online verifier application. - [Update verifier application](/docs/api-reference/platform/verifier-applications/putVerifierApplication.md): Updates an existing mDocs online verifier application. - [Delete a verifier application](/docs/api-reference/platform/verifier-applications/deleteVerifierApplication.md): Deletes an existing verifier application. Once deleted, any associated application instances will no longer be able to interact with the MATTR VII platform. - [Retrieve all registered verifier application instances](/docs/api-reference/platform/verifier-applications/getVerifierApplicationInstances.md): Retrieves all registered instances of a verifier application. This can be used by application owners to view all registered instances for a given verifier application. - [Retrieve a registered verifier application instance](/docs/api-reference/platform/verifier-applications/getVerifierApplicationInstance.md): Retrieves a registered instance of a verifier application. - [Delete a registered verifier application instance](/docs/api-reference/platform/verifier-applications/deleteVerifierApplicationInstance.md): Deletes a registered instance of a verifier application. Deleted instances will no longer be able to interact with the platform or receive tokens, and any existing tokens will be revoked. Application owners can use this endpoint to remove individual instances that are no longer needed or were registered by mistake, without affecting the entire verifier application or its other instances. This is useful for cleaning up test instances or managing specific devices, rather than deleting the whole application and all its associated instances. - Presentation sessions - [Retrieve presentation session result](/docs/api-reference/platform/mdocs-presentation-sessions/getPresentationResult.md): Retrieves the result of an online presentation session by providing the session's ID. When a holder responds to a verification request, the result indicates whether the presentation succeeded and whether the credentials were verified. The response can be a `PresentationSuccessResult` (holder completed the presentation workflow) or a `PresentationFailureResult` (holder was unable to complete the workflow). A successful presentation may include verified credentials, credential errors (requested credentials not provided), claim errors (specific claims that failed verification), or a combination of these outcomes. Your backend should validate that the returned `challenge` matches the challenge generated before starting the session to protect against session replay attacks. For detailed information about result structures, error types, and complete examples, see the [handling verification results guide](https://learn.mattr.global/docs/verification/remote-web-verifiers/handling-verification-results). - **CWT Credentials Verification** - CWT - [Verify a CWT credential](/docs/api-reference/platform/cwt-credentials-verification/verify-compact-credential.md): Verify a CWT credential by providing the encoded payload and specifying verification options. You can provide a valid CWT credential as either an encoded string or a QR code in a PDF document or an image file. Standard checks performed on all verification requests: - Conformance of the string and encoded data. All string representations of CWT credentials must be prefixed with `CSC/1`. - Decoded payload structure is a valid CWT credential. - Issuer DID can be used to resolve its `did.json` document. - Public key from issuer's `did.json` document validates the proof signature, confirming the credential has not been tampered with. Optional parameter checks: - Credential was issued by a trusted issuer. - Current time is after the beginning of the credential validity period. - Current time is not after the end of the credential validity period. - Credential has not been revoked. - Semantic CWT - [Verify a Semantic CWT credential](/docs/api-reference/platform/semantic-cwt-credentials-verification/verifyCompactSemantiCredential.md): Verify a Semantic CWT credential by providing the encoded payload and specifying verification options. You can provide a valid Semantic CWT credential as either an encoded string or a QR code in a PDF document or an image file. Standard checks performed on all verification requests: - Conformance of the string and encoded data. All string representations of CWT credentials must be prefixed with `CSC/1`. - Decoded payload CWT structure and attributes can be validated. - Remote context schema can be resolved and validate claims can be dereferenced. - Issuer DID can be used to resolve its `did.json` document. - Public key from issuer's `did.json` document validates the proof signature, confirming the credential has not been tampered with. Optional parameter checks: - Credential was issued by a trusted issuer. - Current time is after the beginning of the credential validity period. - Current time is not after the end of the credential validity period. - Credential has not been revoked. - **JSON Credentials Verification** - JSON - [Verify a JSON credential](/docs/api-reference/platform/json-credentials-verification/verifyWebSemanticCredentialV2.md): Verify a JSON credential by providing its payload. The credential is verified against the following criteria: - Issuer DID can be resolved, so that the referenced DID Document is available and valid and the public key is obtainable. - Proof is valid and the credential has not been tampered with. - JSON-LD context is valid for subject claims. Optional verification checks: - If `assertExpiry` is set to `true` and the credential has a set expiration date, verification will fail if the expiration date has passed. - If `checkRevocation` is set to `true` and the provided credential contains a revocation status list, verification will fail if the credential has been set to `revoked`. - [Create a presentation template](/docs/api-reference/platform/json-credentials-verification/createPresTemplateV2.md): Creates a presentation template defining what type of credential is required for a particular verification workflow. Presentation templates are used to create presentation requests that are shared with a specific holder. - [Retrieve all presentation templates](/docs/api-reference/platform/json-credentials-verification/retrievePresTemplatesV2.md): Returns a list of all presentation templates on your tenant. - [Retrieve a presentation template](/docs/api-reference/platform/json-credentials-verification/retrievePresTemplateV2.md): Retrieve an existing presentation template by its ID. - [Update a presentation template](/docs/api-reference/platform/json-credentials-verification/updatePresTemplateV2.md): Updates an existing presentation template by its ID. - [Delete a presentation template](/docs/api-reference/platform/json-credentials-verification/removePresTemplateV2.md): Deletes an existing presentation template by its ID. - [Create a presentation request](/docs/api-reference/platform/json-credentials-verification/createPresRequestV2.md): Creates a short lived presentation request based on an existing presentation template. The request is returned in the form of a JWM message and must be [signed](#operation/signMessage) and sent to the holder via one of the following methods: - QR code. - Deeplink. - [Encrypted](#operation/encryptMessage) and [sent](#operation/sendMessage) as a wallet notification. - [Verify a verifiable presentation](/docs/api-reference/platform/json-credentials-verification/verifyPresV2.md): Verifies a provided verifiable presentation that adheres to the [W3C Verifiable Credential Data Model](https://www.w3.org/TR/vc-data-model/#presentations): - Ensures the presentation conforms to the VC Data model. - For each `verifiableCredential` objects: - Issuer DID can be resolved. - JSON-LD context is valid for subject claims. - Proof is valid & the credential has not been tampered with. - Is not in a `revoked` status on a `RevocationList2020`. - The proof is valid for each subjectDID to prove ownership. - Valid proof exists for the presentation `holderDID`. The request must include a `presentation` object that adheres to the [W3C Verifiable Credential Data Model](https://www.w3.org/TR/vc-data-model/#presentations). If a `challenge` and/or `domain` is provided they are used for credential verification. Otherwise, the `challenge` and/or `domain` within the presentation proof is used instead. - **🌐 TRUST NETWORKS** - **Establishing Trust** - DTS root CA certificates - [Create a DTS root CA certificate](/docs/api-reference/platform/dts-root-ca-certificates/createDtsCaCertificate.md): Creates a DTS root CA certificate which is used to sign DTS intermediate and/or signer certificates. - A maximum of three DTS root CA certificates can be created per tenant. - [Retrieve all DTS root CA certificates](/docs/api-reference/platform/dts-root-ca-certificates/getDtsCaCertificates.md): Retrieves all DTS root CA certificates. - [Retrieve a DTS root CA certificate](/docs/api-reference/platform/dts-root-ca-certificates/getDtsCaCertificate.md): Retrieves a DTS root CA certificate. - [Update a DTS root CA certificate](/docs/api-reference/platform/dts-root-ca-certificates/updateDtsCaCertificate.md): Updates a DTS root CA certificate. - [Delete a DTS root CA certificate](/docs/api-reference/platform/dts-root-ca-certificates/deleteDtsCaCertificate.md): Deletes a DTS root CA certificate. - [Retrieve a DTS root CA certificate revocation list](/docs/api-reference/platform/dts-root-ca-certificates/getDtsCaCertificateRevocationList.md): Retrieves the revocation list for a given DTS root CA certificate. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve all public DTS root CA certificates](/docs/api-reference/platform/dts-root-ca-certificates/getDtsCaCertificatePublic.md): Retrieves all public DTS root CA certificates. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve DTS root CA certificate ⚠️](/docs/api-reference/platform/dts-root-ca-certificates/getLatestVicalCaCertificate.md) - [Retrieve DTS root CA certificate revocation list ⚠️](/docs/api-reference/platform/dts-root-ca-certificates/getVicalCertificateRevocationList.md) - [Retrieve DTS root CA certificate](/docs/api-reference/platform/dts-root-ca-certificates/getLatestVicalCaCertificate.md): Retrieves the latest DTS root CA certificate. This can be used by relying parties to verify a signed VICAL. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve DTS root CA certificate revocation list](/docs/api-reference/platform/dts-root-ca-certificates/getVicalCertificateRevocationList.md): Retrieves revocation list for a given DTS root CA certificate. This endpoint is intended for public consumption, and as such does not require authentication. - Intermediate certificates - [Create a DTS intermediate CA certificate](/docs/api-reference/platform/dts-intermediate-ca-certificates/createDtsIntermediateCaCertificate.md): Creates a DTS intermediate CA certificate, which sits between the DTS root CA certificate and the signer certificate to sign DTS signer certificates. DTS intermediate CA certificates are only relevant when using the 3-tier certificate model, where a DTS root CA signs an intermediate CA, which in turn signs the signer certificate. They are only supported for unmanaged (external) DTS root CA certificates that have `useIntermediateCa` set to `true`. For an explanation of the 2-tier and 3-tier models and guidance on choosing between them, refer to the [DTS certificates overview](https://learn.mattr.global/docs/digital-trust-service/certificates-overview#certificate-models-2-tier-and-3-tier). - [Retrieve all DTS intermediate CA certificates under a root CA](/docs/api-reference/platform/dts-intermediate-ca-certificates/getDtsIntermediateCaCertificates.md): Retrieves all DTS intermediate CA certificates issued under the specified DTS root CA. - [Retrieve a DTS intermediate CA certificate](/docs/api-reference/platform/dts-intermediate-ca-certificates/getDtsIntermediateCaCertificate.md): Retrieves a DTS intermediate CA certificate. - [Update a DTS intermediate CA certificate](/docs/api-reference/platform/dts-intermediate-ca-certificates/updateDtsIntermediateCaCertificate.md): Updates a DTS intermediate CA certificate. - [Delete a DTS intermediate CA certificate](/docs/api-reference/platform/dts-intermediate-ca-certificates/deleteDtsIntermediateCaCertificate.md): Deletes a DTS intermediate CA certificate. - VICAL Signers - [Create a VICAL signer](/docs/api-reference/platform/vical-signers/createVicalSigner.md): Creates a VICAL signer. - Only available in implementations using unmanaged (external) DTS root CA certificates. - A maximum of five VICAL signers can be created per tenant. - [Retrieve all VICAL signers](/docs/api-reference/platform/vical-signers/getVicalSigners.md): Retrieves all VICAL signers. - [Retrieve a VICAL signer](/docs/api-reference/platform/vical-signers/getVicalSignerCertificate.md): Retrieves a VICAL signer. - [Update a VICAL signer](/docs/api-reference/platform/vical-signers/updateVicalSigner.md): Updates a VICAL signer by: - Providing a VICAL Signer Certificate (VSC) in PEM format that matches its Certificate Signing Request (CSR). - Activating or deactivating the VICAL signer. Only VICAL signers with a valid `certificatePem` can be activated. - The `certificatePem` field becomes immutable after it's updated for the first time. Only available in implementations using unmanaged (external) DTS root CA certificates. - [Delete a VICAL signer](/docs/api-reference/platform/vical-signers/deleteVicalSigner.md): Deletes a VICAL signer. Only available in implementations using unmanaged (external) DTS root CA certificates. - RICAL Signers - [Create a RICAL signer](/docs/api-reference/platform/rical-signers/createRicalSigner.md): Creates a RICAL signer. - Only available in implementations using unmanaged (external) DTS root CA certificates. - A maximum of five RICAL signers can be created per tenant. Provide either `caId` or `intermediateCaId`. - [Retrieve all RICAL signers](/docs/api-reference/platform/rical-signers/getRicalSigners.md): Retrieves all RICAL signers. - [Retrieve a RICAL signer](/docs/api-reference/platform/rical-signers/getRicalSignerCertificate.md): Retrieves a RICAL signer. - [Update a RICAL signer](/docs/api-reference/platform/rical-signers/updateRicalSigner.md): Updates a RICAL signer by: - Providing a RICAL Signer Certificate in PEM format that matches its Certificate Signing Request (CSR). - Activating or deactivating the RICAL signer. Only RICAL signers with a valid `certificatePem` can be activated. - The `certificatePem` field becomes immutable after it's updated for the first time. Only available in implementations using unmanaged (external) DTS root CA certificates. - [Delete a RICAL signer](/docs/api-reference/platform/rical-signers/deleteRicalSigner.md): Deletes a RICAL signer. Deleting a RICAL signer does not affect any RICALs it has already signed β€” those remain valid. It only means this signer can no longer be used to sign new RICALs. Only available in implementations using unmanaged (external) DTS root CA certificates. - **Ecosystem** - Ecosystems - [Create ecosystem](/docs/api-reference/platform/ecosystems/createEcosystem.md): Creates an ecosystem. - [Retrieve all ecosystems](/docs/api-reference/platform/ecosystems/getEcosystems.md): Retrieves a list of ecosystems. - [Retrieve ecosystem](/docs/api-reference/platform/ecosystems/getEcosystem.md): Retrieves an ecosystem by its ID. - [Update ecosystem](/docs/api-reference/platform/ecosystems/updateEcosystem.md): Updates an ecosystem by its ID. - [Delete ecosystem](/docs/api-reference/platform/ecosystems/deleteEcosystem.md): Deletes an ecosystem by its ID. - [Sync ecosystem](/docs/api-reference/platform/ecosystems/syncEcosystem.md): Synchronizes all configured consumptions and integrations by retrieving the most recent trust information. - Ecosystem Configuration - [Create ecosystem configuration](/docs/api-reference/platform/ecosystem-configuration/createEcosystemConfiguration.md): Creates an ecosystem configuration for the tenant. - [Retrieve ecosystem configuration](/docs/api-reference/platform/ecosystem-configuration/getEcosystemConfiguration.md): Retrieves the tenant's ecosystem configuration. - [Update ecosystem configuration](/docs/api-reference/platform/ecosystem-configuration/updateEcosystemConfiguration.md): Updates the tenant's ecosystem configuration. - [Delete ecosystem configuration](/docs/api-reference/platform/ecosystem-configuration/deleteEcosystemConfiguration.md): Deletes the tenant's ecosystem configuration. - Credential types - [Create credential type](/docs/api-reference/platform/credential-types/createEcosystemCredential.md): Creates a new credential type in the requested ecosystem. - [Retrieve credential types](/docs/api-reference/platform/credential-types/getEcosystemCredentials.md): Retrieves a list of credential types from the requested ecosystem. - [Retrieve credential type](/docs/api-reference/platform/credential-types/getEcosystemCredential.md): Retrieves a credential type from the requested ecosystem by its ID. - [Delete credential type](/docs/api-reference/platform/credential-types/deleteEcosystemCredential.md): Deletes a credential type from the requested ecosystem by its ID. - **Participants** - Participants - [Create participant](/docs/api-reference/platform/participants/createEcosystemParticipant.md): Creates a participant in the requested ecosystem. - [Retrieve participants](/docs/api-reference/platform/participants/getEcosystemParticipants.md): Retrieves a list of participants from the requested ecosystem. - [Retrieve participant](/docs/api-reference/platform/participants/getEcosystemParticipant.md): Retrieves a participant from the requested ecosystem by its ID. - [Update participant](/docs/api-reference/platform/participants/updateEcosystemParticipant.md): Updates a participant in the requested ecosystem by its ID. - [Delete participant](/docs/api-reference/platform/participants/deleteEcosystemParticipant.md): Deletes a participant in the requested ecosystem by its ID. - Participant assignment - [Create issuer assignment](/docs/api-reference/platform/participants-assignment/createEcosystemIssuerPolicy.md): Assigns a credential type to the requested participant in the requested ecosystem. - [Delete issuer assignment](/docs/api-reference/platform/participants-assignment/deleteEcosystemIssuerPolicy.md): Removes a credential type to the requested participant in the requested ecosystem. - [Create verifier assignment](/docs/api-reference/platform/participants-assignment/createEcosystemVerifierPolicy.md): Assigns a credential type to the requested participant in the requested ecosystem. - [Delete verifier assignment](/docs/api-reference/platform/participants-assignment/deleteEcosystemVerifierPolicy.md): Removes a credential type from the requested participant in the requested ecosystem.. - Participant contacts - [Create a participant point of contact](/docs/api-reference/platform/participants-contacts/createParticipantContact.md): Create a new point of contact for the specified participant. A maximum of 10 contacts can exist per participant. - [Retrieve all participant points of contact](/docs/api-reference/platform/participants-contacts/retrieveParticipantContacts.md): Retrieve all points of contact for given participant. - [Retrieve a participant point of contact](/docs/api-reference/platform/participants-contacts/retrieveParticipantContact.md): Retrieve a specific point of contact for a given participant. - [Update a participant point of contact](/docs/api-reference/platform/participants-contacts/updateParticipantContact.md): Update a specific point of contact for a given participant. - [Delete a participant point of contact](/docs/api-reference/platform/participants-contacts/deleteParticipantContact.md): Delete a specific point of contact for a given participant. - Participant evidence - [Upload PDF evidence](/docs/api-reference/platform/participants-evidence/uploadPdfEvidence.md): Upload a PDF file as evidence for the given participant. Maximum file size is 10MB. - [Download PDF evidence](/docs/api-reference/platform/participants-evidence/downloadPdfEvidence.md): Retrieves a specific PDF evidence file. - [Retrieve all PDF evidence metadata](/docs/api-reference/platform/participants-evidence/retrievePdfEvidenceList.md): Retrieve metadata for all PDF evidence uploaded for given participant. - [Retrieve a PDF evidence metadata](/docs/api-reference/platform/participants-evidence/retrievePdfEvidence.md): Retrieve metadata for a given uploaded PDF evidence. - [Update PDF evidence metadata](/docs/api-reference/platform/participants-evidence/updatePdfEvidence.md): Update metadata for a given uploaded PDF evidence. - [Delete PDF evidence](/docs/api-reference/platform/participants-evidence/deletePdfEvidence.md): Delete metadata for a given uploaded PDF evidence and remove it from storage. - Participant issuer certificates - [Create a participant issuer certificate](/docs/api-reference/platform/participants-issuer-certificates/createParticipantIssuerCertificate.md): Create a new issuer certificate for the specified participant. The certificatePem field cannot be modified once the certificate is created. To maintain trust continuity across a certificate rotation, provide `linkCertificateInfo` to add this certificate as a successor to a previously uploaded certificate. Link certificates can only be added when the certificate is created, not when it is updated. - [Retrieve all participant issuer certificates](/docs/api-reference/platform/participants-issuer-certificates/retrieveParticipantIssuerCertificates.md): Retrieve all issuer certificates for the specified participant. - [Retrieve a participant issuer certificate](/docs/api-reference/platform/participants-issuer-certificates/retrieveParticipantIssuerCertificate.md): Retrieve a specific issuer certificate for the specified participant. - [Update a participant issuer certificate](/docs/api-reference/platform/participants-issuer-certificates/updateParticipantIssuerCertificate.md): Update a specific issuer certificate for the specified participant. - [Delete a participant issuer certificate](/docs/api-reference/platform/participants-issuer-certificates/deleteParticipantIssuerCertificate.md): Delete a specific issuer certificate for the specified participant. - Participant verifier certificates - [Create a participant verifier certificate](/docs/api-reference/platform/participants-verifier-certificates/createParticipantVerifierCertificate.md): Create a new verifier certificate for the specified participant. The certificatePem field cannot be modified once the certificate is created. To maintain trust continuity across a certificate rotation, provide `linkCertificateInfo` to add this certificate as a successor to a previously uploaded certificate. Link certificates can only be added when the certificate is created, not when it is updated. - [Retrieve all participant verifier certificates](/docs/api-reference/platform/participants-verifier-certificates/retrieveParticipantVerifierCertificates.md): Retrieve all verifier certificates for the specified participant. - [Retrieve a participant verifier certificate](/docs/api-reference/platform/participants-verifier-certificates/retrieveParticipantVerifierCertificate.md): Retrieve a specific verifier certificate for the specified participant. - [Update a participant verifier certificate](/docs/api-reference/platform/participants-verifier-certificates/updateParticipantVerifierCertificate.md): Update a specific verifier certificate for the specified participant. - [Delete a participant verifier certificate](/docs/api-reference/platform/participants-verifier-certificates/deleteParticipantVerifierCertificate.md): Delete a specific verifier certificate for the specified participant. - **Policies** - Policy - [Publish policy](/docs/api-reference/platform/policy/createEcosystemPolicy.md): Publish a new version of the ecosystem policy. Only active and currently valid participants and IACA certificates are included in the policy. - [Retrieve latest ecosystem policy](/docs/api-reference/platform/policy/getLatestEcosystemPolicy.md): Retrieves the latest ecosystem policy by providing the ecosystem ID. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve ecosystem policy ⚠️](/docs/api-reference/platform/policy/getEcosystemPolicy.md) - [Retrieve ecosystem policy preview](/docs/api-reference/platform/policy/getEcosystemPolicyPreview.md): Retrieves an ecosystem policy preview by providing the Ecosystem's ID. A policy preview includes all the participants and credential types created in the ecosystem, excluding any participants with expired or inactive IACAs. - [Retrieve ecosystem policy](/docs/api-reference/platform/policy/getEcosystemPolicy.md): Retrieves an ecosystem policy by providing the ecosystem ID. This endpoint is intended for public consumption, and as such does not require authentication. - Issuer Policy - [Publish issuer policy](/docs/api-reference/platform/issuer-policy/createIssuerPolicy.md): Publish a new version of the ecosystem issuer policy. A participant is included only if it is active and has at least one issuer certificate that passes validation. Only the certificates that pass validation are included. - [Retrieve issuer policy preview](/docs/api-reference/platform/issuer-policy/getIssuerPolicyPreview.md): Retrieves an ecosystem issuer policy preview by providing the ecosystem's ID. A policy preview includes all the participants and their issuer certificates created in the ecosystem, including those that fail validation and would be excluded from a published policy. The validation result is provided for each certificate. - [Retrieve latest issuer policy](/docs/api-reference/platform/issuer-policy/getLatestIssuerPolicy.md): Retrieves the latest published ecosystem issuer policy by providing the ecosystem ID. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve issuer policy by ID](/docs/api-reference/platform/issuer-policy/getIssuerPolicyById.md): Retrieves a specific published ecosystem issuer policy by providing the ecosystem ID and the issuer policy ID. The issuer policy ID is the `id` returned when a policy is published, and is also included in the response from the [Retrieve latest issuer policy](#operation/getLatestIssuerPolicy) endpoint. This endpoint is intended for public consumption, and as such does not require authentication. - [Delete issuer policy](/docs/api-reference/platform/issuer-policy/deleteIssuerPolicy.md): Deletes a specific published ecosystem issuer policy by providing the ecosystem ID and the issuer policy ID. The issuer policy ID is the `id` returned when a policy is published, and is also included in the response from the [Retrieve latest issuer policy](#operation/getLatestIssuerPolicy) endpoint. - Verifier Policy - [Publish verifier policy](/docs/api-reference/platform/verifier-policy/createVerifierPolicy.md): Publish a new version of the ecosystem verifier policy. A participant is included only if it is active and has at least one verifier certificate that passes validation. Only the certificates that pass validation are included. - [Retrieve verifier policy preview](/docs/api-reference/platform/verifier-policy/getVerifierPolicyPreview.md): Retrieves an ecosystem verifier policy preview by providing the ecosystem's ID. A policy preview includes all the participants and their verifier certificates created in the ecosystem, including those that fail validation and would be excluded from a published policy. The validation result is provided for each certificate. - [Retrieve latest verifier policy](/docs/api-reference/platform/verifier-policy/getLatestVerifierPolicy.md): Retrieves the latest published ecosystem verifier policy by providing the ecosystem ID. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve verifier policy by ID](/docs/api-reference/platform/verifier-policy/getVerifierPolicyById.md): Retrieves a specific published ecosystem verifier policy by providing the ecosystem ID and the verifier policy ID. The verifier policy ID is the `id` returned when a policy is published, and is also included in the response from the [Retrieve latest verifier policy](#operation/getLatestVerifierPolicy) endpoint. This endpoint is intended for public consumption, and as such does not require authentication. - [Delete verifier policy by ID](/docs/api-reference/platform/verifier-policy/deleteVerifierPolicyById.md): Deletes a specific published ecosystem verifier policy by providing the ecosystem ID and the verifier policy ID. The verifier policy ID is the `id` returned when a policy is published, and is also included in the response from the [Retrieve latest verifier policy](#operation/getLatestVerifierPolicy) endpoint. - **VICAL** - General - [Create VICAL](/docs/api-reference/platform/vical/createVical.md): Creates a Verified Issuer Certificate Authority List (VICAL) based on the policy of the requested ecosystem. Refer to VICAL to learn more about the [VICAL](https://learn.mattr.global/docs/digital-trust-service/vical-overview) purpose and data structure. - [Retrieve all VICALs](/docs/api-reference/platform/vical/getVicals.md): Retrieves all VICALs available in the requested ecosystem. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve specific VICAL](/docs/api-reference/platform/vical/getVical.md): Retrieves a specific VICAL from the requested ecosystem by providing the VICAL version identifier. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve latest VICAL](/docs/api-reference/platform/vical/getLatestVical.md): Retrieves the latest VICAL from the requested ecosystem. This endpoint is intended for public consumption, and as such does not require authentication. - [Delete specific VICAL](/docs/api-reference/platform/vical/deleteVical.md): Deletes a specific VICAL from the requested ecosystem by providing the VICAL version identifier. Deleting a VICAL also deletes the issuer policy published from it, if one exists. This action cannot be undone. A `404` is only returned when the ecosystem does not exist. Deleting a `vicalIssueId` that does not exist within an existing ecosystem still returns `204`. - Configuration - [Update VICAL configuration](/docs/api-reference/platform/vical-configuration/updateVicalConfiguration.md): Update the VICAL configuration for the requested ecosystem - [Retrieve VICAL configuration](/docs/api-reference/platform/vical-configuration/getVicalConfiguration.md): Retrieve the VICAL configuration from the requested ecosystem - [Delete VICAL configuration](/docs/api-reference/platform/vical-configuration/deleteVicalConfiguration.md): Delete the VICAL configuration for the requested ecosystem - **RICAL** - General - [Create RICAL](/docs/api-reference/platform/rical/createRical.md): Creates a Reader Identity Certificate Authority List (RICAL) based on the policy of the requested ecosystem. A [RICAL configuration](#operation/updateRicalConfiguration) is required in order for RICALs to be created. - [Retrieve all RICALs](/docs/api-reference/platform/rical/getRicals.md): Retrieves all RICALs available in the requested ecosystem. The response is a JSON list of the published RICALs and their version identifiers. To download an actual RICAL file (a CBOR encoded file matching the RICAL format defined in ISO/IEC 18013-5), call the [Retrieve specific RICAL](#operation/getRical) or [Retrieve latest RICAL](#operation/getLatestRical) endpoint. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve specific RICAL](/docs/api-reference/platform/rical/getRical.md): Retrieves a specific RICAL from the requested ecosystem by providing the RICAL version identifier. The response is a CBOR encoded file matching the RICAL format defined in ISO/IEC 18013-5. This endpoint is intended for public consumption, and as such does not require authentication. - [Retrieve latest RICAL](/docs/api-reference/platform/rical/getLatestRical.md): Retrieves the latest RICAL from the requested ecosystem. The response is a CBOR encoded file matching the RICAL format defined in ISO/IEC 18013-5. This endpoint is intended for public consumption, and as such does not require authentication. - [Delete specific RICAL](/docs/api-reference/platform/rical/deleteRical.md): Deletes a specific RICAL from the requested ecosystem by providing the RICAL version identifier. Deleting a RICAL also deletes the verifier policy published from it, if one exists. This action cannot be undone. A `404` is only returned when the ecosystem does not exist. Deleting a `ricalIssueId` that does not exist within an existing ecosystem still returns `204`. - Configuration - [Update RICAL configuration](/docs/api-reference/platform/rical-configuration/updateRicalConfiguration.md): Update the RICAL configuration for the requested ecosystem. A RICAL configuration is required in order for RICALs to be created. - [Retrieve RICAL configuration](/docs/api-reference/platform/rical-configuration/getRicalConfiguration.md): Retrieve the RICAL configuration from the requested ecosystem. - [Delete RICAL configuration](/docs/api-reference/platform/rical-configuration/deleteRicalConfiguration.md): Delete the RICAL configuration for the requested ecosystem. - **βš™οΈ PLATFORM MANAGEMENT** - **General** - Analytics - [Retrieve events](/docs/api-reference/platform/analytics/getEvents.md): Returns a list of matching events from the tenant's event database. The `categories` and `types` parameters filter based on an **OR** logic, whilst all other parameters use an "AND" logic. For example `(categories OR types) AND requestIds AND dateFrom`. Refer to the [Events registry](https://api-reference-sdk.mattr.global/event-registry/latest/index.html) for an inclusive list of events categories and types. - [Create credential report](/docs/api-reference/platform/analytics/createCredentialReport.md): Creates a report of credential lifecycle operations (issuance and status changes). Only CWT and mDoc credentials are included in the report. - Messaging - [Sign a message](/docs/api-reference/platform/messaging/signMessage.md): Accepts a message payload and signs it with a JWS (JSON Web Signature) using the a specific key from the DID (Decentralized Identifier) provided in the request. - [Verify a message](/docs/api-reference/platform/messaging/verifyJws.md): Verifies the signature of a provided JWS (JSON Web Signature), validating that the payload has not been tampered with and verifying that the kid in the JWS header is the same as the `iss` value in the Request Object. One use case for verifying a JWS with a DID is when the Mobile Wallet App sends a Request Object to an OpenID Provider as part of the Authorization Code Flow (as per https://openid.net/specs/openid-connect-core-1_0-final.html#RequestObject). The Request Object is wrapped in a JWS with a signature that is generated from the Subject DID on the mobile app. Therefore verifying the JWS proves that the mobile app has access to the private key of the Subject DID. - [Encrypt a message](/docs/api-reference/platform/messaging/encryptMessage.md): Encrypts the provided payload using into a JWM (JSON Web Message) format. - [Decrypt a message](/docs/api-reference/platform/messaging/decryptMessage.md): Decrypts a provided message where the tenant manages the keys for the defined `recipientDidUrl`. - [Send a message](/docs/api-reference/platform/messaging/sendMessage.md): Sends an encrypted JWM (JSON Web Messaging) format message to a service endpoint defined in a public DID document. - Inboxes - [Create an inbox](/docs/api-reference/platform/inboxes/createInbox.md): Creates an inbox that can register DIDs and then hold messages sent to those DIDs service points. - [List inboxes](/docs/api-reference/platform/inboxes/getInboxes.md): Returns a list of all inboxes on the tenant. - [Retrieve an inbox](/docs/api-reference/platform/inboxes/getInbox.md): Retrieves an inbox based on its ID. - [Update an inbox](/docs/api-reference/platform/inboxes/updateInbox.md): Update the inbox configurations - [Delete an inbox](/docs/api-reference/platform/inboxes/deleteInbox.md): Deletes an inbox by providing its ID. - [Register DID with an inbox](/docs/api-reference/platform/inboxes/registerInboxDid.md): Register the provided DID to the requested inbox. DID registration with inboxes is currently limited to `did:key`' - [Retrieve inbox DIDs](/docs/api-reference/platform/inboxes/getInboxDids.md): Retrieves a list of all the DIDs registered with the requested inbox. - [Unregister DID with an inbox](/docs/api-reference/platform/inboxes/unregisterInboxDid.md): Unregisters a DID from the requested inbox. - [Retrieve all messages](/docs/api-reference/platform/inboxes/getInboxMessages.md): Retrieving all the messages from an inbox - [Retrieve a message](/docs/api-reference/platform/inboxes/getInboxMessage.md): Retrieves a message from the requested inbox by providing its ID. - [Delete a message](/docs/api-reference/platform/inboxes/deleteInboxMessage.md): Deletes a message from the requested inbox by providing its ID. - **Configuration** - Security - [Create API Auth Token](/docs/api-reference/platform/security/authToken.md): Authorization endpoint for gaining token used for API requests requiring `bearerAuth`. You will be provided the required `client_id` and `client_secret` as part of onboarding. The returned bearer token will only enable access to endpoints as per your client's defined role. Refer to [Access Control](https://learn.mattr.global/docs/platform-management/access-control) for more information. - Custom domain - [Configure custom domain](/docs/api-reference/platform/custom-domain/createCustomDomain.md): Creates a custom domain configuration on your tenant. You can configure a custom domain for a specific MATTR VII tenant to represent your brand and instil trust with your end-users. Any MATTR VII tenant can only have one custom domain. Refer to our [docs](https://learn.mattr.global/docs/platform-management/custom-domain-overview) for more information. - [Retrieve custom domain](/docs/api-reference/platform/custom-domain/retrieveCustomDomain.md): Returns your tenant's custom domain configuration and its verification status. - [Update custom domain](/docs/api-reference/platform/custom-domain/updateCustomDomain.md): Updates the custom domain configuration. - [Delete custom domain](/docs/api-reference/platform/custom-domain/removeCustomDomain.md): Deletes the custom domain configuration on your tenant. Deleting your custom domain configuration breaks the linkage with any credentials issued under the custom domain. These credentials will no longer be valid. - [Verify custom domain](/docs/api-reference/platform/custom-domain/verifyCustomDomain.md): Verifies that you have control of the configured custom domain by examining its TXT record. Your custom domain will not be active until you verify it. Refer to [Verify domain ownership](https://learn.mattr.global/docs/platform-management/custom-domain-overview#verify-domain-ownership) for more information. - Webhooks - [Create Webhook](/docs/api-reference/platform/webhooks/createWebhook.md): Creates a new webhook for this tenant. - [Retrieve all Webhooks](/docs/api-reference/platform/webhooks/getWebhooks.md): Retrieves a list of webhooks configured on the tenant. - [Retrieve Webhook](/docs/api-reference/platform/webhooks/getWebhook.md): Retrieve a specific Webhook by providing its ID. - [Update Webhook](/docs/api-reference/platform/webhooks/updateWebhook.md): Updates an existing Webhook by providing its ID. - [Delete Webhook](/docs/api-reference/platform/webhooks/deleteWebhook.md): Deletes a Webhook by providing its ID. - [Retrieve Webhook JWKs](/docs/api-reference/platform/webhooks/getWebhookJwks.md): Retrieves a list of Webhook JWKs (JSON Web Keys) from the tenant. These keys can be used to verify the HTTP signature and validate the integrity and authorship of generated Webhooks. This endpoint is intended for public consumption, and as such does not require authentication. - DIDs - [Create a DID](/docs/api-reference/platform/dids/createDid.md): Takes a supported [DID method](https://learn.mattr.global/docs/concepts/dids#methods) and returns a new DID with its generated keys and required information. This endpoint also registers the DID Document when applicable. MATTR VII currently supports creating DIDs of the following methods: - **did:key**: The most basic type of DID. The public key forms the DID and has no further data associated with it. - **did:web**: This type of DID requires hosting the DID document on a publicly accessible domain in order to make the document and its contents available. - [Retrieve a list of DIDs](/docs/api-reference/platform/dids/retrieveListOfDids.md): Returns a list of all DIDs (Decentralized Identifiers) managed by the tenant and their associated meta-data. - [Resolve a DID](/docs/api-reference/platform/dids/resolveDid.md): Retrieves a DID and its metadata from the tenant by its URI. This may involve a network call depending on the method involved: - For did:key the public key is encapsulated in the DID URI itself. - For did:web it must be resolved by accessing the `/.well-known/did.json` path on its domain. - [Delete a DID](/docs/api-reference/platform/dids/deleteDid.md): Deletes a DID and all associated metadata by providing its URI. This includes all the removal of all associated private keys from the Key Management System (KMS). For `did:web` you will need to manually remove the `did.json` from your hosted domain. - [Well known DID configuration](/docs/api-reference/platform/dids/wellKnownDidConfig.md): Returns a list of Decentralized Identifier (DID) Configuration entries from the tenant. These are automatically created for **all** DIDS created on a tenant so that they can be used by any party aiming to establish and verify the domain-DID linkage by exposing cryptographic proofs. Thus, this endpoint is unprotected, public facing and can be deterministically found at the root of the tenant subdomain or alias by any party. Refer to [Well Known DID Configuration](https://identity.foundation/.well-known/resources/did-configuration) on the Decentralized Identity Foundation website for more information. - **MATTR VII Management API** - [Overview](/docs/api-reference/management-api-reference-overview.md) - API Reference - Security - [Create API Auth Token](/docs/api-reference/management/security/authToken.md): Returns an API access token specific to the Management API. This token must then be used as an authorization header for all requests to protected endpoints (this is required for the majority of operations). - Security Settings - [Retrieve security settings](/docs/api-reference/management/security-settings/getSecuritySettings.md): Retrieves the current security settings for MATTR portal authentication. This endpoint is part of SaaS Security Posture Management (SSPM) support, an add-on feature that is currently available only for dedicated cloud deployments. It is only available when SSPM support is enabled in your environment. Contact us if you would like to enable it. - Environments - [Retrieve environments](/docs/api-reference/management/environments/getEnvironments.md): Retrieves a list of all available environments. - Tenants - [Create tenant](/docs/api-reference/management/tenants/createTenant.md): Creates a new tenant in the requested environment. - [Retrieve tenants](/docs/api-reference/management/tenants/getTenants.md): Retrieves a list of all available tenants. If you haven't created any tenants, the response will include an empty array. - [Retrieve all tenant roles](/docs/api-reference/management/tenants/getTenantsRoles.md): Retrieves all existing roles that can be assigned to a tenant member, with their associated permissions. - [Retrieve tenant](/docs/api-reference/management/tenants/getTenant.md): Retrieves a tenant by its ID. - [Delete tenant](/docs/api-reference/management/tenants/deleteTenant.md): Deletes a tenant by its ID. - Members - [Invite a tenant member](/docs/api-reference/management/members/inviteTenantMember.md): Invites a user to join the tenant and assigns roles to them within the tenant's context. If the user has not registered to the Self Service Portal yet, then they will receive an email with a link to accept the invite. If the user has already registered, then they will be added as a member to the tenant immediately. This endpoint can only be called by a Portal user that is a member of the tenant. Machine-to-machine (M2M) clients are not currently supported as inviters and will receive a `404 Resource Not Found` response, even when the client holds an `admin` role. This applies regardless of the role assigned, such as `admin`, `issuer`, or `dts-provider`. To invite members, use a Portal user that is a member of the target tenant. A reliable workflow is to create the tenant from the [MATTR Portal](/docs/platform-management/portal) rather than via an M2M client. The Portal user that creates the tenant becomes a member automatically, and can then invite additional users to it, either from the Portal UI or by calling this endpoint with the Portal user's access token. - [Retrieve tenant members](/docs/api-reference/management/members/getTenantMembers.md): Retrieves a list of all users that have access to the tenant. - [Retrieve a tenant member](/docs/api-reference/management/members/getTenantMember.md): Retrieves an existing user that has access to the tenant. - [Update a tenant membership](/docs/api-reference/management/members/updateTenantMembership.md): Updates the membership of a user in the tenant. This includes the roles assigned to this user for this tenant. - [Delete a tenant membership](/docs/api-reference/management/members/deleteTenantMembership.md): Removes the membership of a user from the specified tenant. This will remove all user permissions for this tenant. - Users - [Update user information](/docs/api-reference/management/users/updateUserInfo.md): Updates the information of the currently authenticated user. - [Retrieve user information](/docs/api-reference/management/users/getUserInfo.md): Retrieves information about the currently authenticated user. - Clients - [Create a client](/docs/api-reference/management/clients/createTenantClient.md): Creates a new client for the requested tenant. - [Retrieve clients](/docs/api-reference/management/clients/getTenantClients.md): Retrieves a list of clients authorized to interact with the requested tenant. - [Delete a client](/docs/api-reference/management/clients/deleteTenantClient.md): Deletes an existing client of the specified tenant. - Core concepts - [Overview](/docs/concepts.md) - **Verifiable credentials** - [Overview](/docs/concepts/verifiable-credentials.md) - [Decentralized trust model](/docs/concepts/decentralized-trust-model.md) - [Ecosystems](/docs/concepts/credential-ecosystem.md) - [Policy considerations](/docs/concepts/policy-considerations.md) - [Identity proofing](/docs/concepts/identity-proofing-and-holder-binding.md) - [Selective disclosure](/docs/concepts/selective-disclosure.md) - [mDL](/docs/concepts/mdl.md) - **ISO Standards** - [Overview](/docs/concepts/iso-mdoc-standards.md) - [mDocs](/docs/concepts/mdocs-beyond-mdl.md) - **MATTR products** - [Platforms](/docs/concepts/platforms.md) - [Capabilities](/docs/concepts/capabilities.md) - [Credential formats](/docs/concepts/formats-overview.md) - mDocs - [mDocs](/docs/concepts/mdocs.md) - [Core capabilities](/docs/concepts/mdocs/core-capabilities.md) - [Standards and technologies](/docs/concepts/mdocs/standards-and-technologies.md) - [Structure to function](/docs/concepts/mdocs/structure-to-function.md) - [MATTR platforms](/docs/concepts/mdocs/mattr.md) - CWT - [CWT credentials](/docs/concepts/cwt.md) - [Core capabilities](/docs/concepts/cwt/core-capabilities.md) - [Types](/docs/concepts/cwt/types.md) - [Data structure](/docs/concepts/cwt/data.md) - [Implementation](/docs/concepts/cwt/implementation.md) - [MATTR platforms](/docs/concepts/cwt/mattr.md) - [Privacy](/docs/concepts/privacy.md) - **Identifiers** - [Chain of trust](/docs/concepts/chain-of-trust.md): Learn how certificates form a chain of trust within MATTR's capabilities, providing assurance needed to validate digital artifacts such as credentials, identities, and verification requests. - [DIDs](/docs/concepts/dids.md) - **Glossary** - [Glossary](/docs/concepts/glossary.md) - Digital Trust Service - [Overview](/docs/digital-trust-service.md) - [Trusted Lists](/docs/digital-trust-service/trusted-lists.md): The categories of trust a Digital Trust Service publishes (trusted issuers, trusted readers, and trusted wallets) and why each one matters. - [DTS options](/docs/digital-trust-service/consuming-trust-overview.md): The options MATTR offers for publishing and consuming trust, and which category of trusted list each one serves. - [PKI and key management](/docs/digital-trust-service/pki.md): How MATTR VII's Public Key Infrastructure and key management underpin the Digital Trust Service, the certificate types involved, key protection options, and considerations for planning a deployment. - [DTS certificates](/docs/digital-trust-service/certificates-overview.md) - [FAQ](/docs/digital-trust-service/faq.md) - **Issuer trust lists (VICAL)** - [Overview](/docs/digital-trust-service/vical-overview.md) - [Guide](/docs/digital-trust-service/vical-guide.md) - [Consumption](/docs/digital-trust-service/vical-consumption.md) - API Reference - [General](/docs/digital-trust-service/vical-api-reference/general.md) - [Configuration](/docs/digital-trust-service/vical-api-reference/configuration.md) - [Signers](/docs/digital-trust-service/vical-api-reference/signers.md) - [DTS root and intermediate CA certificates](/docs/digital-trust-service/vical-api-reference/dts-root-ca-certificates.md) - **Reader trust lists (RICAL)** - [Overview](/docs/digital-trust-service/rical-overview.md) - [Guide](/docs/digital-trust-service/rical-guide.md) - [Consumption](/docs/digital-trust-service/rical-consumption.md) - API Reference - [General](/docs/digital-trust-service/rical-api-reference/general.md) - [Configuration](/docs/digital-trust-service/rical-api-reference/configuration.md) - [Signers](/docs/digital-trust-service/rical-api-reference/signers.md) - [DTS root and intermediate CA certificates](/docs/digital-trust-service/rical-api-reference/dts-root-ca-certificates.md) - **More** - [Privacy](/docs/digital-trust-service/privacy.md) - Credential Holding - **Getting started** - [Overview](/docs/holding.md) - [Quickstart](/docs/holding/sdk-quickstart.md) - SDK variants: [iOS](/docs/holding/sdk-quickstart.md?sdk=ios), [Android](/docs/holding/sdk-quickstart.md?sdk=android), [React Native](/docs/holding/sdk-quickstart.md?sdk=react-native) - [FAQ](/docs/holding/faq.md) - **Claim credentials** - [Overview](/docs/holding/credential-claiming-overview.md) - Journey patterns - [OID4VCI Authorization Code flow](/docs/holding/credential-claiming-journey-patterns/authorization-code-journey-pattern.md) - [OID4VCI Pre-authorized flow](/docs/holding/credential-claiming-journey-patterns/pre-authorized-code-journey-pattern.md) - [Tutorial](/docs/holding/credential-claiming-tutorial.md) - SDK variants: [iOS](/docs/holding/credential-claiming-tutorial.md?sdk=ios), [Android](/docs/holding/credential-claiming-tutorial.md?sdk=android), [React Native](/docs/holding/credential-claiming-tutorial.md?sdk=react-native) - [Trusted issuers](/docs/holding/trusted-issuers.md) - [URI scheme handling](/docs/holding/claiming-uri-scheme-handling.md) - SDK variants: [iOS](/docs/holding/claiming-uri-scheme-handling.md?sdk=ios), [Android](/docs/holding/claiming-uri-scheme-handling.md?sdk=android), [React Native](/docs/holding/claiming-uri-scheme-handling.md?sdk=react-native) - [Device Key Authentication](/docs/holding/device-key-authentication-guide.md) - SDK variants: [iOS](/docs/holding/device-key-authentication-guide.md?sdk=ios), [Android](/docs/holding/device-key-authentication-guide.md?sdk=android), [React Native](/docs/holding/device-key-authentication-guide.md?sdk=react-native) - [Revocation status check](/docs/holding/revocation-status-check.md) - SDK variants: [iOS](/docs/holding/revocation-status-check.md?sdk=ios), [Android](/docs/holding/revocation-status-check.md?sdk=android), [React Native](/docs/holding/revocation-status-check.md?sdk=react-native) - Wallet Attestation - [Overview](/docs/holding/wallet-attestation/overview.md): Learn how Wallet Attestation works in MATTR Holder SDKs to enable credential claiming from issuers that require trusted wallet applications. - [How to set up Wallet Attestation](/docs/holding/wallet-attestation/guide.md) - [PKI and key management](/docs/holding/wallet-attestation/pki.md): How MATTR VII's Public Key Infrastructure and key management underpin holding, the certificate types involved, key protection options, and considerations for planning a deployment. - Certificates - [Overview](/docs/holding/wallet-attestation/certificates/overview.md) - [Guide](/docs/holding/wallet-attestation/certificates/guide.md) - [Android app signing](/docs/holding/wallet-attestation/android-app-signing.md) - **Present credentials in-person** - [Overview](/docs/holding/proximity-presentation-overview.md) - [Journey pattern](/docs/holding/proximity-presentation-journey-pattern.md) - [Tutorial](/docs/holding/proximity-presentation-tutorial.md) - SDK variants: [iOS](/docs/holding/proximity-presentation-tutorial.md?sdk=ios), [Android](/docs/holding/proximity-presentation-tutorial.md?sdk=android), [React Native](/docs/holding/proximity-presentation-tutorial.md?sdk=react-native) - [Trusted verifiers](/docs/holding/proximity-verifier-authentication.md) - SDK variants: [iOS](/docs/holding/proximity-verifier-authentication.md?sdk=ios), [Android](/docs/holding/proximity-verifier-authentication.md?sdk=android), [React Native](/docs/holding/proximity-verifier-authentication.md?sdk=react-native) - [NFC device engagement](/docs/holding/nfc-engagement-guide.md) - SDK variants: [iOS](/docs/holding/nfc-engagement-guide.md?sdk=ios), [Android](/docs/holding/nfc-engagement-guide.md?sdk=android), [React Native](/docs/holding/nfc-engagement-guide.md?sdk=react-native) - **Present credentials remotely** - [Overview](/docs/holding/remote-presentation-overview.md) - Journey patterns - [Web](/docs/holding/remote-presentation-journey-patterns/web.md) - [Mobile](/docs/holding/remote-presentation-journey-patterns/mobile.md) - [Tutorial](/docs/holding/remote-presentation-tutorial.md) - SDK variants: [iOS](/docs/holding/remote-presentation-tutorial.md?sdk=ios), [Android](/docs/holding/remote-presentation-tutorial.md?sdk=android), [React Native](/docs/holding/remote-presentation-tutorial.md?sdk=react-native) - [Trusted verifiers](/docs/holding/remote-verifier-authentication.md) - SDK variants: [iOS](/docs/holding/remote-verifier-authentication.md?sdk=ios), [Android](/docs/holding/remote-verifier-authentication.md?sdk=android), [React Native](/docs/holding/remote-verifier-authentication.md?sdk=react-native) - [URI scheme handling](/docs/holding/remote-uri-scheme-handling.md) - SDK variants: [iOS](/docs/holding/remote-uri-scheme-handling.md?sdk=ios), [Android](/docs/holding/remote-uri-scheme-handling.md?sdk=android), [React Native](/docs/holding/remote-uri-scheme-handling.md?sdk=react-native) - DC API - [Overview](/docs/holding/dc-api/overview.md) - [Journey pattern](/docs/holding/dc-api/journey-pattern.md) - [Workflow](/docs/holding/dc-api/workflow.md) - [Guide (iOS)](/docs/holding/dc-api/guide-ios.md) - [Guide (Android)](/docs/holding/dc-api/guide-android.md) - [Guide (React Native)](/docs/holding/dc-api/guide-react-native.md) - **Holder SDK Operation** - [SDK Overview](/docs/holding/sdk-overview.md) - SDK variants: [iOS](/docs/holding/sdk-overview.md?sdk=ios), [Android](/docs/holding/sdk-overview.md?sdk=android), [React Native](/docs/holding/sdk-overview.md?sdk=react-native) - [Getting Started](/docs/holding/sdk-getting-started.md) - [SDK Backend](/docs/holding/sdk-backend.md) - [SDK Logging](/docs/holding/sdk-logging.md) - SDK variants: [iOS](/docs/holding/sdk-logging.md?sdk=ios), [Android](/docs/holding/sdk-logging.md?sdk=android), [React Native](/docs/holding/sdk-logging.md?sdk=react-native) - [Activity Logs](/docs/holding/activity-log.md) - SDK variants: [iOS](/docs/holding/activity-log.md?sdk=ios), [Android](/docs/holding/activity-log.md?sdk=android), [React Native](/docs/holding/activity-log.md?sdk=react-native) - Migration Guides - **iOS** - [6.0.0](/docs/holding/migration-guides/ios-6.0.0-migration-guide.md) - [5.0.0](/docs/holding/migration-guides/ios-5.0.0-migration-guide.md) - **Android** - [7.0.0](/docs/holding/migration-guides/android-7.0.0-migration-guide.md) - [6.0.0](/docs/holding/migration-guides/android-6.0.0-migration-guide.md) - **React Native** - [10.0.0 (⚠ Draft)](/docs/holding/migration-guides/react-native-10.0.0-migration-guide.md) - [9.0.0](/docs/holding/migration-guides/react-native-9.0.0-migration-guide.md) - Reference Docs - [React Native](https://api-reference-sdk.mattr.global/mobile-credential-holder-react-native/latest/index.html.md) - [iOS](https://api-reference-sdk.mattr.global/mobile-credential-holder-ios/latest/documentation/mobilecredentialholdersdk.md) - [Android](https://api-reference-sdk.mattr.global/mobile-credential-holder-android/latest/.md) - **More** - [OID4VCI feature support](/docs/holding/oid4vci-feature-support.md): A feature-by-feature reference for how the MATTR Pi Holder SDKs support the OpenID for Verifiable Credential Issuance (OID4VCI) v1.0 specification when claiming credentials from an issuer. - [OID4VP feature support](/docs/holding/oid4vp-feature-support.md) - GO Hold - [Getting Started](/docs/holding/go-hold/getting-started.md) - [SDK or ready-made wallet?](/docs/holding/go-hold/sdk-or-wallet.md) - [Libraries](/docs/holding/go-hold/libraries.md) - [System requirements](/docs/holding/go-hold/system-requirements.md) - [Privacy](/docs/holding/privacy.md) - Credentials Issuance - **Getting started** - [Overview](/docs/issuance.md) - [Quickstart](/docs/issuance/quickstart.md) - [FAQ](/docs/issuance/faq.md) - **Issuing Credentials** - [Choose a credential type](/docs/issuance/choose-credential-type.md): Choose between mDocs and CWT credential formats for issuance with MATTR VII, and understand which use cases suit each. - [Choose an issuance flow](/docs/issuance/choose-issuance-flow.md): Compare the OID4VCI Pre-authorized Code and Authorization Code flows in MATTR VII, and choose the one that fits how your holders authenticate. - Pre-authorized Code flow - [Overview](/docs/issuance/pre-authorized-code/overview.md) - [Journey pattern](/docs/issuance/pre-authorized-code/journey-pattern.md) - [Quickstart](/docs/issuance/pre-authorized-code/quickstart.md) - [Tutorial](/docs/issuance/pre-authorized-code/tutorial.md) - [API Reference](/docs/issuance/pre-authorized-code/api-reference.md) - Authorization Code flow - [Overview](/docs/issuance/authorization-code/overview.md) - [Journey pattern](/docs/issuance/authorization-code/journey-pattern.md) - [Quickstart](/docs/issuance/authorization-code/quickstart.md) - [Tutorial](/docs/issuance/authorization-code/tutorial.md) - [API Reference](/docs/issuance/authorization-code/api-reference.md) - Authentication provider - [Overview](/docs/issuance/authorization-code/authentication-provider/overview.md) - [Guide](/docs/issuance/authorization-code/authentication-provider/guide.md) - [API Reference](/docs/issuance/authorization-code/authentication-provider/api-reference.md) - Interaction hook - [Overview](/docs/issuance/authorization-code/interaction-hook/overview.md) - [Guide](/docs/issuance/authorization-code/interaction-hook/guide.md) - [Tutorial](/docs/issuance/authorization-code/interaction-hook/tutorial.md) - [API Reference](/docs/issuance/authorization-code/interaction-hook/api-reference.md) - [PKI and key management](/docs/issuance/pki.md): How MATTR VII's Public Key Infrastructure and key management underpin issuance, the certificate types involved, key protection options, and considerations for planning a deployment. - Certificates - [Overview](/docs/issuance/certificates/overview.md) - [Guide](/docs/issuance/certificates/guide.md) - [Revoke signing certificates](/docs/issuance/certificates/revoke-signing-certificates.md) - API Reference - [IACA](/docs/issuance/certificates/api-reference/iaca.md) - [Document signers](/docs/issuance/certificates/api-reference/document-signers.md) - [Issuer metadata](/docs/issuance/certificates/api-reference/issuer-metadata.md) - Credential configuration - [Overview](/docs/issuance/credential-configuration/overview.md) - [Guide](/docs/issuance/credential-configuration/guide.md) - [ISO-compliant credentials](/docs/issuance/credential-configuration/iso-compliant-credentials.md) - API Reference - [mDocs Credentials](/docs/issuance/credential-configuration/api-reference/mdocs.md) - [CWT Credentials](/docs/issuance/credential-configuration/api-reference/cwt.md) - [Semantic CWT Credentials](/docs/issuance/credential-configuration/api-reference/semantic-cwt.md) - Claims source - [Overview](/docs/issuance/claims-source/overview.md) - [Guide](/docs/issuance/claims-source/guide.md) - [Tutorial](/docs/issuance/claims-source/tutorial.md) - [API Reference](/docs/issuance/claims-source/api-reference.md) - Credential offer - [Overview](/docs/issuance/credential-offer/overview.md) - [Guide](/docs/issuance/credential-offer/guide.md) - [API Reference](/docs/issuance/credential-offer/api-reference.md) - Credential issuance - [Overview](/docs/issuance/credential-issuance/overview.md) - [API Reference](/docs/issuance/credential-issuance/api-reference.md) - Trusted Holder Apps - [Overview](/docs/issuance/trusted-holder-apps/overview.md) - [Wallet Attestation](/docs/issuance/trusted-holder-apps/wallet-attestation.md) - [End-to-End Encryption](/docs/issuance/trusted-holder-apps/e2e-encryption.md) - Webhooks - [Overview](/docs/issuance/webhooks/overview.md) - [Guide](/docs/issuance/webhooks/guide.md) - [Tutorial](/docs/issuance/webhooks/tutorial.md) - [API Reference](/docs/issuance/webhooks/api-reference.md) - **Managing Issued Credentials** - Users - [Overview](/docs/issuance/users/overview.md) - [Guide](/docs/issuance/users/guide.md) - [API Reference](/docs/issuance/users/api-reference.md) - Revocation - [Overview](/docs/issuance/revocation/overview.md) - [Journey pattern](/docs/issuance/revocation/journey-pattern.md) - [Tutorial](/docs/issuance/revocation/tutorial.md) - [Guide](/docs/issuance/revocation/guide.md) - API Reference - **mDocs** - [Status List Configuration](/docs/issuance/revocation/api-reference/mdocs-status-list-configuration.md) - [Status List retrieval](/docs/issuance/revocation/api-reference/mdocs-status-list-retrieval.md) - [Status List Signers](/docs/issuance/revocation/api-reference/mdocs-status-list-signers.md) - [Status update](/docs/issuance/revocation/api-reference/mdocs-status-update.md) - **CWT Credentials** - [Revocation lists](/docs/issuance/revocation/api-reference/cwt-revocation-lists.md) - [Status update](/docs/issuance/revocation/api-reference/cwt-status-update.md) - **Semantic CWT Credentials** - [Revocation lists](/docs/issuance/revocation/api-reference/semantic-cwt-revocation-lists.md) - [Status update](/docs/issuance/revocation/api-reference/semantic-cwt-status-update.md) - Credential Refresh - [Overview](/docs/issuance/refresh/overview.md) - Credential Reports - [Guide](/docs/issuance/credential-reports/guide.md) - **Direct Issuance** - [Overview](/docs/issuance/direct-issuance-overview.md) - [Journey pattern](/docs/issuance/issuance-journey-pattern-direct.md) - [Issue a CWT Credential](/docs/issuance/cwt-direct-issuance.md) - CWT Credential Templates - [Create a PDF template](/docs/issuance/cwt-credential-templates/pdf-templates.md) - [Create a Google digital pass template](/docs/issuance/cwt-credential-templates/google-templates.md) - [Create an Apple digital pass template](/docs/issuance/cwt-credential-templates/apple-templates.md) - API Reference - **CWT Credentials** - [Issuance](/docs/issuance/direct-issuance-api-reference/cwt-issuance.md) - [PDF templates](/docs/issuance/direct-issuance-api-reference/cwt-pdf-templates.md) - [Apple Pass templates](/docs/issuance/direct-issuance-api-reference/cwt-apple-pass-templates.md) - [Google Pass templates](/docs/issuance/direct-issuance-api-reference/cwt-google-pass-templates.md) - **Semantic CWT Credentials** - [Issuance](/docs/issuance/direct-issuance-api-reference/semantic-cwt-issuance.md) - [PDF templates](/docs/issuance/direct-issuance-api-reference/semantic-cwt-pdf-templates.md) - [Apple Pass templates](/docs/issuance/direct-issuance-api-reference/semantic-cwt-apple-pass-templates.md) - [Google Pass templates](/docs/issuance/direct-issuance-api-reference/semantic-cwt-google-pass-templates.md) - **More** - [Feature support](/docs/issuance/oid4vci-feature-support.md) - [Privacy](/docs/issuance/privacy.md) - Platform Management - **Overview** - [Platform Management](/docs/platform-management.md) - [Environments and Tenants](/docs/platform-management/environments-and-tenants.md) - **Management tools** - [MATTR Portal](/docs/platform-management/portal.md) - Management API - [Overview](/docs/platform-management/management-api/overview.md) - [API Reference](/docs/api-reference/management-api-reference-overview.md) - [Events registry](https://api-reference-sdk.mattr.global/event-registry-management/latest/index.html.md) - **Access control** - [Overview](/docs/platform-management/access-control.md) - [Roles and permissions](/docs/platform-management/roles-and-permissions.md) - [Tutorial](/docs/platform-management/access-control-tutorial.md) - [Create a client](/docs/platform-management/create-client.md) - **Analytics and monitoring** - Analytics - [Overview](/docs/platform-management/analytics/overview.md) - [Guide](/docs/platform-management/analytics/guide.md) - [API Reference](/docs/platform-management/analytics/api-reference.md) - [Platform Events registry](https://api-reference-sdk.mattr.global/event-registry/latest/index.html.md) - [Management Events registry](https://api-reference-sdk.mattr.global/event-registry-management/latest/index.html.md) - [SSPM](/docs/platform-management/sspm.md) - **Custom domain** - [Overview](/docs/platform-management/custom-domain-overview.md) - [Guide](/docs/platform-management/custom-domain-guide.md) - [API Reference](/docs/platform-management/custom-domain-api-reference.md) - Resources - [Overview](/docs/resources.md) - [Getting started](/docs/resources/get-started.md) - [Reference Docs](/docs/resources/reference-docs.md) - [Developer toolbox](/docs/resources/dev-toolbox.md) - Changelog - [MATTR Changelogs](/docs/resources/changelog.md) - [VII](/docs/resources/changelog/vii.md) - [Pi](/docs/resources/changelog/pi.md) - [GO](/docs/resources/changelog/go.md) - [Release Newsletter](/docs/resources/changelog/newsletter-signup.md) - Standards - [Supported](/docs/resources/standards/supported.md) - [Upcoming](/docs/resources/standards/upcoming.md) - Terms - [Terms and Conditions](/docs/resources/terms.md) - Customer Agreement - [MATTR Customer Agreement](/docs/resources/terms/customer-agreement.md) - [Latest](/docs/resources/terms/customer-agreement.md) - [Recent changes](/docs/resources/terms/customer-agreement/recent-changes.md) - **Previous versions** - [30 June 2022](/docs/resources/terms/customer-agreement/30-6-22.md) - [20 April 2022](/docs/resources/terms/customer-agreement/20-4-22.md) - [25 March 2021](/docs/resources/terms/customer-agreement/25-3-21.md) - Service Level Agreement - [MATTR Service Level Agreement](/docs/resources/terms/service-level-agreement.md) - [Latest](/docs/resources/terms/service-level-agreement.md) - Privacy Policy - [MATTR Privacy Policy](/docs/resources/terms/privacy-policy.md) - [Latest](/docs/resources/terms/privacy-policy.md) - [Recent changes](/docs/resources/terms/privacy-policy/recent-changes.md) - **Previous versions** - [17 October 2025](/docs/resources/terms/privacy-policy/17-10-25.md) - [5 November 2024](/docs/resources/terms/privacy-policy/5-11-24.md) - [10 November 2022](/docs/resources/terms/privacy-policy/10-11-22.md) - [9 December 2021](/docs/resources/terms/privacy-policy/9-12-21.md) - [25 March 2021](/docs/resources/terms/privacy-policy/25-3-21.md) - Data Processing Terms - [MATTR Data Processing Terms](/docs/resources/terms/data-processing-terms.md) - [Latest](/docs/resources/terms/data-processing-terms.md) - [Recent changes](/docs/resources/terms/data-processing-terms/recent-changes.md) - Data Sub-Processors - [MATTR Data Sub-processors](/docs/resources/terms/data-sub-processors.md) - [Latest](/docs/resources/terms/data-sub-processors.md) - [Recent changes](/docs/resources/terms/data-sub-processors/recent-changes.md) - **Previous versions** - [15 April 2026](/docs/resources/terms/data-sub-processors/15-4-26.md) - [23 March 2026](/docs/resources/terms/data-sub-processors/23-3-26.md) - [2 February 2026](/docs/resources/terms/data-sub-processors/2-2-26.md) - [17 October 2025](/docs/resources/terms/data-sub-processors/17-10-25.md) - [8 November 2024](/docs/resources/terms/data-sub-processors/8-11-24.md) - [28 May 2024](/docs/resources/terms/data-sub-processors/28-5-24.md) - [25 March 2024](/docs/resources/terms/data-sub-processors/25-3-24.md) - [16 May 2023](/docs/resources/terms/data-sub-processors/16-5-23.md) - Website Terms of Use - [Website Terms of Use](/docs/resources/terms/website-terms-of-use.md) - [Latest](/docs/resources/terms/website-terms-of-use.md) - [Recent changes](/docs/resources/terms/website-terms-of-use/recent-changes.md) - MATTR Pi SDK Licence Agreement - [MATTR Pi SDK Trial Licence Agreement](/docs/resources/terms/sdk-licence-agreement.md) - [Latest](/docs/resources/terms/sdk-licence-agreement.md) - MATTR GO Applications - [Terms of Use](/docs/resources/terms/go-applications/terms-of-use.md) - [Accessibility Statement](/docs/resources/terms/go-applications/accessibility-statement.md) - [Pilots](/docs/resources/terms/go-applications/pilots.md) - [Recent changes](/docs/resources/terms/go-applications/recent-changes.md) - **Previous versions** - [23 September 2022](/docs/resources/terms/go-applications/23-9-22.md) - [15 September 2020](/docs/resources/terms/go-applications/15-9-20.md) - Credentials Verification - **Getting started** - [Overview](/docs/verification.md) - [Quickstart](/docs/verification/quickstart.md) - [FAQ](/docs/verification/faq.md) - **In-person verification** - [Overview](/docs/verification/in-person-overview.md) - Journey patterns - [mDocs](/docs/verification/in-person-journey-patterns/mdocs.md) - [CWT credentials](/docs/verification/in-person-journey-patterns/cwt.md) - [Quickstart](/docs/verification/in-person-quickstart.md) - SDK variants: [iOS](/docs/verification/in-person-quickstart.md?sdk=ios), [Android](/docs/verification/in-person-quickstart.md?sdk=android), [React Native](/docs/verification/in-person-quickstart.md?sdk=react-native) - [Tutorial](/docs/verification/in-person-tutorial.md) - SDK variants: [iOS](/docs/verification/in-person-tutorial.md?sdk=ios), [Android](/docs/verification/in-person-tutorial.md?sdk=android), [React Native](/docs/verification/in-person-tutorial.md?sdk=react-native) - [Trusted issuers](/docs/verification/in-person-trusted-issuers.md) - SDK variants: [iOS](/docs/verification/in-person-trusted-issuers.md?sdk=ios), [Android](/docs/verification/in-person-trusted-issuers.md?sdk=android), [React Native](/docs/verification/in-person-trusted-issuers.md?sdk=react-native) - [Revocation status check](/docs/verification/in-person-revocation-status-check.md) - SDK variants: [iOS](/docs/verification/in-person-revocation-status-check.md?sdk=ios), [Android](/docs/verification/in-person-revocation-status-check.md?sdk=android), [React Native](/docs/verification/in-person-revocation-status-check.md?sdk=react-native) - [Handling verification results](/docs/verification/in-person-handling-verification-results.md) - **Remote verification** - [Overview](/docs/verification/remote-overview.md) - [Trusted issuers](/docs/verification/remote-trusted-issuers.md) - Signing verification requests - [Overview](/docs/verification/signing-verification-requests/overview.md) - [PKI and key management](/docs/verification/signing-verification-requests/pki.md): How MATTR VII's Public Key Infrastructure and key management underpin verification, the certificate types involved, key protection options, and considerations for planning a deployment. - [Guide](/docs/verification/signing-verification-requests/guide.md) - [Android app signing](/docs/verification/signing-verification-requests/android-app-signing.md) - **> Web App Verification** - [Journey pattern](/docs/verification/remote-web-verifiers/journey-pattern.md) - IDV Integration patterns - [Onboarding](/docs/verification/remote-web-verifiers/idv-integration-patterns/onboarding.md) - [Login](/docs/verification/remote-web-verifiers/idv-integration-patterns/login.md) - [Embedded Web App](/docs/verification/remote-web-verifiers/idv-integration-patterns/embedded.md) - [Step-up verification](/docs/verification/remote-web-verifiers/idv-integration-patterns/step-up-verification.md) - [Workflow](/docs/verification/remote-web-verifiers/workflow.md) - [Quickstart](/docs/verification/remote-web-verifiers/quickstart.md) - [Tutorial](/docs/verification/remote-web-verifiers/tutorial.md) - [Handling URI schemes](/docs/verification/remote-web-verifiers/oid4vp-wallet-interactions.md) - [Handling verification results](/docs/verification/remote-web-verifiers/handling-verification-results.md) - [Correlating verification sessions](/docs/verification/remote-web-verifiers/correlating-verification-sessions.md) - DC API - [Overview](/docs/verification/remote-web-verifiers/dc-api/overview.md) - [Journey pattern](/docs/verification/remote-web-verifiers/dc-api/journey-pattern.md) - [Workflow](/docs/verification/remote-web-verifiers/dc-api/workflow.md) - [Guide](/docs/verification/remote-web-verifiers/dc-api/guide.md) - Verifier Web SDK - [Overview](/docs/verification/remote-web-verifiers/sdks/overview.md) - [Reference Docs](https://api-reference-sdk.mattr.global/verifier-sdk-web/latest/index.html.md) - **> Mobile App Verification** - [Journey pattern](/docs/verification/remote-mobile-verifiers/journey-pattern.md) - [Workflow](/docs/verification/remote-mobile-verifiers/workflow.md) - [Quickstart](/docs/verification/remote-mobile-verifiers/quickstart.md) - SDK variants: [iOS](/docs/verification/remote-mobile-verifiers/quickstart.md?sdk=ios), [Android](/docs/verification/remote-mobile-verifiers/quickstart.md?sdk=android), [React Native](/docs/verification/remote-mobile-verifiers/quickstart.md?sdk=react-native) - [Tutorial](/docs/verification/remote-mobile-verifiers/tutorial.md) - SDK variants: [iOS](/docs/verification/remote-mobile-verifiers/tutorial.md?sdk=ios), [Android](/docs/verification/remote-mobile-verifiers/tutorial.md?sdk=android), [React Native](/docs/verification/remote-mobile-verifiers/tutorial.md?sdk=react-native) - [Handling verification results](/docs/verification/remote-mobile-verifiers/handling-verification-results.md) - [Verify with Apple Wallet](/docs/verification/remote-mobile-verifiers/verify-with-apple-wallet.md) - SDK variants: [iOS](/docs/verification/remote-mobile-verifiers/verify-with-apple-wallet.md?sdk=ios), [React Native](/docs/verification/remote-mobile-verifiers/verify-with-apple-wallet.md?sdk=react-native) - **Verifier Mobile SDK** - [Overview](/docs/verification/verifier-sdk/overview.md) - [Getting Started](/docs/verification/verifier-sdk/sdk-getting-started.md) - SDK variants: [iOS](/docs/verification/verifier-sdk/sdk-getting-started.md?sdk=ios), [Android](/docs/verification/verifier-sdk/sdk-getting-started.md?sdk=android), [React Native](/docs/verification/verifier-sdk/sdk-getting-started.md?sdk=react-native) - [SDK Backend](/docs/verification/verifier-sdk/sdk-backend.md) - SDK variants: [iOS](/docs/verification/verifier-sdk/sdk-backend.md?sdk=ios), [Android](/docs/verification/verifier-sdk/sdk-backend.md?sdk=android), [React Native](/docs/verification/verifier-sdk/sdk-backend.md?sdk=react-native) - [SDK Logging](/docs/verification/verifier-sdk/sdk-logging.md) - Reference Docs - [React Native](https://api-reference-sdk.mattr.global/mobile-credential-verifier-react-native/latest/index.html.md) - [iOS](https://api-reference-sdk.mattr.global/mobile-credential-verifier-ios/latest/documentation/mobilecredentialverifiersdk.md) - [Android](https://api-reference-sdk.mattr.global/mobile-credential-verifier-android/latest/.md) - Migration Guides - **iOS** - [6.0.0](/docs/verification/verifier-sdk/migration-guides/ios-6.0.0-migration-guide.md) - [5.0.0](/docs/verification/verifier-sdk/migration-guides/ios-5.0.0-migration-guide.md) - **Android** - [7.0.0](/docs/verification/verifier-sdk/migration-guides/android-7.0.0-migration-guide.md) - [6.0.0](/docs/verification/verifier-sdk/migration-guides/android-6.0.0-migration-guide.md) - **React Native** - [9.0.0](/docs/verification/verifier-sdk/migration-guides/react-native-9.0.0-migration-guide.md) - **More** - [OID4VP](/docs/verification/oid4vp.md) - [OID4VP feature support](/docs/verification/oid4vp-feature-support.md) - GO Verify - [Getting Started](/docs/verification/go-verify/getting-started.md) - [Libraries](/docs/verification/go-verify/libraries.md) - [System requirements](/docs/verification/go-verify/system-requirements.md) - [Privacy](/docs/verification/privacy.md) ## Full Documentation - [Complete documentation in LLM-optimized format](/llms-full.txt): All documentation pages concatenated for comprehensive context