ZapSign API
English
English
  • General Information
  • Getting Started
  • ZapSign Environments
  • Ready-to-use requests!
  • Authentication
    • Static token
    • JWT Authentication
      • Get access token
      • Refresh your access token
  • Types of Tokens
  • API versioning
  • Rate Limit Policies
  • Incident alerts
  • How Payment Works
  • Status Code
  • Account
    • Plan Information
    • List account users
    • Create account users
    • Delete account user
  • Documents
    • Create document via Upload
    • OneClick (ClickWrap)
      • Create document (OneClick)
    • Create document via Template
    • Add attachment (extra document)
    • Add attachment (extra document) via Template
    • Detail document
    • List documents
    • Delete document
    • Document Audit Trail
    • Optional: Place signatures
    • Reject Documents
  • Signature Validation
  • Signers
    • Detail signer
    • Update signer
    • Add signer
    • Delete signer
    • Batch sign via API
    • Reject Documents by User
  • Templates
    • Create template (DOCX)
      • Configure Template Form
    • List templates
    • Get template
    • Update template
    • Delete template
  • Partnerships
    • Update Payment Status
    • Create Account
  • TIMESTAMP
    • Add timestamp
  • Background Check
  • Introduction
  • Understanding the Result
  • Creating a Background Check
    • Person Check
    • Company check
  • Retrieve a Check
  • Check details
  • Webhooks
    • How webhooks works
    • Testing webhooks on ZapSign
    • Create Webhook
    • Webhooks logs
    • Events
      • Document
        • Doc created
        • Doc deleted
        • Created signer
      • Signer
        • Signature request send
        • Document viewed
        • Reading confirmation
        • Doc signed
        • Doc refused
        • Email bounce
        • Failed Validation
      • Background check
        • Background check completed
    • Reprocessing Documents and Webhooks
    • Delete Webhook
  • Widget
    • How widget works
Powered by GitBook
On this page

Was this helpful?

Signature Validation

POST https://api.zapsign.com.br/api/v1/validate-pdf-signature/

Description: This endpoint validates digital signatures in PDF files sent via request. The verification returns whether the document is valid or invalid.

The criteria for a document to be considered valid are:

  • The document has one or more digital signatures.

  • All signatures contained in the file were made by ZapSign.

  • All signatures in the file are cryptographically valid.

  • The document has not been altered after being signed.

  • There are no signatures rejected by the signer.

  • There are no pending signatures.

In case of an invalid document, the endpoint returns a message with the reason why it was invalidated.

How to Use:

Send a POST request in multipart/form-data format containing the PDF file in the file field.

Headers

Key
Value

Content-Type

multipart/form-data

Request Body (form-data)

Key
Type
Description

file

file (PDF)

PDF file to be validated

Response Body (JSON)

Key
Type
Description

isValid

Boolean

true if the file is signed and valid, and false if invalid

message

Text

Message regarding the validation result

authority

Text

Common Name of the Certifying Authority

signingDate

Text

Signing date formatted dd/mm/YYYY hh:mm:ss

commonName

Text

Common Name of the signature (ZapSign)

Response Examples:

Valid Document:

200: OK

{
    "isValid": true,
    "message": "Document signed correctly (CN=ZAPSIGN) and without subsequent notes.",
    "authority": "AC Certisign Multipla G7",
    "signingDate": "11/19/2024 14:34:58",
    "commonName": "ZAPSIGN PROCESSAMENTO DE DADOS LTDA"
}

Invalid Document:

200: OK

{
    "isValid": false,
    "message": "Signature Signature1 does not cover the whole document",
    "authority": "N/A",
    "signingDate": "N/A",
    "commonName": "N/A"
}
PreviousReject DocumentsNextDetail signer

Last updated 1 day ago

Was this helpful?