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
  • 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
  • API Implementation Essentials
  • Chat with Gepeto!

Was this helpful?

General Information

NextGetting Started

Last updated 5 months ago

Was this helpful?

ZapSign is an electronic document signing platform that ensures authenticity, integrity, and non-repudiation. All signatures made through ZapSign are legally valid in their respective jurisdictions. The signature is legally valid in the US, EU, Latin America, with few exceptions. to learn about the legal validity of signatures in each country

If you haven’t yet integrated with ZapSign, we recommend starting with the testing environment (sandbox) by to avoid charges.

API Implementation Essentials

Time Management

  • UTC+0 Time Zone: Our server stores dates and times in the UTC+0 time zone. Most frameworks and browsers automatically perform this conversion when dealing with datetime objects.

For any questions, please contact our support team via or by email at support@zapsign.com.br. You can also for customized solutions.

Chat with Gepeto!

Have any questions? Use our artificial intelligence trained with all the API documentation. =)

Click here
clicking here
WhatsApp
speak with our specialists
LogoChat
Cover

We work with a REST API that uses GET and POST methods. All data is read in JSON, and our responses are also in JSON.

Cover

Null Strings: Our API does not accept strings defined as null. If a field is defined as a string, do not send it as null. If you want the field to be empty, send it as an empty string ("") or simply omit it from your request.

Cover

Booleans vs. Strings: true and false (booleans) are not equivalent to "true" and "false" (strings). Be sure to use the correct type to avoid test failures.