Stateless signature
If only a signature with a seal, or a PKCS12, is required, the PDF document can be signed with a single REST call. This reduces the overhead, as no session data (with huge pdf files) is stored in the DB, and increases performance.
Seal a document
To sign a document, a HTTP POST request is required. As for the add document call, the following multipart form data values can be set:
| Name | Type | Description |
|---|---|---|
| document | File | The document to sign |
| location | string | Location of the signature |
| reason | string | Reason of the signature |
| template | string | ID of the template |
| x | string | X0 in userspace units[^1] |
| y | string | Y0 in userspace units[^1] |
| w | string | X1 in userspace units[^1] |
| h | string | Y1 in userspace units[^1] |
| page | string | page of the signature seal |
Depending on the signature type, the following set of parameters is required:
- Invisible signature needs the following parameter: document, location, reason
- Image on default position (as specified in the template) needs additionally: template
- Image on specific position needs additionally: x, y, w, h, page
If the signature is successful, the service responds with a 200 OK and the signed PDF document.
"a.sign seal qualified" signatures
To seal a document with an "a.sign seal qualified" certificate, it is required to configure Hash2Sign as described in the Hash2Sign manual. Afterwards, the StatelessSealSignature endpoint can be used.
PKCS12 signatures
To seal a document with a PKCS12, it is required to configure Hash2Sign as described in the Hash2Sign manual. Afterwards, the StatelessCertificateSignature endpoint can be used.
Footnotes
[^1] https://opensource.adobe.com/dc-acrobat-sdk-docs/library/interapp/IAC_API_CoordinateSystems.html