DocuSign API Documentation

---

title: DocuSign API Documentation

description: Start DocuSign API Documentation on Atlas REST: envelope lifecycle from draft through signed PDF without seat licenses. Includes five free sends on signup.

date: 2026-06-09

updated: 2026-06-09

---

Developers search "docusign api documentation" when they need REST paths, OAuth steps, and envelope payload examples. DocuSign publishes docs at developers.docusign.com under eSignature REST API. This guide orients you to the v2.1 surface and maps common calls to Atlas routes for side-by-side migration.

Share: DocuSign docs center on envelopes and tabs. Atlas uses detection plus review instead of manual tab arrays.

Where DocuSign API documentation lives

DocuSign eSignature REST API documentation covers:

• Authentication (OAuth authorization code, JWT, implicit legacy)
• Envelope create, send, void, and status
• Templates and bulk send
• Connect webhooks
• Admin and monitor APIs on separate doc trees

Base URL pattern:

https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/...
https://www.docusign.net/restapi/v2.1/accounts/{accountId}/...

Sandbox accountId differs from production. CI pointing at prod breaks limits quickly.

Envelope create in DocuSign docs

DocuSign API documentation shows POST /envelopes with:

• documents array (documentBase64 or template)
• recipients.signers with email, name, recipientId, routingOrder
• tabs (signHereTabs, dateSignedTabs, textTabs)
• status created for draft or sent for immediate dispatch

Minimal create example from DocuSign docs shape:

curl -X POST "https://demo.docusign.net/restapi/v2.1/accounts/$ACCOUNT_ID/envelopes" \
  -H "Authorization: Bearer $DS_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "status": "created",
    "documents": [{
      "documentId": "1",
      "name": "contract.pdf",
      "documentBase64": "JVBERi0x..."
    }],
    "recipients": {
      "signers": [{
        "email": "signer@example.com",
        "name": "Signer",
        "recipientId": "1",
        "routingOrder": "1"
      }]
    }
  }'

Response envelopeId anchors all follow-up routes.

Atlas create without tab arrays:

curl -X POST https://atlaswork.ai/api/envelope \
  -H "Authorization: Bearer $ATLAS_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: docusign-doc-map-1" \
  -d '{
    "document_url": "https://example.com/contract.pdf",
    "parties": [{"email": "signer@example.com", "name": "Signer", "role": "Customer"}]
  }'

Returns envelope_id and review_url. Send is separate POST /api/envelope/{id}/send.

See DocuSign create envelope API and DocuSign SDK guide.

Status and list routes

DocuSign GET /envelopes/{envelopeId} returns status, recipients, and timestamps.

Atlas equivalents:

Lightweight poll: GET /api/envelope/{id}/status returns signed_count, total, next_signer_email.

Connect webhooks in DocuSign documentation

DocuSign Connect delivers XML or JSON with configurable triggers. Common events: envelope-sent, recipient-completed, voided, declined.

Atlas sends JSON with HMAC signature header. Map envelope.sent, envelope.signed, envelope.voided, envelope.declined.

See DocuSign webhook guide.

OAuth section of DocuSign API docs

DocuSign API documentation dedicates pages to:

• Integration key registration
• Redirect URI allowlists
• Consent for impersonation
• JWT grant for server apps

Atlas uses Bearer API keys from dashboard settings. MCP clients use OAuth at /api/oauth for Claude and ChatGPT without per-bot DocuSign seats.

See DocuSign OAuth guide.

Common mistakes DocuSign docs warn about

Missing tabs. Create succeeds but signers see blank pages. Atlas avoids manual tabs with AI-assisted field detection and review UI.

Wrong accountId. Sandbox and production IDs differ.

Immediate sent in CI. Tests consume send quota. Prefer created status in sandboxes.

Base64 size limits. Large PDFs need chunked upload or alternative document sources.

Idempotency

DocuSign docs recommend client-side dedupe on envelope custom fields. Atlas supports Idempotency-Key on POST /api/envelope and send routes with 24-hour dedupe window.

Full lifecycle route map

MCP alternative

Agent clients skip raw REST with Atlas MCP tools:

• send_contract_for_review
• check_signing_status
• get_envelope

See MCP electronic signatures.

When to keep DocuSign API

• Connect integrations embed envelope IDs in dozens of services
• Legal blocked parallel vendors until full migration plan
• You rely on DocuSign recipient authentication options Atlas does not mirror

When Atlas fits while reading DocuSign docs

• Engineering owns send volume outside rep dashboards
• You want review_url before first send on new document shapes
• Agents need MCP without OAuth refresh middleware

DocuSign comparison for pricing context. Sign up for five free sends.

DocuSign API alternative (documentation lens)

Developers search "docusign alternative api" while reading official docs. They compare auth shape, tab model, webhook payloads, and seat pricing. Atlas alternative: Bearer API key, no accountId path segment, detection plus review instead of manual tabs, MCP tools for agents, one credit per send.

Use this guide for DocuSign route names. Use DocuSign REST API for verb-by-verb mapping. Use Migrate from DocuSign API for cutover checklists.

Envelope API alternative

"docusign envelope api alternative" searches focus on create, send, status, void. DocuSign envelope API is the core POST /envelopes surface documented above. Atlas maps create to POST /api/envelope, send to POST /api/envelope/{id}/send, status to GET /api/envelope/{id}/status, void to POST /api/envelope/{id}/void.

Create envelope API alternative

"docusign api create envelope alternative" is the first integration step. DocuSign requires documents plus recipients plus often tabs. Atlas accepts document_url or upload, optional parties at create, returns review_url before send consumes a credit.

Status API alternative

"docusign api status alternative" queries appear in poll loops. DocuSign GET /envelopes/{id} returns rich recipient detail. Atlas GET /api/envelope/{id}/status returns signed_count, total, next_signer_email for lightweight cron jobs.

Admin, Monitor, and CLM API alternatives

DocuSign splits admin, monitor, and CLM APIs into separate doc trees with different OAuth scopes. Teams search alternatives when they only need send/sign/status, not full CLM.

Atlas does not mirror CLM or monitor suites. It covers send, sign, void, remind, template repeat, and post-sign extract via REST and MCP. If your job is contract lifecycle management, incumbents still win. If your job is programmatic signature on PDFs, narrow APIs reduce integration surface.

Postman and OpenAPI

DocuSign developer portal ships Postman collections for envelope create and status routes. Pin environment variables for demo accountId separately from production.

Atlas publishes /openapi.json for the same routes your middleware will call in production. Import into Insomnia or Postman for shared team fixtures.

FAQ

Does Atlas use tab arrays? No. Detection proposes fields. Review confirms. DocuSign tabs are often explicit in API payloads.

Embedded signing? Atlas sign pages live at atlaswork.ai/sign. Link from your portal with party tokens.

Bulk send? DocuSign bulk jobs map to Atlas template bulk or repeated POST /api/templates/{id}/send.

API limits? See DocuSign API limits. Atlas charges one credit per send. Drafts free.

PDF and DOCX? Atlas accepts both at create. DOCX becomes PDF before signing.