Adobe Sign API Documentation
---
title: Adobe Sign API Documentation
description: Integrate Adobe Sign API Documentation through Atlas REST or MCP: PDF or DOCX upload, party binding, and signed PDF delivery.
date: 2026-06-15
updated: 2026-06-15
---
Developers search "adobe sign api documentation" when they need the official REST reference, not a sales deck. Adobe publishes Acrobat Sign API docs under Adobe Developer Console. This guide orients you to the v6 REST surface and maps common routes to Atlas equivalents for migration planning.
Share: Adobe docs cover agreements and transient documents. Atlas splits create and send with a review gate.
Where Adobe Sign API documentation lives
Adobe Sign REST API documentation is hosted on developer.adobe.com under Acrobat Sign API. The current major version is REST v6. Regional base URLs matter:
https://api.na1.adobesign.com/api/rest/v6/ https://api.eu1.adobesign.com/api/rest/v6/
Pick the shard assigned in Adobe Admin Console. Cross-region calls fail auth even with valid tokens.
Authentication docs cover OAuth integration keys and JWT service accounts. Scopes like agreement_read, agreement_write, webhook_read, and webhook_write gate each route family.
Core REST objects in Adobe docs
Adobe Sign API documentation centers on these resources:
| Resource | Purpose |
|---|---|
| transientDocuments | Upload PDF bytes before agreement create |
| agreements | Create, send, cancel signing workflows |
| libraryDocuments | Reusable templates |
| webhooks | Event subscriptions |
| workflows | MegaSign and bulk patterns on some tiers |
Agreement states include AUTHORING, IN_PROCESS, SIGNED, and CANCELLED. Docs explain PUT transitions between states.
Create flow from Adobe documentation
Adobe transient upload:
POST /transientDocuments Content-Type: multipart/form-data File: binary PDF
Then POST /agreements with fileInfos, participantSets, signatureType, and state.
Atlas equivalent splits upload and send:
curl -X POST https://atlaswork.ai/api/envelope \
-H "Authorization: Bearer $ATLAS_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: adobe-doc-migration-1" \
-d '{
"document_url": "https://example.com/msa.pdf",
"parties": [{"email": "signer@example.com", "name": "Signer", "role": "Customer"}]
}'
Response includes envelope_id and review_url. Send is POST /api/envelope/{id}/send after fields_status is ready.
See Adobe Sign REST API for endpoint-level detail and Adobe Sign API overview for auth patterns.
Status and download routes
Adobe GET /agreements/{agreementId} returns status and participant progress.
Atlas lightweight poll:
GET /api/envelope/{id}/status
Signed PDF download on Atlas uses envelope routes after status signed, or webhook payload references.
Webhooks in Adobe Sign docs
Adobe POST /webhooks registers callback URLs with webhookSubscriptionEvents arrays. Payload shapes vary by event type.
Atlas accepts webhook_url on create. Verify HMAC-SHA256 with X-Atlas-Signature header and your API key.
Error codes Adobe documents
Common Adobe Sign API error responses:
- INVALID_ACCESS_TOKEN: refresh OAuth
- INVALID_AGREEMENT_ID: stale id on retry
- UPLOAD_LOCKED: concurrent upload limits
Atlas returns 402 when credits exhaust, 409 on fields_version mismatch, 409 when send runs while fields_status is pending.
Wrap both clients with retries only on idempotent creates. Atlas supports Idempotency-Key header with 24-hour dedupe.
Rate limits and sandbox
Adobe API documentation publishes account-level rate limits that vary by license. Implement exponential backoff on HTTP 429.
Adobe sandbox licensing follows Adobe developer program rules. Atlas drafts are free. Production sends consume one credit each.
Route map for migration engineers
| Intent | Adobe Sign REST v6 | Atlas REST |
|---|---|---|
| Upload | POST transientDocuments | POST /api/envelope |
| Send for sign | POST agreements + state | POST /api/envelope/{id}/send |
| Status | GET agreements/{id} | GET /api/envelope/{id}/status |
| Void | PUT agreements state cancel | POST /api/envelope/{id}/void |
| Remind | POST reminders | POST /api/envelope/{id}/remind |
| Template send | libraryDocuments + agreements | POST /api/templates/{id}/send |
MCP alternative to raw REST
Agent clients can skip Adobe OAuth refresh with Atlas MCP tools:
- send_contract_for_review
- check_signing_status
- get_envelope
See MCP electronic signatures.
When to keep Adobe Sign API
- Adobe ETLA already covers Sign seats for every sender
- Legal requires Adobe audit exports you already run
- Workflows depend on Adobe library documents with strict governance
When Atlas fits alongside Adobe docs
- Engineering owns send volume and hates seat math on bots
- You want review_url on ad-hoc PDF or DOCX uploads
- Agents need MCP tools without building an Adobe wrapper
Sign up for five free sends. Full reference: e-signature API.
Adobe Sign API Documentation FAQ
Does Adobe Sign REST use JSON? Yes. REST v6 is JSON. Legacy SOAP is separate.
Which OAuth scopes do I need? Request agreement_read, agreement_write, webhook_read, webhook_write as needed. Least privilege wins.
Does Atlas mirror Adobe participant sets? Atlas uses parties array with email, name, role, and sequential order. Map roles at send time.
Bulk send in Adobe docs? MegaSign and bulk APIs are separate from single agreement create. Atlas template send handles repeat shapes.
PDF and DOCX on Atlas? Atlas accepts both at create. DOCX converts to PDF before signing.
Postman and OpenAPI
Adobe publishes Postman collections in developer docs. Import into team workspaces with secrets stored outside git.
Atlas OpenAPI lives at /openapi.json. Generate clients in TypeScript, Python, or Go from the same spec your QA team uses for contract tests.
FAQ
Does Atlas accept PDF and DOCX?
Yes on every create path.
How do I authenticate?
Bearer API key from dashboard settings.
When do credits get used?
One credit per send, not per upload.
Where is the full API reference?