DocuSign API: How to set "Reminders" and "Expirations" via JSON?

Understanding DocuSign API for Envelope Management

In the competitive landscape of electronic signature solutions, DocuSign’s API remains a cornerstone for developers integrating automated workflows into business processes. As companies scale their digital operations, features like reminders and expirations play a critical role in ensuring timely document completion without manual oversight. This article explores how to configure these settings via JSON in the DocuSign API, drawing from official documentation and practical implementation insights. From a business perspective, mastering these API elements can optimize contract cycles, reduce administrative burdens, and enhance compliance in high-volume environments.

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

Setting Reminders and Expirations in DocuSign API: A Step-by-Step Guide

DocuSign’s eSignature API allows developers to embed reminders and expiration rules directly into envelope creation requests. These features are essential for business automation, as they automate follow-ups and prevent indefinite document limbo, which can tie up resources in sales, HR, or legal teams. Reminders notify signers at set intervals if documents remain unsigned, while expirations void envelopes after a specified period, ensuring workflow efficiency.

Prerequisites for API Integration

Before diving into JSON payloads, ensure you have:

• A DocuSign developer account with API access (available via the Developer Center).
• Authentication set up using OAuth 2.0 or JWT for secure API calls.
• Familiarity with the Envelopes: create endpoint (POST /accounts/{accountId}/envelopes).

The API uses RESTful endpoints, and all configurations are passed in the JSON body of the request. Pricing for API usage falls under DocuSign’s Developer Plans, starting at $600/year for the Starter tier, which includes basic envelope quotas suitable for initial testing.

Configuring Reminders via JSON

Reminders are defined in the reminders object within the envelope definition. This object specifies frequency, delay before the first reminder, and the number of attempts. Businesses often use this to nudge signers in scenarios like client contracts or employee onboarding, reducing drop-off rates.

Here’s a sample JSON snippet for the envelope creation request:

{
  "status": "sent",
  "emailSubject": "Please sign this document",
  "documents": [
    {
      "documentBase64": "BASE64_ENCODED_DOCUMENT_CONTENT",
      "name": "Sample Agreement",
      "fileExtension": "pdf",
      "documentId": "1"
    }
  ],
  "recipients": {
    "signers": [
      {
        "email": "signer@example.com",
        "name": "John Doe",
        "recipientId": "1",
        "routingOrder": "1"
      }
    ]
  },
  "reminders": {
    "reminderDelay": 2,  // Days before first reminder (e.g., 2 days after sending)
    "reminderFrequency": "daily",  // Options: daily, weekly, monthly
    "reminderOffset": 1,  // Number of days between reminders
    "reminderMaxAttempts": 5  // Total reminders sent (e.g., 5 attempts)
  }
}

• reminderDelay: Sets the initial wait period in days. For time-sensitive deals, a value of 1-3 days is common.
• reminderFrequency: Dictates the interval—daily for urgent matters, weekly for standard contracts.
• reminderOffset: The gap between reminders, aligning with business cadences.
• reminderMaxAttempts: Caps the total to avoid spam; DocuSign recommends 3-7 based on envelope volume.

To implement, send this JSON via a POST request to the Envelopes API. For example, using cURL:

curl -X POST "https://demo.docusign.net/restapi/v2.1/accounts/{accountId}/envelopes" \
-H "Authorization: Bearer {access_token}" \
-H "Content-Type: application/json" \
-d '@envelope.json'

In practice, enterprises on the Advanced API plan ($5,760/year) benefit from higher quotas, allowing robust reminder logic in bulk sends. Testing in the sandbox environment ensures configurations align with compliance needs, such as audit trails for regulated industries.

Implementing Expirations via JSON

Expirations automatically decline unsigned envelopes after a deadline, freeing up API quotas and preventing resource waste. This is particularly valuable in high-velocity sales pipelines where documents might otherwise linger.

The expireAfter and expireNotify settings are nested under the envelope’s top-level properties or within recipient-specific configurations for granular control.

Sample JSON for expiration:

{
  "status": "sent",
  "emailSubject": "Action Required: Review and Sign",
  "documents": [
    // ... (same as above)
  ],
  "recipients": {
    "signers": [
      // ... (same as above)
    ]
  },
  "expireAfter": "30",  // Days until expiration (e.g., 30 days from send date)
  "expireNotify": true  // Whether to email the sender upon expiration (true/false)
}

