Ensuring documents are signed on time is essential. Setting an expiration date adds a layer of security to the document, ensuring it is only valid for a specified period.
You can configure an expiration date for your document through the BoldSign API by specifying the expiration value with the expiration date type. Once the expiration date is reached, the document will no longer be available for signing.
Code snippets
Let’s see how to add expiration date via the BoldSign API in various programming languages.
Curl
curl -X 'POST' \
'https://api.boldsign.com/v1/document/send' \
-H 'accept: application/json' \
-H 'X-API-KEY: {your API key}' \
-H 'Content-Type: multipart/form-data' \
-F 'Message={document message}' \
-F 'Signers={
"name": "alexgayle",
"emailAddress": "alexgayle@boldsign.dev",
"signerType": "Signer",
"formFields": [
{
"id": "textbox1",
"name": "textbox1",
"filetype": "Textbox",
"pageNumber": 1,
"bounds": {
"x": 140,
"y": 140,
"width": 82,
"height": 32
},
"isRequired": true
}
]
}' \
-F 'ExpiryDays={The number of days after which the document expires}' \
-F 'Files=@{your file}' \
-F 'Title={title}' \
-F 'ExpiryDateType={set the expirydatetype}' \
-F 'ExpiryValue={expiryvalue}' \
Other programming languages — check it on the BoldSign blog page.
Conclusion
Incorporating expiration date into document workflows is a strategic move towards ensuring efficiency, compliance, and security. Organizations may enhance productivity, reduce wait times, and retain document control by utilizing solutions such as BoldSign’s API.
Begin your 30-day BoldSign Free trial today and unlock its full potential. We value your feedback, so please share your thoughts below. If you have any questions or need more information about our services, don’t hesitate to Schedule a demo or reach out to our support team through our Support Portal.
Related blogs
- REST API vs SDK: Which is Best for eSignature Integration
- Explore BoldSign eSignature APIs in Postman: A Step by Step guide
- API Key Vs. OAuth – How to Choose the best Authentication
Note: This blog was originally published at boldsign.com
Top comments (0)