From: €0.69 + VAT
The Advanced Electronic Signature solution combines signer identification security, greater legal certainty, and a simple, fast, and fully customizable signing experience.
The Advanced Electronic Signature solution allows you to integrate a signing process directly into your systems via API — CRM, ERP, SaaS, management software, portals, and websites — eliminating the need to print, manually sign, and scan documents.
Compared to a simple electronic signature, it provides greater evidentiary value and enhanced legal certainty. Fully compliant with the eIDAS Regulation, ETSI standards, and GDPR, the process includes, among other features, fast and legally compliant user identification, which can be configured with or without liveness verification depending on the required level of security.
Authentication via OTP (One-Time Password), sent to a verified contact (mobile phone number), uniquely associates the signer with the document. Every operation is tracked to ensure complete control, traceability, and a detailed audit trail of the entire process.
Finally, a single endpoint can be used to manage both identification and signing for one or more people.
The POST/EU-AES endpoint allows you to request the electronic signature service and obtain the links to the platform where signers will complete the identification procedure and the signing process.
POST/EU-AES
POST https://esignature.openapi.com/EU-AES
In the request payload, you need to provide the document to be signed (URL or Base64), the signer's details (first name, last name, email address, mobile phone number), an optional message, and the signature position (page and coordinates) for each individual signer. You can also define:
Here is an example of a payload:
{
"signers": [
{
"name": "string",
"surname": "string",
"email": "[email protected]",
"mobile": "string",
"message": "string",
"signatures": [
{
"page": 1,
"x": "331"
"y": "45"
"name": "string"
}
]
},
{
"name": "string",
"surname": "string",
"email": "test@emailcom",
"mobile": "string",
"message": "string",
"signatures": [
{
"page": 1,
"x": "331",
"y": "45",
"name": "string"
}
]
}
],
"inputDocuments": "https://url.pdf.com",
"callback": {
"url": "https://www.mysite.it/callback.php"
},
"signatureMode": [
"typed",
"drawn"
],
"userEditableData": {
"name":"true",
"mobile":"true"
"email":"true"
}
}
For Advanced Electronic Signatures, the only method available for sending the OTP is via SMS.
If you require user identification with the liveness option, the payload structure remains unchanged, but the request must be sent to the dedicated POST/EU_AES_liveness endpoint.
When making the request, you can also set a callback to receive updates whenever the request status changes.
POST/EU-AES
The response includes information such as:
{
"data": {
"id": "6927055e66abe148eb0efc6b",
"errorNumber": null,
"errorMessage": null,
"updatedAt": "2025-11-26 13:49:18.879+00:00",
"createdAt": "2025-11-26 13:49:18.879+00:00",
"certificateType": "EU-SES",
"state": "WAIT_VALIDATION",
"signatureType": "pades",
"signers": [
{
"authentication": [
"sms"
],
"name": "Mario",
"surname": "Rossi",
"state": "NEW",
"email": "[email protected]",
"id": "76d6e556-a35c-42a5-9973-xxxxxxxxx",
"url": "https://esign.openapi.com/76d6e556-a35c-42a5-9973-xxxxxxx",
"language": "browser",
"message": "Hi, this is your OTP",,
"signatures": [
{
"page": 1,
"x": 331,
"y": 45,
"formId": null
}
],
"emailValidation": {
"domain": "email.com",
"host": "email.com",
"mxRecords": [...],
"otpAttempts": 0
}
},
{
"name": "Mario",
"surname": "Rossi",
"state": "NEW",
"email": "[email protected]",
"id": "0a551419-0da9-4a32-bd4a-xxxxxxxxx",
"url": "https://esign.openapi.com/0a551419-0da9-4a32-bd4a-6xxxxxxx",
"language": "browser",
"message": "Hello Mario, this is your OTP code:","
"signatures": [
{
"page": 1,
"x": 331,
"y": 45,
"formId": null
}
],
"emailValidation": {
"domain": "email.com",
"host": "email.com",
"mxRecords": [],
"otpAttempts": 0
}
}
],
"options": {
"asyncDocumentsValidation": true,
"asyncSignature": false,
"signatureMode": [
"typed",
],
"userEditableData": {
"name": true,
"mobile": true,
"email": true
},
"withTimestamp": false,
"timezone": "UTC"
},
"document": {}
},
"message": Created",
"success": true,
"error": null
}
At this stage, the link to the customizable platform (Web App) is returned, where each signer can view the document and complete the signing process using OTP authentication (as defined in the request).
The request ID is essential for the subsequent steps, particularly for checking the request status and downloading the signed document.
The simple electronic signature solution allows you to fully customize the signing interface, without limits, with corporate logos, colors, and redirect pages.
In particular, you can define:
Customization settings must be passed as options in the signing request payload and can be modified for each new signing process initiated.
If the interface is not customized, the default interface will be provided. It is neutral and does not include corporate logos.
POST/verify
You can verify a signed document using the dedicated /verify endpoint. In the request payload, you must provide the signed document in Base64 format and, optionally, the detached content, the password for encrypted PDFs, and whether the verification should be recursive or scheduled for a specific date.
{
"inputDocument": "BASE64string",
"detachedContent": "BASE64string",
"pdfEncryptionPassword": "password123",
"recursive": true,
"verifyOnDate": "2025-02-14",
}
POST/verify
The response includes information such as the verification date, signature format, document integrity, and certificate information.
{
"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 MARI",
"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": ""
"success": true
}
GET /signature/{id}/{actionType}
At the end of the signing process, you can request the following via API:
The audit trail is the document containing all the information that contributed to the successful completion of the signing process. In the event of a dispute, this file makes it possible to technically reproduce every step of the procedure. The audit trail provides process data (ID, creation, sending, and expiration date), signer data (first name, last name, email address, phone number, IP address), and information on signer authentication methods (authentication method, message sent, and validation time).
The audit trail is archived in its original form for 10 years, as required by applicable regulations, while the document will be available for 3 months.
The Advanced Electronic Signature (AES) is designed for companies and organizations that want to digitize signing processes, eliminate paper-based workflows, and integrate electronic signatures directly into their systems. Thanks to secure identification, traceability, and greater legal certainty, it is particularly suitable for:
Do you need help?
Haven't found the answer you're looking for?
Fill in all the details, we will get back to you as soon as possible!
The Advanced Electronic Signature (AES) service with OTP allows you to integrate a complete electronic signature process into any platform, application, or business system, enabling document signing to be dematerialized and the entire process to be digitized.
Unlike traditional handwritten signatures, no physical support is required: the process is based on digital procedures that identify the signatory, associate the signature with their identity, and ensure the integrity of the document.
Unlike a Simple Electronic Signature (SES), an AES requires a specific user identification procedure based on an identity document, available with or without liveness verification, depending on the required security level.
During the signing process, the user is also authenticated using an OTP (One-Time Password), a temporary password that can only be used once. This contributes to ensuring a high level of security and uniquely linking the signatory to the signature affixed to the document.
Openapi offers the following types of electronic signatures:
The signing process is the same in both cases. The only difference concerns the signatory identification method, which may or may not include a Liveness check.
1. Advanced Electronic Signature without Liveness
Identification is fully automated and based on artificial intelligence, providing fast, secure, and cost-effective verification.
During the procedure, the user records a video of both the front and back of their identity document, including movements and tilts of the document to enable authenticity checks. The service automatically extracts and validates data from identity documents issued in more than 190 countries and territories, integrating advanced AI-based authenticity checks and, when necessary, the support of a specialized fraud prevention team.
2. Advanced Electronic Signature with Liveness
This includes all the features of verification without Liveness, with the addition of Liveness detection, which verifies that the identified person is actually present during the procedure.
In addition to recording their identity document, the user is therefore required to record their face while performing specific facial movements. This additional check increases the level of security and helps prevent fraud attempts based on the use of images, videos, or other tools designed to simulate the user's presence.
Both methods comply with the GDPR and the European PSD2 Directive and are certified according to the ETSI standard.
The Advanced Electronic Signature (AES) can be used to sign many types of digital documents, particularly when the law does not require a specific type of signature or the involvement of a public official.
Common use cases include:
However, an AES cannot be used indiscriminately for every document. Certain legal acts may require a specific form, a Qualified Electronic Signature (QES), the involvement of a public official, or other formalities required by law. In Italy, for example, specific limitations apply to certain categories of legal acts.
For this reason, before using an AES for a specific document, it is important to verify the requirements established by the applicable regulations and by the country in which the document is intended to produce legal effects.
In general, the eIDAS Regulation establishes that an electronic signature cannot be denied legal effect or admissibility as evidence solely because it is in electronic form or because it is not a qualified electronic signature.
The service is provided in real time.
The Advanced Electronic Signature service is simple and allows you to sign PDF documents remotely. The same document can be signed by multiple people, on one or more pages.
The process is simple:
The user receives a link to start the identification process, which can also be accessed via QR code. They simply need to photograph their identity document, take a selfie, and perform a few simple facial movements.
The system guides the user step by step and provides real-time feedback throughout the entire procedure, making identification simple, fast, and secure.
For the Advanced Electronic Signature (AES) process, the OTP is delivered exclusively via SMS.
Choosing SMS as the OTP delivery channel ensures high standards of legal validity and usability:
Yes, you can customize the text of the SMS message. The maximum message length is 160 characters (including the OTP code).
Additionally, the recipient's phone number must be provided in the international E.164 format.
Yes, the same signer can place multiple signatures on different pages of the same document (e.g., contracts, specific contractual clauses, privacy notices). The service cost is calculated per signer, not based on the number of signatures applied.
Yes, it is possible to add a timestamp to the signed document. During configuration, you can also specify the desired hash algorithm by choosing from SHA1, SHA256, SHA384, and SHA512.
The cost of applying a timestamp is €0.150 per document.
Yes, it is possible to add a timestamp to the signed document. During configuration, you can also specify the desired hash algorithm by choosing from SHA1, SHA256, SHA384, and SHA512.
The cost of applying a timestamp is €0.150 per document.
For each signing process, the interface can be branded with the following customizations:
By default, the signing interface uses the language configured in the browser and can be easily changed during the signing process.
This parameter can be configured individually for each signer (signers).
Although the language is automatically detected from the browser settings, a different language can be selected when submitting the signature request.
The following languages are currently available:
The selected language applies exclusively to the signing interface and does not affect the content of SMS messages containing the OTP.
No, currently it is not possible to customize the domain of the signing page. However, you can embed it within your own website using an <iframe>.
Yes, you can embed the web application within your own webpage. To ensure that identity verification works correctly, the iframe tag must include the allow="camera; microphone" attribute and be served over HTTPS.
Additionally, when using an iframe, you must specify the iframeAncestors field in the signature request payload (under options ui), providing the parent URLs authorized to embed the application.
The standard used to apply the signature is PAdES (PDF Advanced Electronic Signature).
No. Password-protected PDF documents cannot be signed: the system requires files to be accessible without restrictions in order to complete the signing process correctly.
Yes, at the end of the signing procedure, you can request the signed document via API, as well as a copy of the audit trail. The audit trail is the document containing all the information that led to the successful completion of the signature. In the event of a dispute, this file will allow each step of the procedure to be technically reproduced.
The audit trail contains data on:
The audit trail is archived for 10 years.
Yes. The Advanced Electronic Signature with OTP is recognized under European Union law through the eIDAS and ETSI regulatory frameworks and complies with the GDPR.
The service includes signatory identification and, at the end of the procedure, Openapi makes both the signed document and the audit trail available. The audit trail is the record containing information and evidence relating to the signing process.
The audit trail makes it possible to technically reconstruct and verify the different stages of the procedure and can therefore represent important evidence in the event of disputes or challenges.
The information recorded in the audit trail includes:
The original audit trail is retained for 10 years, in accordance with applicable regulations.
Yes. Openapi's AES meets the requirements of Article 26 of Regulation (EU) No. 910/2014 (eIDAS):
Some Member States impose additional national requirements on providers offering AES to their users. It is the customer's responsibility to verify and comply with the regulations of the country in which they operate.
Yes, Openapi's Advanced Electronic Signature (AES) solution complies with the ETSI standards applicable to trust services and electronic signatures.
The technical compliance of generated signatures can be verified using verification and validation tools based on ETSI standards.
The document will be available for 3 months, while the audit trail will be available for 10 years.
Photos of identity documents captured during identity verification are stored in encrypted form within the audit trail.
Who is responsible? Responsibility for retaining signature evidence lies with the company requesting the signature, which acts as the data controller under the GDPR. Openapi acts as the technology provider and data processor (Article 28 GDPR).
For how long? The eIDAS Regulation does not establish a general requirement for legally compliant long-term preservation of Advanced Electronic Signatures. However, some countries may require specific preservation services. Customers are responsible for verifying how each Member State has implemented the provisions of eIDAS 2 and taking any necessary measures.
Openapi stores documents in encrypted form for 3 months and the audit trail for 10 years.
In the event of a dispute. The evidentiary value and any additional requirements depend on the legislation applicable in each European country. Some legal systems recognize AES as having effects equivalent to a handwritten signature in certain circumstances, while others require additional measures or services. Customers are responsible for verifying the regulations applicable in their country.
Is it mandatory to retain signature evidence?
As stated in the technical manual signed before activating the service, customers must verify whether retaining evidence or using e-archiving services is recommended or mandatory in their country.
In all cases, Openapi recommends that all customers retain signature evidence for the long term. For this purpose, customers can use a legally compliant Digital Preservation service available through Openapi, which can be activated separately from the signing process.
The cost is calculated per signer, not by the number of signatures affixed to the document
The cost for the Advanced Electronic Signature service with OTP without liveness verification is:
The cost for the Advanced Electronic Signature service with OTP with liveness verification is:
If there are multiple signers, the cost is multiplied by the number of signers involved, applying the applicable rate (subscription or single request). It is charged at the time of the request, regardless of how the signing process is subsequently completed.