Skip to main content

GET {{baseUrl}}/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/documents/combined is not working for us and we need enhancements.

In our contracting process we want to assemble and reuse templates as much as possible.

The boilerplate language of the agreement is a template with tabs.

Our Exhibit A is a listing of arable fields that a farmer operates and may be eligible for a carbon program.  We generate and add this document via the API

Exhibits B, C and D are reuseable templates.

We may optionally add sensitive documents such as the IRS W-9 template, and our ACH enrollment forms.  These sensitive documents need to be captured and place in a secure Azure container, with only authorized individuals allowed to see (PII).  

The business does NOT want to send multiple envelopes.  These are farmers, and sometimes the only computer they have is in the tractor cab or their cellphone.

We need to add query parameters to the combine resource to specify s{“documentId”: “1”, “sequenceId”:”1”},{“documentId”: “2”, “sequenceId”:”2”},{“documentId”: “3”, “sequenceId”:”3”}, “documentId”: “4”, “sequenceId”:”4”}, {“documentId”: “5”, “sequenceId”:”5”}], and retrieve the remaining directly.

The existing combine feature is too basic.  Support has suggested use this Idea platform.

That's a great idea, and it's really useful for a business scenario like yours.

 

FreeLink/甫连信息

🌍 Docusign Partner | Partner Profile

🏆 Docusign 2024 APAC Reseller Growth Partner of the Year

🌟 The only Docusign Partner globally certified as both a Certified eSignature Administrator and eSignature Technical Consultant.

📊 Docusign Community Leaderboard Top 5 contributor.

🚀 Expertise in Docusign integrations with on-premises systems for leading enterprises across various industries.