Signature creation and validation service API's overview
Signature creation and validation service (SignAPI) hosts:
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.
Session API
Operations
Method | Endpoint | Description |
---|
GET | start | Data processing session creation |
GET | {sessionId}/close | Closing data processing session |
Storage API
Operations
Method | Endpoint | Description |
---|
PUT | {sessionId}/upload | Upload file |
GET | {sessionId}/list | Retrieve file list in specific session |
GET | {sessionId}/{documentiId} | Download file |
DELETE | {sessionId}/{documentiId} | Delete file |
POST | {sessionId}/addDocumentDigest | Add file digest and file name for signing. |
Signing API
Operations
Method | Endpoint | Description |
---|
POST | calculateDigest | Signable data calculation. |
POST | finalizeSigning | Signed document finalization. |
POST | addArchive | Archive timestamp requesting. |
POST | eSealCreate | Creates electronic seal with client provided electronic seal key. |
Validation API
Operations
Method | Endpoint | Description |
---|
GET | {sessionId}/{documentiId}/validate | Validation of signed file |
Configuration API
Operations
Method | Endpoint | Description |
---|
GET |
| Retrieve Service provider's configuration |