{
"documentName": "string",
"summary": {
"totalSignatures": 1073741824,
"validSignatures": 1073741824
},
"signatures": [
{
"signatureId": "string",
"indication": "string",
"indicationDetails": "string",
"signer": "string",
"validationTime": "2025-02-08T20:59:59.039Z",
"signingTime": "2025-02-08T20:59:59.039Z",
"signingCertificate": {
"subject": "string",
"issuer": "string",
"serialNumber": "string",
"validFrom": "2025-02-08T20:59:59.039Z",
"validTo": "2025-02-08T20:59:59.039Z"
},
"certificateChain": [
{
"subject": "string",
"issuer": "string",
"serialNumber": "string",
"validFrom": "2025-02-08T20:59:59.039Z",
"validTo": "2025-02-08T20:59:59.039Z"
}
],
"signatureDetails": {
"errors": [
"string"
],
"warns": [
"string"
],
"infos": [
"string"
]
}
}
]
}
curl --location 'https://zylalabs.com/api/6122/digital+signature+verification+api/8389/qualified+electronic+signature+validation' \
--header 'Content-Type: application/json' \
--form 'image=@"FILE_PATH"'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Digital Signature Verification API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
The Digital Signature Validator API provides endpoints to validate electronic signatures in documents. It supports both Qualified Electronic Signatures (QES) and Advanced Electronic Signatures (AdES) validation under standards like eIDAS. The validation process ensures the signatures' authenticity, compliance, and legal validity.
In a simplified model, validating a digital signature involves two main steps:
Cryptographic Validation: Ensuring the digital signature's cryptographic integrity by decrypting its value and comparing the result to the hash of the signed data.
Certificate Validation: Confirming the validity of the signing certificate, which includes performing certification path validation.
The API confirms that the certificate used in the signature is a Qualified Certificate (QC) by: 1. Checking its compliance with ETSI EN 319 412 standards. 2. Verifying its revocation status using Certificate Revocation Lists (CRL) and Online Certificate Status Protocol (OCSP). 3. Ensuring that the issuing CA is recognized on EU Trusted List.
A Qualified Electronic Signature (QES) is the highest level of electronic signature under regulations like eIDAS. It provides legal equivalence to handwritten signatures. Validation ensures that the signature is authentic, legally compliant, and has not been tampered with.
The API currently supports validation of QES signatures in PDF and XML document formats.
Yes, the API ensures that validated signatures meet all the legal and technical requirements defined under eIDAS and other relevant electronic signature standards. This makes it suitable for use in legally binding digital transactions.
The API follows a multi-step process to validate QES, including: 1. Extracting the signature and metadata from the document. 2. Performing a cryptographic integrity check to ensure the signature is unaltered. 3. Validating the certificate, checking expiration, revocation status, and compliance with official trusted lists (e.g., EU Trusted List). 4. Ensuring the signature meets eIDAS legal and technical requirements.
The endpoint returns a JSON response containing details about the document, including the total number of signatures, valid signatures, and specific information for each signature, such as validation status, signer details, and certificate information.
Key fields include `documentName`, `summary` (with `totalSignatures` and `validSignatures`), and an array of `signatures` containing details like `signatureId`, `indication`, `signer`, and `signingCertificate`.
The response is structured in a hierarchical format, starting with document-level information, followed by a summary of signatures, and detailed validation results for each signature in an array format.
Users can customize their requests by providing parameters such as the document format (PDF or XML) and the signature data to be validated, ensuring the API processes the correct information.
The endpoint provides information on the validity of signatures, details about the signing certificate, validation time, signing time, and any errors or warnings encountered during the validation process.
Users can analyze the `summary` to assess overall signature validity and review individual `signatures` for detailed validation results, including any errors or warnings, to ensure compliance and authenticity.
The API performs multiple checks, including cryptographic integrity verification, certificate validation against trusted lists, and compliance with eIDAS standards, ensuring high data accuracy and reliability.
Typical use cases include validating electronic contracts, ensuring compliance in legal documents, and verifying signatures in financial transactions, where authenticity and legal validity are crucial.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund