Back to Docusign.com
Here are some of the latest popular questions that developers asked in the Docusign Community for the month of November 2025.
Thread: Inquiry: Polling Violation
https://community.docusign.com/esignature-api-63/inquiry-polling-violation-25891
Summary: The developer is looking for guidance on the correct architectural pattern for checking envelope status without violating rules around excessive polling. Their proposed architecture is to call the Envelopes:get endpoint each time a recipient completes their assigned portion of the envelope. However, the developer is concerned that this could violate the envelope request limits.
Answer: Depending on how often the GET request is made, the developer may be able to implement the solution without exceeding the envelope request limits. However, the developer is describing a solution that relies on polling, which Docusign discourages. A better solution is to use Connect webhooks to receive updates when specific triggering events occur.
Thread: Not Receiving Identity Verification (Pending/Completed) Webhook Events — Only Envelope Events
Summary: The developer has set up a Connect configuration, and their app is receiving notifications for envelope and recipient events specified in the configuration. They also want the app to receive notifications for ID Verification (IDV). The developer subscribed to the identity-verification-pending and identity-verification-completed events, but their app isn't receiving notifications for these events.
Answer: The IDV events that the developer subscribed to are designed to be used specifically with IDV for EU qualified electronic signatures. At this time, there are no Connect events to support other kinds of IDV.
Thread: Embedded Signing Frame Fails to Load Due to CSP / Frame-Ancestors Issue (Works Only With Third-Party Cookies Blocked)
Summary: The developer is embedding an envelope in their app using focused view. When attempting to display the envelope in the iframe, the app receives a CSP violation error. The developer included these domains in the frameAncestors property:
https://our-domain.comhttps://demo.docusign.nethttps://apps-d.docusign.com
Answer: This issue can be resolved by removing https://demo.docusign.net from the frameAncestors property. For developer environments, the frameAncestors array should only include your site’s origin and https://apps-d.docusign.com.