This repository documents the APIs related to the MUSAP project. MUSAP consists of the following three APIs:
- MUSAP API (native iOS/Android)
- MUSAP Link API (REST/JSON API)
- MUSAP Coupling API (JSON API)
Additionally, the MUSAP Specification can be found here, and KeyURI specification here.
Overall MUSAP Architecture is:
The MUSAP API is described in detail in Chapter 11 of the MUSAP Specification. Generally it consists of the following parts:
- Key Discovery API
- Signature API
- Key Lifecycle API
- Key Binding API
- Import/Export API
The Link API is an API intended for Application Providers. It can be used to request key generation and signatures from MUSAP libraries that have been integrated with a MUSAP Link server. The API is described in detail in Chapter 10.1 of the MUSAP Specification.
The API includes the following end-points:
- /link
- /sign
- /docsign
- /generatekey
- /updatekey
Postman API description can also be found here.
The Coupling API is used by the MUSAP library to communicate with the MUSAP Link backend. The API is described in detail in Chapter 10.2 of the MUSAP Specification.
It includes the following end-points:
- getdata
- signcallback
- enrolldata
- updatedata
- linkaccount
- externalsignature
For all users MUSAP provides at least two keystores to be interfaced with end-user-add: