Guidelines for SignAPI service integration
History
| Version | Description |
|---|---|
| v.1 | Initial web version |
Description
Signature creation and validation service API's (SignAPI) work is based on sessions.
Received session identifier shall be used in all future requests as reference to a specific set of files.
SignAPI provides session storage on a perpetual basis and is used as an identifier for a particular file or set of files.
Service providers only need to retrieve the session identifier once and Service provider shall save session identifier with the parameters of a related particular file or set of files.
Components
SignAPI hosts
| Environment | Host <SignAPI_base_url> |
|---|---|
| Test | signapi-prep.eparaksts.lv |
| Production | signapi.eparaksts.lv |
New Alternative Signing Model
In addition to the Signing Platform, a Remote eID Signature (CSC API) integration is also available for creating remote qualified electronic signatures. View the documentation here.
Test and explore SignAPI
Start testing with the Postman collection or use the API Reference to inspect endpoints and try requests directly from the documentation.
Updated about 1 month ago