Hello Kumar,
Yes, it is partially possible to achieve better sender identification and transparency in DocuSign emails using the DocuSign eSignature API, but directly replacing the docusign.net domain with a completely arbitrary sender email address for every envelope is generally not supported for security and deliverability reasons.

Here's a breakdown of what you can and cannot do, along with recommended solutions:

What is NOT Directly Possible:

• Dynamically Replacing docusign.net with Any Sender Email: DocuSign, like most reputable email service providers, implements security measures to prevent email spoofing. Allowing any user to arbitrarily set the "From" address to any domain would be a significant security vulnerability and would likely lead to deliverability issues (emails being marked as spam).

What IS Possible and Recommended Solutions:

While you cannot directly replace the docusign.net domain, you can significantly improve sender identification and transparency through the following methods using the DocuSign eSignature API:

1. Setting the Sender's Name:

   • You can use the emailSubject and emailBlurb properties when creating an envelope via the API. Clearly state the sender's name and potentially their company within these fields. This is the most straightforward and universally supported way to improve identification.
   • API Fields:
     • emailSubject: The subject line of the email sent to recipients. Include the sender's name or company here.
     • emailBlurb: The introductory text within the email body. Clearly identify the sender here.

2. Using Custom Branding:

   • DocuSign allows you to configure custom branding for your account. This branding can include your company logo and name, which will be visible to recipients within the DocuSign signing experience and potentially in some email notifications.
   • Configuration: This is typically configured within your DocuSign Admin settings, but the API can be used to manage some aspects of branding in more advanced scenarios.

3. Utilizing the signerEmail and signerName Properties:

   • When defining recipients (signers, carbon copies, etc.) in your envelope definition via the API, ensure you are accurately setting the signerEmail (the recipient's email) and signerName (the recipient's name). While this doesn't change the sender's domain, it ensures the recipient's information is correct.

4. Leveraging the customFields Feature:

   • You can use custom fields on the envelope to include information about the sender. While these fields are primarily for data collection, they can be displayed to recipients during the signing process, further clarifying the sender.

5. Implementing a Clear Communication Strategy:

   • Outside of DocuSign itself, establish a clear communication strategy with your recipients. Inform them beforehand that they will be receiving documents through DocuSign and that the email will originate from a docusign.net address but will clearly identify your company or the sender within the subject and body.

6. Investigating DocuSign Connect (Webhooks):

   • DocuSign Connect allows you to receive real-time notifications about envelope events. You could potentially use this to trigger a separate email from your own email system to the recipient, informing them that a document is awaiting their signature in DocuSign and clearly stating the sender's email address. However, this adds complexity and doesn't directly change the sender of the DocuSign email itself.
     
      

Thank you so much and if you need any help you can raise a support case anytime at https://support.docusign.com