• expireAfter: Specified in days (1-9999). Businesses set shorter periods (7-14 days) for urgent agreements to maintain momentum.
• expireNotify: Defaults to false; enabling it alerts the sender for follow-up actions, integrating seamlessly with CRM systems.

For recipient-level expirations (useful in multi-signer workflows), embed it in the signer object:

"signers": [
  {
    "email": "signer@example.com",
    "name": "John Doe",
    "recipientId": "1",
    "routingOrder": "1",
    "expireAfter": "15",  // Per-signer expiration
    "expireNotify": "1"  // Notify sender (1 = yes, 0 = no)
  }
]

Combining reminders and expirations creates a comprehensive lifecycle management strategy. For instance, a 30-day expiration with daily reminders after 5 days can boost completion rates by 20-30%, per industry benchmarks. Note that these settings consume envelope quotas—Standard plans limit to ~100 envelopes/user/year, so API users on Intermediate tiers ($3,600/year) gain flexibility for automated workflows.

Best Practices and Common Pitfalls

From a commercial standpoint, over-configuring reminders can increase SMS/add-on costs (metered at per-message rates), while lax expirations tie up seats in seat-based pricing models. Always validate JSON against the API schema using DocuSign’s Swagger docs. Pitfalls include timezone mismatches—use UTC for global teams—and ignoring decline reasons, which can be customized for better analytics.

In APAC regions, where latency and compliance add complexity, API integrations must account for regional add-ons like SMS delivery, potentially raising costs. Testing with sample payloads in the DocuSign sandbox is advisable before production deployment.

This API functionality underscores DocuSign’s strength in developer-friendly tools, though businesses should evaluate total costs, including automation caps (~10/user/month).

Competitive Landscape: eSignature Platforms Compared

As electronic signatures become integral to digital transformation, comparing DocuSign with alternatives like Adobe Sign, eSignGlobal, and HelloSign (now Dropbox Sign) reveals diverse strengths. DocuSign excels in global API robustness but faces scrutiny on pricing scalability, especially for API-heavy users. Adobe Sign integrates deeply with Adobe ecosystems, suiting creative workflows. eSignGlobal targets APAC with localized compliance, while HelloSign offers simplicity for SMBs.

Overview of Key Players

DocuSign: A market leader with comprehensive API features, including reminders and expirations as detailed above. Its strength lies in enterprise-grade security and integrations, but seat-based pricing can escalate for teams. The platform supports unlimited envelopes in higher tiers, though automation sends are capped.

Adobe Sign: Adobe’s solution emphasizes seamless integration with PDF tools and Acrobat, ideal for document-heavy industries. It offers similar API controls for reminders (via “notification” settings) and expirations (up to 999 days), with JSON payloads mirroring DocuSign’s structure. Pricing starts at $10/user/month for individuals, scaling to enterprise custom quotes. It’s particularly strong in North American compliance but may incur add-ons for advanced API usage.

eSignGlobal: This APAC-focused provider supports compliance in 100 mainstream global countries and regions, with a pronounced advantage in Asia-Pacific. The region’s electronic signature landscape is fragmented, with high standards and strict regulations—contrasting the more framework-based ESIGN/eIDAS in the US/EU. APAC demands “ecosystem-integrated” approaches, requiring deep hardware/API-level docking with government digital identities (G2B), far exceeding email verification or self-declaration models common in the West. eSignGlobal competes head-on with DocuSign and Adobe Sign worldwide, including in the Americas and Europe, through cost-effective plans. Its Essential version costs just $16.6/month (annual), allowing up to 100 documents for signature, unlimited user seats, and access code verification—all on a compliant, high-value basis. It integrates seamlessly with Hong Kong’s iAM Smart and Singapore’s Singpass, addressing regional pain points like data residency and latency.

HelloSign (Dropbox Sign): Acquired by Dropbox, it prioritizes user-friendly interfaces and file storage synergies. API support for reminders and expirations is available via JSON, with simpler quotas (e.g., 20 envelopes/month on free tiers). Pricing begins at $15/month for Essentials, appealing to small teams but less scalable for enterprise API needs compared to DocuSign.

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

Markdown Comparison Table

This table highlights neutral trade-offs: DocuSign for depth, Adobe for integration, eSignGlobal for regional value, and HelloSign for accessibility.

Final Thoughts on eSignature Choices

In summary, configuring reminders and expirations in DocuSign’s API via JSON streamlines business operations, but selecting the right platform depends on scale, region, and budget. For DocuSign users seeking alternatives, eSignGlobal stands out as a regionally compliant option with strong global reach.