Credential Designs: EuPid and Mdl

A credential design defines a credential type: its format bindings, its claims with display labels, and per-claim policy such as selective disclosure. This walkthrough creates two designs through the credential-design API (API reference):

• EuPid, a European personal identity credential in dc+sd-jwt format, bound by its verifiable credential type (vct) and credential configuration id.
• Mdl, a mobile driving licence in mso_mdoc format, bound by the ISO 18013-5 doctype org.iso.18013.5.1.mDL.

EuPid (SD-JWT)

SD-JWT claims carry an sdPolicy. Claims marked ALWAYS are selectively disclosable: the holder chooses whether to reveal them at presentation time. Here family name, given name, and issuing country are disclosable while date of birth and nationality are always present:

• Overview
• Request
• Response

01 Create EuPid SD-JWT design

Endpoint: POST /api/credential-design/v1/designs/credentials

Captured response: 201 Created

This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.

Mdl (ISO mdoc)

mdoc claims are namespace-qualified: every claim path starts with the ISO 18013-5 namespace. The portrait is transported as base64 image data and driving privileges as a structured array:

• Overview
• Request
• Response

02 Create Mdl mdoc design

Endpoint: POST /api/credential-design/v1/designs/credentials

Captured response: 201 Created

This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.

Listing designs

• Overview
• Request
• Response

03 List credential designs

Endpoint: GET /api/credential-design/v1/designs/credentials

Captured response: 200 OK

This captured endpoint is shown from the E2E run; it is not mapped to one of the generated EDK REST API reference pages.

Next, create the status list that revocation will use.