If you are running your eSignature flows through APIs, you have probably hit this annoying edge case: everything in your automation works perfectly until a signer takes a bit longer than expected. The document quietly expires even though the deal is still very much alive.

This is exactly where extending document expiry via API becomes a lifesaver. Instead of treating expiry as a fixed setting, your services can adjust it on the fly based on what is actually happening in your systems—an opportunity still in pipeline, an approval waiting on a manager, or a contract stuck in legal review.

In this blog, we will walk through how a simple BoldSign API call to extend expiry can keep your signing processes running smoothly, without brittle hacks, noisy retries, or frustrated stakeholders.

Why extend a document expiry?

• Prevent unintended expiry: Give signers more time if they are unavailable or miss the deadline.
• Support ongoing negotiations: Keep documents active while discussions continue.
• Avoid resending documents: Update the expiry without recreating templates or configuring fields again.
• Ensure compliance: Regulated workflows often require extended review time.

Expiry types in BoldSign

BoldSign supports three expiry configurations:

• Days: yyyy-MM-dd (e.g., 2025-10-15)
• Hours: Integer (e.g., 12)
• Specific date and time: ISO format (e.g., 2025-10-15T10:58:04Z)

How to extend the expiry with the BoldSign API

To extend expiry:

• The document must be unsigned.
• New expiry must be greater than or later than the current expiry.
• Expiry cannot exceed 180 days from document creation.

You will first retrieve the current expiry configuration and then update it with a new value through the API.

Refer to the documentation to install the SDKs for your application’s technology stack. After installation, generate your API key in BoldSign. Use the API key generation guide for detailed steps.

Step 1: Get document properties

• Before extending a document’s expiry date, you must first check its current expiryDateType and expiryValue. Retrieve the document properties by using the BoldSign API.
• Use the following endpoint: GET /v1/document/properties
• 👉 You can refer to the official documentation here: Get Document Properties API
• This API call returns all relevant details about the document, including any forms added—such as signature or text fields—as well as the expiry configuration (expiryDateType and expiryValue).

Step 2: Extend the expiry date

After you find out the expiryDateType, you can use the code snippets below to update the document expiry date by using the API.

curl -X PATCH "https://api.boldsign.com/v1/document/extendExpiry?documentId={documentId}"
-H 'X-API-KEY: {your API key}'
-H "Content-Type: application/json"
-d "{\"newExpiryValue\": \"2025-12-15\", \"warnPrior\": true}"

Important properties and rules for updating expiry dates

To ensure a successful update, follow these rules:

• documentId : The ID of the document to update.

• newExpiryValue : Format depends on the original expiry type:

• Days → yyyy-MM-dd

• Hours → Integer value

• Specific Date & Time → ISO format

• warnPrior :

• true: Sends reminder 1 day before expiry

• false: Disables reminder

• null: Keeps existing configuration

• New expiry must be greater than or later than the current expiry.

• Expiry must not exceed 180 days from document creation.

A successful update returns 200 OK with the new expiry details.

Key benefits of extending document expiry

• Greater flexibility: Adjust expiry dates to match changing project timelines or client availability without starting over.
• Improved completion rates: Giving recipients more time increases the chances of getting documents signed and returned.
• Better user experience: Signers appreciate having extra time, especially when delays are unavoidable.
• Enhanced workflow efficiency: Keeps your document pipeline moving smoothly without interruptions due to expired links.

Conclusion

Delays are inevitable—but restarting your signing workflow doesn’t have to be. With BoldSign expiry extension API, you can adapt to everyday challenges and keep your documents moving forward.

Ready to try it?

View the API Reference in the BoldSign API documentation and sign up for a free sandbox account to get started.

Related blogs

• REST API vs SDK: Which is Best for eSignature Integration
• Explore BoldSign eSignature APIs in Postman: A Step by Step guide
• Exploring the API Trenches: Overcoming Challenges in API Integration and Development

Note: This blog was originally published at boldsign.com