View Products Overview

Collect information to use in contracts and agreements.

Create contracts swiftly through templates, AI, or create and edit your own.

Route contracts seamlessly for editing, review, and approval.

Easily work with internal and external participants to edit and redline contracts in real-time

Capture secure, compliant, and legally binding signatures on any device.

Connect to the systems you use daily, or build into your application with our APIs.

Answering Your Biggest Questions About the Docubee API

We are so excited to share our new Docubee API with you. With a new product like this, we know there are always new questions that pop up that need to be answered. So, we’ve been listening, and have broken down the answers to your burning questions.

Docubee API FAQs:

Q: What is the difference between a webhook and an API?
A: Developers use APIs to make requests of the application they are calling. They receive a response to that API request and have logic to process the response. 

Webhooks are similar, but they basically skip the request part. So, a webhook allows a developer to say “here’s a URL, send a message to it when ____ happens”. 

An example of this we can use for Docubee API would be getting a signed document. With an API, the calling application requests the status of the document from Docubee. Docubee responds telling the application “this document hasn’t been signed yet”, and then the application waits and asks again “what about now”. 

Once the Docubee response indicates that the document has been signed, another API is called to download the document. With a webhook, that same application goes “hey, send the document here once it has been signed” so when the document is signed, Docubee’s webhook automatically sends them the document.

Q: What warrants an API integration versus a webhook integration?
A: APIs are more granular and allow the calling application to poll Docubee and make decisions based on what is returned. One example use of an API that isn’t in a webhook would be to check the status of a document or workflow.

Q: What integration allows my company to send documents to my HRIS in addition to data collected by a Docubee workflow?
A: Either an API or a webhook. 

Q: Does Docubee receive data/documents from an API integration as well as send them?
A: Yes.

Q: With the API packages, do I get the same features and support as the Enterprise plan?
A: Yes, you do get the same level of support, as well as 10 hours of services that can be used to help you get up and running quickly with a workflow that can be called via the APIs.

If you didn’t see your question on this list or need more information about Docubee API, please reach out to us here. Someone from our support team will be happy to answer any of your questions or give you a quick demo if your question is a little more complex.