28 results found
-
Add CORS support
Add CORS support to the eSignature and other APIs. This will enable single page applications (including React, Angular, and related frameworks) to make API calls to DocuSign directly from the application running in the browser.
4 votes -
A new type of trigger event could be added to the Connect webhook system
We have a use case where if a signer does not sign a document for 3 days (or let us say N days), then the sender application should get an event notification on their webhook, stating that the signer has not signed the document after N days. This can be very similar to the signing_completed notification that we receive once all signers have signed the document. For more details, refer this question on SO - https://stackoverflow.com/questions/70978461/can-we-get-a-notification-if-the-signer-has-not-signed-the-document-for-3-days
1 vote -
eSignature message
It would be really handy & convenient if the "message" that was sent out to clients was also included on the "completed" version of the DocuSign as a full record of what was sent to the clients, also making it easier for the Sender to store a copy of the "message".
1 vote -
HMAC signature for embedded signing results
Today, after an embedded signing session is used, DocuSign redirects back to the developer's application and includes status on what happened (envelope signed or sign later, etc).
But the status can't be relied on since there's no way to know, for sure, that the redirect came from DocuSign (it could be a spoof from a bad guy).
THIS IDEA: in the createRecipientView API call, include an optional hmac_secret attribute. Then that attribute would be used to create an HMAC of the response URL and the HMAC would be included in the redirect URL.
So the redirect URL would look something…
2 votes -
Use PowerForms via an API
It would be great if I could make a GET or POST call to open a PowerForm for embedded signing and then receive back the envelope ID that was created.
The GET or POST call could optionally supply values for the template fields (tags).
This would be a much easier way to provide embedded signing for envelopes that can use a template.
FRM-1368
2 votes -
Finish button in Preview redirect to return URL.
The Finish button in envelope preview is currently disabled even after filling in signature fields. Would be nice if clicking this redirected to the return URL supplied.
2 votes -
Embedded Sending: full API control over features
There are now some API controls for the Embedded Sending app's features. See https://www.docusign.com/blog/developers/introducing-customizable-embedded-sending
This idea: provide FULL control via API including which Field types should or should not be shown in the tagger window, ability to hide the document settings gear icon, hide the Send and Save buttons, etc
EC-3420
1 vote -
API access to all Certificate of Completion data
Currently most of the data included in the Certificate of Completion (CoC) is available via the eSignature API but some is not.
This idea: DocuSign should audit and ensure that ALL the data in the CoC is programmatically available via the API.
1 vote
- Don't see your idea?