Integrate the Docusign API.Caddi writes and runs the integration for you.
Docusign has a REST API. Free self-serve developer (demo) account for building; going live requires a paid production account (Enterprise or API plan, not a free trial) and passing Go-Live review.
- 99%of agent runs complete successfully
- ~45 minon average to build your first agent
- 1M+back-office tasks completed
The connection is a project before it does anything.
Before the first record moves: an app registration, credentials, token refresh, and somewhere to host and monitor the code. Default of 3,000 API calls per hour per account across all apps, plus a burst limit, raisable via the API Usage Center.
Register an app, store Docusign credentials, refresh tokens and code around the rate limits.
Connect your Docusign account once. Caddi holds the connection.
The job doesn't stop at Docusign.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Docusign API only reaches Docusign.
Each extra system is another API, another set of credentials, another integration to own.
One automation runs across every tool the job touches, each through its API.
Someone has to own the code.
API versions change, fields get added and your process moves. Envelopes sent from a developer account do not produce legally binding signatures.
A developer patches and redeploys the integration each time.
The person who does the work updates it by showing or describing the change. Every automation is reviewed before it runs in production, and every run is logged.
What the Docusign API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (Authorization Code Grant or JWT Grant)
- Who can get access
- Free self-serve developer (demo) account for building; going live requires a paid production account (Enterprise or API plan, not a free trial) and passing Go-Live review.
- What it covers
- Envelopes, documents, recipients, tabs, templates, users, accounts, and Connect webhooks for eSignature workflows.
- Limits
- Default of 3,000 API calls per hour per account across all apps, plus a burst limit, raisable via the API Usage Center.
- Worth knowing
- Envelopes sent from a developer account do not produce legally binding signatures.
Official docs: developers.docusign.com. Checked September 2026. Vendors change access terms, so confirm with Docusign before you build.
When to build the Docusign integration in-house
When you have engineers and the integration is your product, or you need one narrow sync between two systems and someone to own it. When the goal is getting Docusign work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the Docusign API for
Model Selection Forms
Caddi pulls household and account details to populate a model selection form and sends it for signature, reducing manual form prep for advisor teams.
Signed Model Form Archiving
Caddi collects signed model selection forms and archives the final PDFs with the right metadata, reducing manual follow-up and filing for advisor teams.
Signed IPS Archiving
Caddi downloads signed investment policy statements, archives the PDFs with the right metadata, and updates the related household record and task.
Retainer Agreement Drafting
Caddi pulls client and offer details to populate a retainer agreement and sends it for signature, reducing manual contract prep for intake teams.
Everything Caddi does with Docusign.
Docusign API questions
Does Docusign have an API?
Yes. Docusign has a REST API, authenticated with OAuth 2.0 (Authorization Code Grant or JWT Grant). The official documentation is at https://developers.docusign.com/docs/esign-rest-api/.
How do I get access to the Docusign API?
Free self-serve developer (demo) account for building; going live requires a paid production account (Enterprise or API plan, not a free trial) and passing Go-Live review.
Does the Docusign API have rate limits?
Default of 3,000 API calls per hour per account across all apps, plus a burst limit, raisable via the API Usage Center.
Can I connect Docusign to my other tools without writing code against its API?
Yes. With Caddi you show the Docusign task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Docusign and the other tools the job touches. Steps that need a person's judgment are handed to Copilot or Claude, and Caddi monitors those too.
Do I need a developer to automate Docusign with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Docusign is reviewed before it runs in production, and every run is logged.