...
It is not possible to use USB-tokens or any user-related certificates for signing when using
this API call as the login is not linked to a user. The possibility does exist to use a dedicatteHeadless signing is normally used with a dedicated
eSeal. This can be configured by the PKIsigning technical team.
...
Headless signing begins by posting a request as can be found in example 1 to the
/api/signing/signheadless url.
Code Block | ||
---|---|---|
| ||
POST /api/signing/signheadless HTTP/1.1 Host: https://api.pkisigning.io Authentication: Bearer kjhafd22323…094alskdfasjasf Content-Type: application/json { "documentsToSign": [ { "filename": "document1.pdf", "contents": "<<base64>>", "placeholders":["Signer1","Signer2"] }, [...] ], "assuranceLevel":"substantial", "signatureFormat":"PadES" } |
Code example 1: Initiating headless signing session
The result will be equal to example 42.Based on the documenttypes and mimetypes, the PKIsigning service will determine the type
of signing to perform.
Code Block |
---|
HTTP/1.1 200 OK
{
"id": "<<sessionId>>",
"password": "<<encryptionkey>>"
} |
Code example 2: Start session response
Info |
---|
Please note: |
...
|
...
|
Info |
---|
Please find a complete swagger definition of our API at https://accengine.pkisigning.io/swagger/index.html?urls.primaryName=Headless |