DocuSign API: How to download the "Combined" PDF vs separate PDFs?

Understanding DocuSign’s API for PDF Downloads

In the competitive landscape of electronic signature platforms, DocuSign stands out as a leader for businesses handling high-volume document workflows. From small teams to enterprises, its API enables seamless integration into custom applications, automating everything from sending agreements to retrieving signed documents. A common challenge developers face is managing PDF outputs post-signing—specifically, downloading a “Combined” PDF (a single file merging all documents and signatures) versus separate PDFs for each envelope component. This article explores this API functionality in depth, drawing from DocuSign’s developer documentation and practical business use cases, while maintaining a neutral perspective on its implementation.

The Role of DocuSign API in Document Management

DocuSign’s eSignature API is part of its broader ecosystem, including tools like Intelligent Agreement Management (IAM) and Contract Lifecycle Management (CLM). IAM enhances security with features such as single sign-on (SSO), advanced audit trails, and identity verification, making it ideal for regulated industries like finance and healthcare. CLM, on the other hand, streamlines the entire contract process from creation to renewal, integrating with CRM systems for end-to-end visibility. These products underscore DocuSign’s focus on compliance and efficiency, but for developers, the API is the backbone for custom integrations.

When it comes to PDF downloads, the API provides endpoints that allow programmatic access to signed documents. This is crucial for businesses automating workflows, such as HR onboarding or sales contract fulfillment, where retrieving files quickly can reduce manual errors and speed up processes. The key distinction lies between a “Combined” PDF—which consolidates the original document, signer attachments, and certificate of completion into one file—and separate PDFs, which break down the envelope into individual components like the signed form or audit logs.

How to Download the “Combined” PDF Using DocuSign API

Downloading a Combined PDF is straightforward via the DocuSign eSignature REST API, particularly using the Envelopes API. This approach is preferred in scenarios where a unified file simplifies archiving or sharing, such as in legal reviews or client deliveries. Here’s a step-by-step guide based on DocuSign’s official API v2.1 documentation:

1. Authenticate and Obtain Access Token: Start by generating an OAuth 2.0 JWT token or using Authorization Code Grant. This ensures secure API calls. For production, integrate with your app’s backend to handle token refresh automatically.

2. Retrieve Envelope Details: Use the GET /envelopes/{envelopeId} endpoint to fetch the envelope status. Confirm it’s in a “completed” state before proceeding. The response includes document IDs and recipient details.

3. Request the Combined PDF: Call the GET /envelopes/{envelopeId}/documents/combined endpoint. This returns a single PDF that includes:

   • The original document(s) with applied signatures and fields.
   • Signer attachments (if any).
   • A certificate of completion summarizing the signing audit trail.

   Example cURL request (replace placeholders):

   curl -X GET "https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/combined" \
   -H "Authorization: Bearer {accessToken}" \
   -o combined.pdf
   

   The response is a binary PDF stream, which you can save directly. In code (e.g., Node.js with the DocuSign SDK), use the EnvelopesApi.getDocument method with the combined parameter set to true.

4. Handle Large Files and Errors: For envelopes with multiple documents, the Combined PDF can exceed 25MB—monitor API quotas (e.g., Starter plan allows ~40 envelopes/month). Implement error handling for 404 (not found) or 429 (rate limit) responses.

From a business perspective, this method streamlines compliance reporting. Enterprises using DocuSign’s Advanced or Enterprise plans benefit from enhanced features like Bulk Send integration, where Combined PDFs can be batched for mass distribution. However, note that automation sends are capped (e.g., ~10/month per user), so high-volume users may need custom Enterprise pricing.

Downloading Separate PDFs: When and How

In contrast, separate PDFs offer granularity, useful for workflows requiring isolated components—like extracting only the signed agreement for database storage or sending audit logs separately for regulatory audits. This approach uses the same Envelopes API but targets individual documents.

1. List Documents in Envelope: Query GET /envelopes/{envelopeId}/documents to get a list of document IDs. Each ID corresponds to a specific file, such as the main document (ID 1), attachments, or the completion certificate (often ID -1 for summary).

