Demo account – Envelopes sent via API but recipients do not receive any email notifications

​@Rob1_862 

Email delivery problems are usually tied to DocuSign notification handling, throttling, recipient-side filtering, or recipient configuration, not the source IP that made the API call. Also, if your API calls are still succeeding normally, that argues against a simple IP block on your integration traffic.

Can you check if your recipients are being created with clientUserId, DocuSign treats them as embedded/captive recipients, and that changes how notification works. That is a classic reason “sent” envelopes appear fine but no email is expected. https://support.docusign.com/s/articles/DocuSign-Developer-FAQs-eSignature-API?language=en_US

Thanks for your response. I actually did quite a bit of research before posting this message, and I noticed that this clientUserId thing kept coming up. I’m not sending that field at all in my API calls. The IP-related issue also seems unlikely to me. What I don’t understand is why it was working before and then, from one day to the next, without any changes to the DocuSign configuration or the code, it stopped working.

​@Rob1_862 

Use unique email addresses you have never used before in recent demo testing, and slow the cadence down.

I got the same issue. I came back to add feature to my existing app, and the emails are broken, I cannot test it. They are never sent to the recipients, so the fault is on Docusign side. They must have changed something without notifying us

Hi everyone,

I'm running into exactly the same issue on my Developer (demo) account, and I wanted to add my report here so it's clear this isn't an isolated case.

My scenario matches what ​@Rob1_862  and ​@nekoenko described almost exactly. I create envelopes from a template with 2 or 3 signers in sequential routing order. Recipient emails are correct and verified (I tested with Gmail, Outlook and corporate domains). The API call returns success and the envelope status shows as "Sent" in the envelope history, and the history even confirms the email was dispatched to the first signer's correct address. But no email ever arrives. Not in Inbox, not in Spam, not in Promotions, not in any folder. Since routing is sequential, signers 2 and 3 are never notified either.

I've already ruled out the usual suspects: addresses are correct (double-checked character by character), I checked Spam, Promotions and All Mail across multiple providers, I'm not sending clientUserId so recipients aren't being treated as embedded/captive, account-level email suppression is off, and I also tested with completely fresh email addresses I'd never used before.

Like ​@nekoenko  mentioned, this really looks like something changed on DocuSign's side. Nothing on my end has changed. And the fact that several developers are reporting the exact same pattern within the past month (envelope marked Sent, zero email delivery, no errors in the API) points more to a sandbox-side deliverability issue than to individual misconfigurations.

Could someone from DocuSign please confirm whether there have been recent changes to email delivery, throttling or suppression rules on demo accounts? An official update on this thread would really help, since it's blocking multiple developers from completing their integrations. I'm also happy to share my Account ID, Base URI and failing envelope IDs privately (via DM or whichever secure channel you prefer) so you can check internal delivery logs on your side. Just let me know how you'd like me to send them.

For context, my environment is a Developer Sandbox (demo) account in the North America region (demo.docusign.net). This is currently blocking my evaluation of DocuSign for a production rollout, so any official guidance would be highly appreciated.

Thanks!

Hey, in my case it started working ∼2 days ago. On my end I didn’t change anything, just came back again to test some new stuff.