Docusign APIConnect Docusign without building on its API
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. If you're reading the docs because you need Docusign to talk to the rest of your stack, Caddi does that without you writing or maintaining integration code: you show it the job once, and it runs it across Docusign and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessPaid plan to go live
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.
Building on the Docusign API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Docusign credentials, and manage tokens and refreshes. | Connect your Docusign account once. Caddi holds the connection. |
| Writing the integration | A developer maps fields, handles pagination, retries and rate limits, and writes the sync. | You show Caddi the Docusign task the way you'd train a new hire. It writes verified code for it. |
| Steps the API doesn't cover | Screens with no endpoint stay manual, or need a separate RPA tool. | Caddi uses a secure, audited browser session where there's no API, in the same automation. |
| The other systems in the loop | Each extra tool is another API, another set of credentials, another integration to own. | One automation runs across all the tools the job touches. |
| Keeping it running | Someone owns the code when the API version, fields or your process change. | Every automation is reviewed before it runs in production, and every run is logged. |
Building on the API is the right call when you have engineers and the integration is your product. When the goal is getting Docusign work off someone's desk, the build is the slow part.
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.
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. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
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.
Connect Docusign without the build.
Drop your work email and pick a time. We'll show you Caddi running your Docusign workflow end to end.