2. Download Individual PDFs: For each document, use GET /envelopes/{envelopeId}/documents/{documentId}. Specify the format as PDF in the query (e.g., ?format=pdf).

   Example:

   curl -X GET "https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes/{envelopeId}/documents/{documentId}" \
   -H "Authorization: Bearer {accessToken}" \
   -o document_{documentId}.pdf
   

   In SDKs like Python’s docusign-esign, loop through documents:

   api_instance = EnvelopesApi()
   results = api_instance.get_document(account_id, envelope_id, document_id, token)
   with open(f'doc_{document_id}.pdf', 'wb') as f:
       f.write(results)
   

3. Use Cases and Limitations: Separate downloads shine in modular systems, such as integrating with CLM for version control. However, they require more API calls, increasing latency and costs (API plans start at $600/year for Starter). For envelopes with conditional logic or Web Forms (Business Pro feature), ensure you fetch all relevant IDs to avoid incomplete sets.

Business observers note that while Combined PDFs reduce storage overhead (one file vs. multiples), separate PDFs enhance flexibility for analytics tools parsing specific sections. In APAC regions, where data residency rules vary, separate handling can aid compliance with local storage mandates.

Key Differences: Combined vs. Separate PDFs

This comparison highlights why businesses weigh efficiency against needs—Combined for speed, separate for precision.

Competitive Landscape: eSignature Platforms Compared

To contextualize DocuSign’s API strengths, consider alternatives like Adobe Sign, eSignGlobal, and HelloSign (now Dropbox Sign). Each offers API access for PDF handling, but varies in pricing, compliance, and regional focus. Below is a neutral comparison based on 2025 public data:

This table illustrates DocuSign’s enterprise edge but highlights cost and regional variances in competitors.

Comparing eSignature platforms with DocuSign or Adobe Sign?

eSignGlobal delivers a more flexible and cost-effective eSignature solution with global compliance, transparent pricing, and faster onboarding.

👉 Start Free Trial

Spotlight on Adobe Sign

Adobe Sign, part of Adobe Document Cloud, excels in creative and document-heavy industries. Its API supports Combined and separate PDF downloads similar to DocuSign, using endpoints like /agreements/{agreementId}/combinedDocument. Pricing starts low for basics but scales with users, making it suitable for marketing teams needing embedded signing in PDFs. However, it may require additional Adobe licenses for full CLM-like features.

Spotlight on eSignGlobal

eSignGlobal positions itself as a global player compliant in over 100 mainstream countries, with a strong advantage in the Asia-Pacific (APAC) region. APAC’s electronic signature landscape is fragmented, with high standards and strict regulations—unlike the framework-based ESIGN/eIDAS in the US/EU, APAC emphasizes “ecosystem-integrated” compliance. This requires deep hardware/API-level docking with government digital identities (G2B), a technical hurdle far beyond email verification or self-declaration common in the West. eSignGlobal has launched comprehensive competition plans against DocuSign and Adobe Sign worldwide, including in the US and Europe, offering competitive pricing. For instance, its Essential version costs just $16.6 per month, allowing up to 100 documents for electronic signature, unlimited user seats, and verification via access code—all while maintaining compliance. It seamlessly integrates with Hong Kong’s iAM Smart and Singapore’s Singpass, enhancing regional efficiency.

Looking for a smarter alternative to DocuSign?

eSignGlobal delivers a more flexible and cost-effective eSignature solution with global compliance, transparent pricing, and faster onboarding.

👉 Start Free Trial

Business Implications and Final Thoughts

For developers and IT leads, mastering DocuSign’s API for PDF downloads optimizes workflows but demands attention to quotas and costs—especially in API plans like Intermediate ($3,600/year) for advanced features. While DocuSign dominates enterprise spaces, alternatives provide viable paths for cost-sensitive or regionally focused operations. As a neutral recommendation, eSignGlobal emerges as a solid DocuSign alternative, particularly for regional compliance needs in APAC.