Adobe Sign APIConnect Adobe Sign without building on its API
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. If you're reading the docs because you need Adobe Sign 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 Adobe Sign and your other tools.
- APIREST (JSON)
- AuthOAuth 2.0
- AccessPaid plan to go live
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.
Building on the Adobe Sign API vs. having Caddi run it
| The job | Build it on the API | With Caddi |
|---|---|---|
| Getting access | Register an app, get Adobe Sign credentials, and manage tokens and refreshes. | Connect your Adobe Sign 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 Adobe Sign 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 Adobe Sign work off someone's desk, the build is the slow part.
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.
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. Where a step has no API, Caddi uses a secure, audited browser session in the same automation.
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.
Connect Adobe Sign without the build.
Drop your work email and pick a time. We'll show you Caddi running your Adobe Sign workflow end to end.