Templates and catalogues

List credential categories

GET/v4/config/ows/issuer/credential-categories

Lists the credential categories: the eIDAS category under which a credential configuration issues its credentials (EAA, QEAA, PuB-EAA, mDL or PID). For each category: what the certificate of the signing key must have, the certificate preset to request, the entitlement of the provider (ETSI TS 119 475 Annex A.2), the EAA category claim that the issuer adds, and the sources of the rules.

Put the id in credentialConfigurations[].credentialCategory of Create credential definition. The issuer compares the certificate of the signing key of a configuration with the rules of its category and shows the result in signingKeyCheck of the configuration. The result is information: the create and update calls save a configuration whose signing key does not fit its category. The list is the same for every organisation.

Language of the request sample

curl 'https://demo-api.igrant.io/v4/config/ows/issuer/credential-categories' \
  -H 'Authorization: ApiKey <your-api-key>'

{
  "credentialCategories": [
    {
      "id": "eaa",
      "name": "EAA (non-qualified attestation)",
      "description": "An electronic attestation of attributes that is not qualified, for example a membership card or a ticket. Any organisation can issue it as a non-qualified trust service. It needs an electronic seal certificate.",
      "certificateRequirements": [
        "keyUsage type A, B or F (ETSI EN 319 412-2 table 1: nonRepudiation, with digitalSignature or also with keyEncipherment or keyAgreement)",
        "organizationIdentifier in the subject"
      ],
      "presetId": "eaa-provider",
      "mdocPresetId": "eaa-provider-mdoc",
      "entitlement": "Non_Q_EAA_Provider",
      "eaaCategory": null,
      "sources": [
        "ETSI TS 119 412-6 V1.2.1 clause 6 (EAA provider)",
        "ETSI EN 319 412-3 V1.4.1 LEG-4.3.1-3 (keyUsage type A, B or F for a seal over content)",
        "ETSI EN 319 412-3 V1.4.1 LEG-4.2.1-2 (organizationIdentifier)",
        "ETSI TS 119 472-1 V1.2.1 EAA-5.2.2.1-01 and EAA-6.2.2.1-01 (no category claim)",
        "ETSI TS 119 475 V1.2.1 A.2.3 (Non_Q_EAA_Provider)"
      ]
    },
    {
      "id": "qeaa",
      "name": "QEAA (qualified attestation)",
      "description": "A qualified electronic attestation of attributes. Only a qualified trust service provider (QTSP) can issue it, and it has the same legal effect as a lawfully issued paper attestation. It needs a qualified seal certificate. The platform adds the ETSI category urn:etsi:esi:eaa:eu:qualified.",
      "certificateRequirements": [
        "QcCompliance statement (0.4.0.1862.1.1)",
        "QcSSCD statement (0.4.0.1862.1.4)",
        "QcType id-etsi-qct-eseal (0.4.0.1862.1.6.2)",
        "keyUsage type A, B or F (ETSI EN 319 412-2 table 1: nonRepudiation, with digitalSignature or also with keyEncipherment or keyAgreement)"
      ],
      "presetId": "qeaa-provider",
      "mdocPresetId": "qeaa-provider-mdoc",
      "entitlement": "QEAA_Provider",
      "eaaCategory": "urn:etsi:esi:eaa:eu:qualified",
      "sources": [
        "ETSI TS 119 412-6 V1.2.1 clause 7 (QEAA provider)",
        "ETSI EN 319 412-5 V2.6.1 4.2.1 (QcCompliance), 4.2.2 (QcSSCD) and 4.2.3 (QcType)",
        "ETSI EN 319 412-3 V1.4.1 LEG-4.3.1-3 (keyUsage type A, B or F for a seal over content)",
        "ETSI TS 119 472-1 V1.2.1 QEAA-4.2.2.2-02, QEAA-5.2.2.2-01, QEAA-6.2.2.2-01 and QEAA-7.2.2.2-01 (the EAA category)",
        "ETSI TS 119 475 V1.2.1 A.2.2 (QEAA_Provider)"
      ]
    },
    {
      "id": "pub-eaa",
      "name": "PuB-EAA (public sector attestation)",
      "description": "An electronic attestation of attributes that a public sector body responsible for an authentic source issues, or that is issued on its behalf, for example a vehicle registration from the national register. It has the same legal effect as a lawfully issued paper attestation. It needs a qualified seal certificate with the public sector statement (the law and the authentic source). The platform adds the ETSI category urn:etsi:esi:eaa:eu:pub.",
      "certificateRequirements": [
        "QcPSB statement (0.4.0.194126.1.3) with the country of the law, the authentic source and the law",
        "QcCompliance statement (0.4.0.1862.1.1)",
        "QcSSCD statement (0.4.0.1862.1.4)",
        "QcType id-etsi-qct-eseal (0.4.0.1862.1.6.2) or id-etsi-qct-eidaspsbeaa (0.4.0.194126.1.3)",
        "keyUsage type A, B or F (ETSI EN 319 412-2 table 1: nonRepudiation, with digitalSignature or also with keyEncipherment or keyAgreement)"
      ],
      "presetId": "pub-eaa-provider",
      "mdocPresetId": "pub-eaa-provider-mdoc",
      "entitlement": "PUB_EAA_Provider",
      "eaaCategory": "urn:etsi:esi:eaa:eu:pub",
      "sources": [
        "ETSI TS 119 412-6 V1.2.1 clause 8: PSB-8.3-01 to PSB-8.3-05 and Annex A (QcPSB)",
        "CIR (EU) 2024/2979 Annex II PuB-EAA-4.6.3-04 (QcType id-etsi-qct-eidaspsbeaa)",
        "ETSI EN 319 412-5 V2.6.1 4.2.1 (QcCompliance), 4.2.2 (QcSSCD) and 4.2.3 (QcType)",
        "ETSI EN 319 412-3 V1.4.1 LEG-4.3.1-3 (keyUsage type A, B or F for a seal over content)",
        "ETSI TS 119 472-1 V1.2.1 PuB-EAA-4.2.2.3-02, PuB-EAA-5.2.2.3-01, PuB-EAA-6.2.2.3-01 and PuB-EA-7.2.2.3-01 (the EAA category)",
        "ETSI TS 119 475 V1.2.1 A.2.4 (PUB_EAA_Provider)"
      ]
    },
    {
      "id": "mdl",
      "name": "mDL (mobile driving licence)",
      "description": "A mobile driving licence: an mso_mdoc credential with the mDL doctype. It needs a Document Signer certificate of an IACA (ISO/IEC 18013-5 Table B.3). This category and the mDL doctype go together.",
      "certificateRequirements": [
        "keyUsage digitalSignature, critical",
        "extendedKeyUsage 1.0.18013.5.1.2 (mdlDS), critical"
      ],
      "presetId": "mdoc-document-signer",
      "mdocPresetId": null,
      "entitlement": null,
      "eaaCategory": null,
      "sources": [
        "ISO/IEC 18013-5 Table B.3 (document signer: keyUsage digitalSignature critical, extendedKeyUsage 1.0.18013.5.1.2 critical)"
      ]
    },
    {
      "id": "pid",
      "name": "PID",
      "description": "Person identification data: the identity data of a natural person (for example the name and date of birth) that a Member State, or a body on its behalf, issues to the EUDI Wallet. It needs a PID provider certificate.",
      "certificateRequirements": [
        "QcType id-etsi-qct-pid (0.4.0.194126.1.1)",
        "keyUsage type A, B, C or F (ETSI EN 319 412-2 table 1)"
      ],
      "presetId": "pid-provider",
      "mdocPresetId": "pid-provider-mdoc",
      "entitlement": "PID_Provider",
      "eaaCategory": null,
      "sources": [
        "ETSI TS 119 412-6 V1.2.1 clause 4: PID-4.4.1-01 (keyUsage type A, B, C or F) and PID-4.5-01 (QcType id-etsi-qct-pid)",
        "ETSI EN 319 412-2 V2.5.1 4.3.2 and table 1 (key usage types)",
        "ETSI TS 119 475 V1.2.1 A.2.5 (PID_Provider)"
      ]
    }
  ]
}

Authorizations

Authorizationstringheaderrequired
Your API key with the prefix ApiKey: ApiKey <your-api-key>. Get an API key.
Scope:credential-definitions:read

Response

application/json

The credential categories.

credentialCategoriesobject[]
The credential categories, in this order: eaa, qeaa, pub-eaa, mdl, pid.