Skip to main content
arrow-left Back to Docusign.com

Docusign is committed to maintaining exceptional levels of security and operability across all of its products and integrations. In keeping with this commitment, we will begin the migration of selected Embedded view API methods in line with our August 2024 Release.

This change is particularly important for our ISVs, as they address security issues when the API user differs from the application user. ISVs need to start planning to use the new API in new applications entering production later this year. Docusign will maintain backward compatibility for a limited time.

What is the impact on our ISVs? 

ISVs using the following eSignature REST API methods as part of their integrations will be impacted:

The CreateRecipient view, which is used for embedded signing, is not affected.

The expected workload to update the impacted applications is minimal. Docusign will provide detailed instructions as part of the documentation associated with these APIs, in line with the information available in these blog posts:

If you’re unsure about your integration using these methods, use the API Request Logging feature to check if your application makes any of these API calls. 

ISVs that use the License/Embed (OEM) business model bear the highest risk using the current APIs; ISVs that have created connectors are also vulnerable but to a lesser extent. Nevertheless, all ISVs should immediately take action on the updates as soon as practical.

Timeline of Changes:

  • August 2024: Docusign will deliver the API updates and documentation as part of the August 2024 release. Ensure you sign up for the Docusign Product Updates newsletter
  • October 2024: ISVs must have identified the need for migration for their existing integrations; all new integrations can only use the new versions of the API methods
  • November 2024: ISV License/Embed (OEM) partners to complete necessary migrations
  • February 2024: ISVs' general connectors to complete migration.

Hi ​@Mayar.Abounnaiem 

Thank you for the reminder. We find the release notes documentation and timeline regarding the migration requirements(Docusign Core Production Release Notes: 24.2.02.00 August 2024:Deprecation notice: Updates Required for API Integrations Using Embedded Sender, Edit, Correct, or Template Edit Views). We truly appreciate DocuSign’s commitment to providing clear guidance and support for partners like us.

 

We’ve identified that some of our customers fall under Category 3: At Risk, as defined in the documentation. These are organizations that have developed an integration for their own internal use. Many of them have leveraged our API integration consulting services to successfully integrate their business systems with DocuSign. However, the deadline for Category 3 applications is May 15, 2025, leaving nine months for necessary updates. With over three months already passed, a significant number of our customers have not yet started the migration process.

 

Larry’s blog posts have been incredibly beneficial, not only in helping us learn about new features but also in providing best practices for updating our integration solutions in alignment with these changes. We have also noticed similar reminders in the release notes, which have been instrumental in our preparation efforts. However, we would like to seek clarification on a specific concern raised by our customers regarding the DocuSign SDK.

 

Many of our customers are using DocuSign SDK version 3.21, which supports Java 1.8 due to their business system dependencies. Upgrading to DocuSign SDK versions beyond 6.x is not an option for them as it requires a newer JDK. They are seeking confirmation on the following critical point:

  • After the May 15, 2025 deadline, will API calls made via DocuSign SDK 3.21 to the impacted methods (Embedded Sender, Edit, Correct View) fail with errors?

If these calls are confirmed to fail, it will necessitate a migration to the REST API, which presents a considerable workload given their current dependencies. To mitigate this risk, it is imperative for our customers to finalize their migration plans at least one month before the deadline.

 

We would greatly appreciate it if you could confirm this scenario or connect us with Larry or another member of your internal team for further clarification. Your input is crucial for helping us guide our customers and ensure they meet the migration requirements on time.

 

Thank you once again for your continued efforts and support.

 

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.

Reply


Code of Conduct

Docusign Community

Code of Conduct