.png%3Falt%3Dmedia%26token%3D5103af49-8d57-46b4-a946-d0ccdb82d09b)
.png%3Falt%3Dmedia%26token%3D5103af49-8d57-46b4-a946-d0ccdb82d09b)
Comment on page
REST API
Manage keys, DIDs, issue Verifiable Credentials, and verify them using the SSI-Kit's REST API.
Make sure you have Docker or a JDK 16 build environment including Gradle installed on your machine
Docker
Local
Pull the docker container directly from docker hub and run the project
docker run -p 7000-7004:7000-7004 -itv $(pwd)/data:/app/data waltid/ssikit serve -b 0.0.0.0
This will create a folder called data in your current directory as storage for the VC, DIDs, Keys and other things which need to be stored in order to provide all the functionality.
- 1.Clone the project
git clone https://github.com/walt-id/waltid-ssikit.git
2. Change the folder
cd waltid-ssikit/
3. Run the project
The first time you run the command you will be asked to built the project. You can confirm the prompt.
./ssikit.sh serve
If you want to get a more detailed overview of the options provided for building the project on your machine, please refer to building the project.
After successfully running the project, you will have the endpoints, described below, available for use.
Exposed endpoints:
Type | Locally | General Available |
|---|---|---|
Signatory API - For Issuers | http://127.0.0.1:7001 | |
Custodian API - For Holders | http://127.0.0.1:7002 | |
Auditor API - For Verifiers | http://127.0.0.1:7003 | |
Core API | http://127.0.0.1:7000 | |
ESSIF API | http://127.0.0.1:7004 |
The Core API exposes most of the functionalities provided by the SSI Kit, however newer features will only be released in the other API endpoints. Therefore, it is recommended to use the Signatory API, Custodian API and Auditor API for most use cases.
Last modified 19d ago