49 results found
-
Alternative to JWT grant that doesn't require API calls for authentication
Please provide an alternative to the JWT grant so my app doesn't need to make API calls to get an access token. For example, use the JWT itself as an access token.
GitHub, AWS, and others enable a static access string/key to be used for calls.
8 votes -
Add methods to support Shared Access functionality which went live September 2022
It's been 4 months since Shared Access went live and Shared Envelopes was deprecated. Confusingly, you have listSharedAccess and updateSharedAccess methods that do not support the enhanced Shared Access feature. Some of my users are anxious to take advantage of Shared Access, but I can't deploy it until the DocuSign API fully supports it. All I wanted for Christmas 2022 were new methods to update Shared Access settings. Please don't make us wait until next Christmas to deliver this overdue enhancement.
4 votes -
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 -
API Support: Shared Envelopes vs. Shared Access
We have been using the "Shared Envelopes" feature to allow specific users who are not the sender or a recipient of the envelope to be able to view an envelope in our applications without any issues. I used the following instructions to do so:
How to embed the DocuSign UI in your app: https://developers.docusign.com/docs/esign-rest-api/how-to/embed-ui/
This lays out using the SDK method Envelopes::createConsoleView.However, DocuSign has deprecated "Shared Envelopes" in favor of their new "Shared Access". We need "Shared Envelopes" to be maintained until the API is updated to support "Shared Access".
If this is not done API developers will have…
3 votes -
New Template Set Up
Simply speaking- Create a template for one envelope with one email notification for one signor with 2 sets of documents. The first set of documents are mandatory to sign in order to see the second set with out using document visibility. The tags must be signed in order.
We don't want to use Document Visibility
Due to CCR910, this will only start in California on 12/9/22. New York will follow soon.
3 votes -
Graphic change
Can we change the person on the webpage. I liked the graphic before. It was neutral and wasn't gender based. This is a webpage used for everyone of all genders and I think we should keep it that way.
3 votes -
3 votes
-
Delete Clickwrap Agreements by ID
Allow developers to delete responses (agreements/denials) to Clickwraps through the Click API
2 votes -
Add a property to an envelope so with a query you can get the envelopes that are used and deducted from the purchased amount of envelopes
Can your development team add a field in the envelopes object and call it "EnvelopeIsUsedForBilling" and have your automation set the value to yes when the envelope counts against the envelopes used from purchased envelopes?
We need to be able to see the actual envelopes used per employee. This way we can charge the docusign costs against our projects.2 votes -
Envelope Search
Instead of searching for envelope via "Shared Envelopes" (User by User) Create a seach for the entire DocuSign Accounht:
Account #9034273 Highland Capital Corporation (HCC)
Please let me know
2 votes -
Full Firefox compatibility
My company just started using DocuSign, and it looks really nice and handy! I find it insane however, that Firefox is not a "modern browser", and I either need to download an arbitrary smartphone app / another web browser (which is supposed to be built on standards?) to parttake in a simple videocall to verify my identity. I know it well it's easier to just support a single platform, but I personally don't like either Chromium, or technological monopolies that they are building. Please, consider giving users a free choice on an open web.
2 votes -
Html Tabs can have the same ID to Replicate data
According to https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/responsive/setting-tabs/.
We can create signable documents from an HTML definition.
The expected behavior is to be able to include tablLabels more than one time within the same document, replicating data for supplied tabLabels.
Example:
<div>{{"tabLabel": "StakeholderName"}}</div>
<div>{{"tabLabel": "StakeholderName"}}</div>Let's think of StakeholderName tab will be replaced by "Elon Musk" value, so the expected result should be:
<div>Elon Musk</div>
<div>Elon Mush</div>2 votes -
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 -
Recipient Colors
It would be nice if the Recipients default colors could be changed by senders during editing screens or the shades could be varied. Some of your visually challenged senders sometimes have issue distinguishing between the green and blue shades or even gray when placing radio, checkbox, or signatures and such.
2 votesThe accessibility team is planning to investigate and work on this issue in 2022.
DocuSign tracking number SIGN-27341
Thank you for the idea.
-
Postman Collection for ID Evidence API
Postman collection for DocuSign APIs would be very helpful.
2 votes -
captive recipient documentation
Really having trouble finding anything outside of oauth workflows.
Captive recipients should authenticate via an ISV app. This video talks about it: https://www.youtube.com/watch?v=0wdWMIXE9l8 however there's no matching documentation I could find other than https://developers.docusign.com/docs/esign-soap-api/esign101/embedding/captive-recipients/ which doesn't give an explanation on how to actually use it.
1 vote -
Sort domains in Admin profile editor
Sort domains in Admin section. In Docusign Admin under a user's profile section, when updating their email to another claimed domain, the domains are not sorted. This is cumbersome when an org has many domains.
1 vote -
The link for "Marke hinzufügen" (below in blue) is broken. http://now.eloqua.com/es.asp?s=566810826&e=49278225&elqTrackId=a0951024370a4562b8
The link for "Marke hinzufügen" (below in blue) is broken. http://now.eloqua.com/es.asp?s=566810826&e=49278225&elqTrackId=a0951024370a4562b8
1 vote
- Don't see your idea?