Configure credential types

Credential types define what credentials are valid in the ecosystem.

This does not mean that other credentials cannot be issued or verified in the ecosystem - that is up to the customer business logic to determine. It only means that these are the only credentials that are considered valid (Level 2 trust).

Request

Make the following request to configure a new credential type:

http
Copy to clipboard.
1POST https://YOUR_TENANT_URL/v1/ecosystems/{ecosystemId}/credentials
  • ecosystemId: Credential types must be configured within a specific ecosystem. Use the ecosystem unique id obtained when you created the ecosystem.

json
Copy to clipboard.
1{
2  "profile": "compact",
3  "type": "DriverLicence",
4  "name": "Driver's Licence"
5}
  • profile: Insert the profile of the new credential (web-semantic, compact-semantic, compact or mobile).

  • type: Insert the type of the new credential.

  • name: Insert a meaningful name for the new credential.

Response

json
Copy to clipboard.
1{
2  "id": "599bf148-d711-405a-a20b-9c8a87ac8850",
3  "ecosystemId": "6f219af9-edc2-4840-b8e7-05b27f28751d",
4  "profile": "compact",
5  "type": "DriverLicence",
6  "name": "Driver's Licence"
7}
  • id: A unique identifier for the new credential. This identifier is used when creating a policy.

  • ecosystemId: The requested ecosystem identifier.

When required, ecosystem operators can delete a configured credential type so that it is no longer considered valid in the ecosystem.

What's Next?

Your ecosystem now has valid participants and credential types. You can now combine the two to create policies.