Integrate the Adobe Sign API.Caddi writes and runs the integration for you.
Adobe Sign has a REST API. A free Developer Edition account is available for testing; Adobe says production API access needs an Enterprise-tier plan, and PARTNER apps that access other accounts must be certified.
- 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. Per-user limits per endpoint per minute, hour and day that scale with service plan (no numbers published), and polling of the same GET resource is capped at 3 identical calls per minute on Global/Enterprise/Developer tiers.
Register an app, store Adobe Sign credentials, refresh tokens and code around the rate limits.
Connect your Adobe Sign account once. Caddi holds the connection.
The job doesn't stop at Adobe Sign.
An intake, a filing or a client update also runs through email, documents and the other systems your team works in. The Adobe Sign API only reaches Adobe Sign.
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.
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 Adobe Sign API gives you
- Type
- REST (JSON)
- Authentication
- OAuth 2.0 (integration keys also exist for internal use)
- Who can get access
- A free Developer Edition account is available for testing; Adobe says production API access needs an Enterprise-tier plan, and PARTNER apps that access other accounts must be certified.
- What it covers
- Agreements, library templates, web forms, bulk sends (MegaSign), users, groups and webhooks.
- Limits
- Per-user limits per endpoint per minute, hour and day that scale with service plan (no numbers published), and polling of the same GET resource is capped at 3 identical calls per minute on Global/Enterprise/Developer tiers.
Official docs: developer.adobe.com. Checked September 2026. Vendors change access terms, so confirm with Adobe Sign before you build.
When to build the Adobe Sign 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 Adobe Sign work off someone's desk, the build is the slow part, and Caddi does it for you.
What teams usually want the Adobe Sign API for
Envelope prep from CRM data
Caddi pulls signer details from the CRM, populates the right Adobe Sign template, and sends the envelope to the correct contacts.
Signed-doc archive + record update
On signature, Caddi files the signed PDF in your DMS with the right metadata and closes the matching task in the CRM.
NIGO follow-up
When a signed packet is rejected, Caddi drafts the NIGO email, attaches the corrected pages, and re-sends through Adobe Sign.
Everything Caddi does with Adobe Sign.
Adobe Sign API questions
Does Adobe Sign have an API?
Yes. Adobe Sign has a REST API, authenticated with OAuth 2.0 (integration keys also exist for internal use). The official documentation is at https://developer.adobe.com/acrobat-sign/docs/overview/developer_guide/.
How do I get access to the Adobe Sign API?
A free Developer Edition account is available for testing; Adobe says production API access needs an Enterprise-tier plan, and PARTNER apps that access other accounts must be certified.
Does the Adobe Sign API have rate limits?
Per-user limits per endpoint per minute, hour and day that scale with service plan (no numbers published), and polling of the same GET resource is capped at 3 identical calls per minute on Global/Enterprise/Developer tiers.
Can I connect Adobe Sign to my other tools without writing code against its API?
Yes. With Caddi you show the Adobe Sign task once, the way you'd train a new hire, and Caddi builds it as verified code that runs across Adobe Sign 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 Adobe Sign with Caddi?
No. There is no integration code for you to write or maintain. Every automation Caddi builds for Adobe Sign is reviewed before it runs in production, and every run is logged.