Automatic Qualified Electronic Seal

The Qualified Electronic Seal (QeSeal) via API is the innovative solution that enables legal entities to guarantee the authenticity and integrity of a large number of documents automatically, from a server and without fees. This can be done in bulk or individually and in a matter of seconds.

It is a fully flexible and customizable service, as it allows the selection of any signature format (CAdES, PAdES, XAdES, and PKCS#1), and the process can occur either synchronously or asynchronously.

No annual fees are required: you only pay for the activation cost of the certificate and for actual usage.

The Qualified Electronic Seal (QeSeal) is the equivalent of the Qualified Electronic Signature (QES), but issued to a legal entity (e.g., company, institution, and organization). Thanks to QeSeal, it is possible to give probative value to one's own data and documents.

Compliant with the eIDAS Regulation, the Seal is legally recognised throughout Europe and is also valid for verifying companies on EPREL.

The solution has 30 customisable security levels. It can be integrated via API into management software, software and websites, to make the signing of large volumes of documents immediate and secure.

During the process of affixing the Seal, it is also possible to mark the document, using any time stamp from an accredited Certification Authority

Before using the QeSeal service via API, it is necessary to activate the automatic qualified electronic seal, which can be purchased by contacting our customer support

On Openapi, automatic and massive Qualified Electronic Signature services are also available in variants with OTP (EU-QES_otp) and without (EU-QES_automatic).

Qualified Electronic Seal Request (EU-QES_eseal)

POST/EU-QES_eseal

The endpoint POST/EU-QES_eseal allows proceeding with the application of the qualified electronic seal via API.

{
 "inputDocument":[
  {
  	"sourceType": "remote",
	  "url": "https://my-domain.com/remoteResource.pdf",
  },
  {
	  "sourceType": "remote",
	  "payload": "BASE64string",
  }
],
 "certificateUsername": "[email protected]",
 "certificatePassword": "password123",
 "title": "PAdES Signature",
 "description": "PAdES signature of a remote and base64 file",
 "signatureType": "pades",
}

The mandatory fields to proceed with the operation are:

If not specified (in the signatureType field), the system will search for the most appropriate format (CAdES, PAdES, XAdES, and PKCS#1) based on the mimeType of the uploaded file.

As mentioned earlier, the service is extremely flexible and allows configuring, via various options, the document validation and signature modes (synchronous or asynchronous), signature level, hash algorithm, and potential callback.

Some options may only be available for specific signature formats (e.g., positioning the signature in the PDF document).

The service also allows marking the document with any type of timestamp.

Qualified Electronic Seal Response (EU-QES_eseal)

POST/EU-QES_eseal

The response content will depend on the status of the request and may include:

If the process is completed, the response will contain data such as state (DONE), options, date:

{
 "data":{
   "id": "67af252164f60538280f70f9",
	 "updatedAt": "2025-02-14 11:12:53.699+00:00",
   "createdAt": "2025-02-14 11:12:34.218+00:00",
   "certificateType": "EU-QES_automatic",
   "state": "DONE",
   "signatureType": "pades",
   "options": {
     "asyncDocumentsValidation": false,
     "asyncSignature": false,
     "level": "B",
     "hashAlgorithm": "SHA256",
     "encryptInAnyCase": false,
     "page": 1,
     "withSignatureField": false,
  },
    "document": {
    "title": "B",
    "description": "",
    "inputDocuments": [
     {
      "sourceType": "base64",
      "createdAt": "2025-02-14 11:12:33.819+00:00",
      "mimetype": "application/pdf",
      "extension": "pdf",
      "size": 339,
      "id": "67af252164f60538280f70fb",
      "md5": "694be78a9eaa52d602bec92e211fa5dc",
      "name": "694be78a9eaa52d602bec92e211fa5dc.pdf",
    }  
  ],
   "validatedDocument": {,
     "mimetype": "application/pdf",
     "extension": "pdf",
     "size": "339",
     "createdAt": "2025-02-14 11:12:33.819+00:00",
     "id": "67af252164f60538280f70fb",
     "md5": "694be78a9eaa52d602bec92e211fa5dc",
     "name": "694be78a9eaa52d602bec92e211fa5dc.pdf"
}
  "signedDocument": {,
     "createdAt": "2025-02-14 11:12:34.229+00:00",
     "mimetype": "application/pdf",
     "extension": "pdf",
     "size": "50133",
     "id": "67af252264f60538280f70fe",
     "md5": "363cfdb141fe0e1a3f598e1d6377a4f5",
     "name": "67af252264f60538280f70fe.pdf"
   },
  }
}

Audit

GET /signatures/{id}/{actionType}

At the end of the procedure, it will be possible to request details of the completed process, the signed document, the validated document, or the audit trail, which is the document containing all the information that led to the successful signing. In case of disputes, this file will allow reproducing each step of the procedure technically.

Verify Signature Validity

POST/verify

Openapi also allows verifying if a document has actually been signed, who the signature is associated with, and how long it is valid. The reference endpoint in this case is POST/verify.

REQUEST EXAMPLE

During the request phase, it is necessary to upload the signed document.

{
  "inputDocument": "BASE64string",
  "detachedContent": "BASE64string",
  "pdfEncryptionPassword": "password123",
  "recursive": true,
  "verifyOnDate": "2025-02-14"
}

RESPONSE EXAMPLE

The system will return various pieces of information about the document. First, it specifies whether the document was correctly signed, in which format, and if the signature is valid.

It also indicates:

{
  "data": {
    "checkDate": "2025-02-14 11:11:01.892+00:00",
    "verificationDate": "2025-02-14 11:11:01.892+00:00",
    "signatureFormat": "PAdES",
    "nrOfSignatures": 1,
    "overallVerified": true,
    "signatureReportList": [
      {
        "id": "0",
        "integrity": true,
        "signatureAlgorithmName": "SHA256withRSA",
        "subjectDN": "C=IT,SURNAME=ROSSI,GIVENNAME=MARIO,SERIALNUMBER=TINIT-RSSMRA73R02H501H,CN=ROSSI MARIO,DNQ=AUSL2023021972028357",
        "issuerDN": "C=IT,O=Namirial S.p.A./02046570426,OU=Certification Authority,CN=Namirial CA Firma Qualificata",
        "subjectCN": "ROSSI MARIO",
        "issuerCN": "Namirial CA Firma Qualificata",
        "serialNumber": "5557601230250214000",
        "signerCertificateStatus": "VALID",
        "signerCertificateNotBefore": "2025-02-14 11:11:01.892+00:00",
        "signerCertificateNotAfter": "2025-02-14 11:11:01.892+00:00",
        "signerCertificateRevocationDate": "2025-02-14 11:11:01.892+00:00",
        "issuerCertificateStatus": "VALID",
        "issuerCertificateRevocationDate": "2025-02-14 11:11:01.892+00:00",
        "trustedSignatureDate": false,
        "signatureDate": "2025-02-14 11:11:01.892+00:00",
        "issuerTrustedList": true,
        "keySize": 2048,
        "qcComplianceStatus": "VALID",
        "qcSSCDStatus": "VALID",
        "derEncodedSignerCert": "BASE64string"
      }
    ],
    "noteReportList": [
      {
        "policy": 3,
        "about": 2,
        "type": 1,
        "synopsis": "Certified qualified in conformity",
        "description": "The qualified certificate of ROSSI MARIO complies with European Directive 1999/93/EC"
      }
    ],
    "plainDocument": "BASE64string"
  },
  "message": "Signature is valid",
  "error": null,
  "success": true
}

The automatic qualified electronic seal is designed for those who need to certify the validity of a large number of documents on a daily basis and in bulk mode (e.g. law firms, banks, insurance companies, public bodies). The main benefits of this service include time and cost savings, optimisation of document workflows and digitisation of processes.