Browse credential presets

List credential presets

Every public preset on the platform is available to you, with no setup and no permissions to request, alongside any private presets your own tenant has published. Listing returns the current catalogue; pick the one that matches what you want to issue. The API exposes a separate listing per credential format. Use the one for the format you’re after, or the generic listing if you want everything in one call:

GET /v1/presets/credentials/sd-jwt returns SD-JWT presets only.
GET /v1/presets/credentials/mdoc returns mDoc presets only.
GET /v1/presets/credentials returns both formats together.

curl -X GET "$BASE_URL/me-creds/api/v1/presets/credentials/sd-jwt" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Narrow by namespace

All three listings accept an optional namespace query parameter:

Query	Returns
(omitted)	Every public preset, plus your own private ones
`?namespace=public`	The shared catalogue only
`?namespace=private`	Only presets your tenant authored privately

Private presets belonging to other tenants never appear, whichever you use. See public and private presets. A trimmed example entry:

{
  "credentialFormat": "sd-jwt",
  "id": "didx:basic-identity",
  "author": "didx",
  "code": "basic-identity",
  "templateName": "Basic Identity Credential",
  "templateType": "https://test.didxtech.com/vct/didx/basic-identity",
  "templateDescription": "Standard basic identity credential",
  "templateAttributes": {
    "firstName": {
      "type": "string",
      "name": "First Name",
      "required": true,
      "alwaysDisclosed": false
    },
    "lastName": {
      "type": "string",
      "name": "Last Name",
      "required": true,
      "alwaysDisclosed": false
    }
  },
  "issuerConfig": { "signer": "did:web" }
}

What to look at

Field	What it tells you
`id`	Pass this as `presetId` when issuing
`author`	The publisher’s tenant alias (for example `didx`)
`templateName`, `templateDescription`	Human-readable summary
`credentialFormat`	`sd-jwt` or `mdoc`. Determines which wallets and verifiers can use the credential
`templateAttributes`	The keys you supply under `attributes` when issuing
`templateAttributes.*.required`	Whether you must supply that key
`templateAttributes.*.alwaysDisclosed`	If `true`, the wallet shares the value whenever the holder presents the credential

Inspect a single preset

When you’ve found a candidate, fetch it directly. The same format split applies. Use GET /v1/presets/credentials/sd-jwt/:id for SD-JWT, GET /v1/presets/credentials/mdoc/:id for mDoc, or GET /v1/presets/credentials/:id for the generic lookup:

curl -X GET "$BASE_URL/me-creds/api/v1/presets/credentials/sd-jwt/didx:basic-identity" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

What if nothing fits?

Publish your own: Create an SD-JWT credential preset or Create an mDoc credential preset.
Or define a one-off: Custom credential template.

Overview

User Onboarding

Issuance

Verification

Branding

Webhooks

Custom Templates (advanced)

Errors

List credential presets

Narrow by namespace

What to look at

Inspect a single preset

What if nothing fits?

​List credential presets

​Narrow by namespace

​What to look at

​Inspect a single preset

​What if nothing fits?

List credential presets

Narrow by namespace

What to look at

Inspect a single preset

What if nothing fits?