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
  • Using Postman
  • Using Insomnia

Was this helpful?

Ready-to-use requests!

Postman and Insomnia are powerful tools for developing, testing, and documenting APIs. At ZapSign, we've prepared complete request libraries for both platforms to streamline your workflow.

PreviousZapSign EnvironmentsNextAuthentication

Last updated 8 months ago

Was this helpful?

Using Postman

You can save a lot of time by using the pre-built requests available in Postman.

Once the environment is selected, simply configure your variables by clicking on "Environments" in the left-hand menu.

With Postman configured, you're ready to use all the endpoints. The only mandatory variable is the api_token, your authentication token. All other variables can be filled in as needed.

Using Insomnia

For Insomnia, we’ve prepared all the endpoints in this file. After importing the file, you’ll need to select the environment and input your API token before making a request.

In Insomnia, press Shift+Ctrl+G while viewing a request, and the code will be automatically generated in any programming language you choose.

After opening the link, select the environment you want to test from the top right corner and create a fork to access all the endpoints within your own workspace.

In the right sidebar menu, the </> code icon allows you to export all requests in your preferred language.

File import with all requests for Insomnia.
LogoPublic API | ZapSign Public WorkspacePostman
17KB
Insomnia_2023-03-27.json
Insomnia ZapSign API.json