Issuing Verifiable Credentials with the Blerify API

This section of the documentation explains how to use the Blerify API to issue W3C-VC Standard.

API Endpoints for W3C-VC Standard Issuance

The following are the Blerify API endpoints for Verifiable Credentials issuance:

1- "Create" Endpoint

• Description: This endpoint is used to create a W3C Verifiable Credentials format.

• HTTP Method: POST

• Endpoint URL: {{api-host}}/api/v1/organizations/{{organization-id}}/projects/{{project-id}}/credentials

Blerify APIBlerify Public API

2- "Approve" Endpoint

• Description: This endpoint is used to approve the VC created in the previous step.

• HTTP Method: POST

• Endpoint URL: {{api-host}}/api/v1/organizations/{{organization-id}}/projects/{{project-id}}/crypto/sign/es256

Blerify APIBlerify Public API

Example Workflow

1. The Service Account is created in the Blerify portal and the JSON file is downloaded.

2. A library (preferred by the client) is used to generate the access token.

3. The "Create" endpoint is called to create the W3C-VC, sending the access token at all times and generating it again if necessary.

4. The Digital Credential ID is received in the response.

5. The "Approve" endpoint is called using the Digital Credential ID and the digital signature.

6. The complete credential object is received in the response.

7. This object is delivered to the end user for download to their wallet.