Automatic Qualified Electronic Signature with OTP

The Automatic Qualified Electronic Signature (QES) with OTP is the solution via API to automate and simplify signature processes, in full compliance with European regulations.

Strong authentication, using One Time Passwords, enhances the security level of the electronic signature and provides additional protection to signed documents.

The service is flexible and customizable. In particular, it allows you to choose

There are no annual fees: the only fixed cost is the certificate activation fee (€99). Afterwards, you only pay for actual usage.

The Automatic Qualified Electronic signature is available on OpenAPI also for legal entities, through a specific service (Qualified Electronic Seal).

The electronic signature has full European validity: it is recognised by European Union law through the eIDAS regulation.

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

Before using the Qualified Electronic Signature with OTP, it is necessary to purchase a signing certificate via the dedicated POST /certificates/namirial-otp endpoint. For the identification procedure, video recognition is included in the price, and can be done from the office or from home, in a matter of seconds. Alternatively, other identification procedures are available via SPID, CIE, CNS, Digital Signature.

After the certificate activation, it will be possible to start using the specific automatic signature service, which is available via API either with OTP or without OTP (in the latter case, the reference endpoint is EU-QES_automatic).

Request for Qualified Electronic Signature with OTP (EU-QES_otp)

POST/EU-QES_otp

The POST/EU-QES_otp endpoint allows you to apply the qualified electronic signature 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 for proceeding with the signature are:

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

As mentioned above, the service is highly flexible and allows you to configure, for example, document validation and signing modes (synchronous or asynchronous), signature level, hash algorithm, and possible callbacks.

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

Additionally, the service allows for timestamping the document with any type of timestamp.

Response for Qualified Electronic Signature with OTP (EU-QES_otp)

POST/EU-QES_otp

The content of the response after the request will clearly depend on the request status and could be:

In case of completing the signing process, 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",
   }
} 

Audit

GET /signatures/{id}/{actionType}

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

Signature Validity Verification

POST /verify

Openapi also allows you to verify whether a document has actually been signed, who the signature is associated with, and how long it remains valid. The relevant endpoint in this case is POST /verify.

REQUEST EXAMPLE

When making a request, 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 information about the document. First, it specifies whether the document has been properly signed, in which format, and whether the signature is valid.

Additionally, it provides:

{
  "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 signature is designed for those who need to sign a large number of documents on a daily basis and in mass mode (e.g. administrators, doctors, law firms, public bodies). The main benefits of this type of signature include time and cost savings, optimisation of document workflows and digitisation of processes.