DocuSign is retiring the listRecipientNamesByEmail API endpoint as part of improvements to its system architecture and security posture.
Nintex has already updated DocGen to support this change. Most customers do not need to take action.
You only need to review this change if you use the DocuSign Delivery Option in Nintex DocGen for Salesforce.
Who should review this?
This change only applies to customers using the DocuSign Delivery Option in Nintex DocGen for Salesforce.
If you use any other delivery option, no action is needed.
What’s changing?
The only change is how recipient names are resolved for DocuSign delivery.
Before the change:
If the recipient name configured in DocuSign was different from the recipient name configured in your DocGen Package, the DocuSign name would override it.
After the change:
The recipient name configured in your DocGen Package delivery option is used as-is. Recipient names configured in DocuSign will no longer override it.
Recommended action
If you use the DocuSign Delivery Option, test your DocGen Packages in Demo/Sandbox after July 7, 2026.
We recommend validating DocuSign delivery for any packages where recipient names are important, especially if your recipient names may differ between DocuSign and your DocGen Package configuration.
During testing, confirm that:
-
DocuSign delivery completes successfully
-
Recipient names appear as expected
-
Any templates or processes that rely on recipient names continue to behave as expected
Timeline
| Date | What happens |
|---|---|
| May 28, 2026 | Nintex deploys updates to address the DocuSign change |
| July 7, 2026 | DocuSign removes the API from Demo/Sandbox environments |
| July 7 - July 15, 2026 | Testing window to validate DocuSign delivery in Sandbox |
| July 23, 2026 | DocuSign removes the API from Production environments |
Questions?
Open a support case through the Nintex Support portal and reference “DocuSign API deprecation.”
For more details, refer to DocuSign deprecation announcement.