Create verifier application

POST/v2/presentations/applications

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).

Analytic events

CREDENTIAL_PRESENTATION_VERIFIER_APPLICATION_CREATE_START
CREDENTIAL_PRESENTATION_VERIFIER_APPLICATION_CREATE_SUCCESS
CREDENTIAL_PRESENTATION_VERIFIER_APPLICATION_CREATE_FAIL

Authorization

bearerAuth

AuthorizationBearer <token>

In: header

Request Body

application/json

Verifier application payload

TypeScript Definitions

Use the request body type in TypeScript.

Configuration for an mDocs online verifier application.

Configuration for an mDocs online verifier web application. Either OID4VP or Digital Credentials API configuration must be provided.

name?string

Unique name to identify the verifier application.

type*"web"

Defines the type of the verifier application.

Value in

"web"

domain*string

Fully qualified domain name of verifier application that can create an online presentation session. This ensures the verifier tenant only accepts requests from known and trusted applications. Note that localhost is not supported. Use local tunneling services for testing.

additionalDomains?array<string>

List of fully qualified domain names of additional verifier applications who can create an online presentation session.

Items1 <= items

openid4vpConfiguration?

Configuration settings that enable verification using OID4VP.

At least one of openid4vpConfiguration or dcApiConfiguration must be provided.

dcApiConfiguration?

Configuration settings that enable verification using the Digital Credentials API.

At least one of openid4vpConfiguration or dcApiConfiguration must be provided.

DC API support is currently offered as a tech preview. As such, functionality may be limited, may not work in all scenarios, and could change or break without prior notice.

resultAvailableInFrontChannel?boolean

Indicates whether or not the verification result should be returned directly to the verifier application (true) or only via a configured back-end (false). Refer to the detailed workflow for more information.

Defaulttrue

Response Body

`application/json`

curl -X POST "https://example.com/v2/presentations/applications" \  -H "Content-Type: application/json" \  -d '{    "name": "string",    "type": "web",    "domain": "string"  }'

{  "id": "string",  "name": "string",  "type": "web",  "domain": "string",  "additionalDomains": [    "string"  ],  "openid4vpConfiguration": {    "supportedModes": "all",    "redirectUris": [      "string"    ],    "display": {      "logoImage": {        "url": "string",        "altText": "string"      },      "headerText": "string",      "bodyText": "string",      "privacyPolicyUrl": "string",      "primaryColorHex": "string"    }  },  "dcApiConfiguration": {    "supportedBrowserPlatforms": {      "desktop": true,      "mobile": true    }  },  "resultAvailableInFrontChannel": true}

Create verifier application

Roles

Analytics Events

Analytic events

Authorization

Request Body

Response Body

`application/json`

`application/json`

Create verifier application

Roles

Analytics Events

Analytic events

Authorization

Request Body

Response Body

201application/json

400application/json

`application/json`

`application/json`