Back to Docusign.com
Here are some of the latest popular questions that developers asked on StackOverflow and Docusign Community in the month of August 2025.
Thread: Is it necessary to update BaseUri for Rest EndPoints because of the move to Azure
Summary: In light of the announcement that Docusign eSignature transactions are moving to Microsoft Azure, this developer is wondering if they need to make any changes to the base URI of the endpoints that they’re using.
Answer: With the move to Azure, the base URI is not changing. The only change that developers may need to make is that, if your organization restricts inbound network connections and allow-lists specific Docusign IP addresses, you’ll need to update your allow-list to include all current Docusign IP ranges.
- IP allow-listing: Make sure your allow-list includes all current Docusign IP ranges from our Trust Center by December 31, 2025 for both production and demo accounts.
- Note: If your production account is in AU, CA, or JP1, no action is required for production, but action is needed for demo accounts.
- Domain allow-listing: Update your settings to include the following subdomains:
- demo-b.docusign.net
- na1-b.docusign.net
- na2-b.docusign.net
- na3-b.docusign.net
- na4-b.docusign.net
- eu-b.docusign.net
Thread: Webhook Expired Events
https://community.docusign.com/esignature-api-63/webhook-expired-events-25189
Summary: The developer has set up webhooks to receive notifications about envelope events. This is working as expected, except when an envelope is voided due to being past its expiration date. The developer is not receiving any events when the envelope is voided and they want to know how to ensure that they are notified when that happens.
Answer: The events that your webhook subscribes to are determined by the Connect Configuration settings for that webhook. To receive events when an envelope is voided, be sure to check the box next to Envelope Voided in the list of events.
Thread: Docusign API RequestJWTUserTokenAsync - "No such host is known. (https:443)"
Summary: The developer is trying to use JWT authentication and keeps seeing the following error: No such host is known. (https:443). They’ve tried debugging with various methods but haven’t been able to find the root of the issue. However, they are able to call other endpoints of Docusign APIs successfully.
Answer: In this developer’s case, the problem was that they were using the incorrect base path for the authentication methods. If you try to use the base path for the eSignature REST API when authenticating, your call will be unsuccessful. In the demo environment, the base path for authentication should be account-d.docusign.com.