49 results found

1. 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 like:

   https://app.example.com/signingResults?event=signing_complete&HMAC=uhieondoid3el9u...

   The HMAC would enable verification and give the guarantee that the first part of the URL (https://app.example.com/signingResults?event=signing_complete) really was from DocuSign.

   Benefit: this would save making an API call to confirm that the signer really did sign during the embedded signing session.

   SCORE-594

   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… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  eSignature API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  eSignature API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  eSignature API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. 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 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  other  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   planned  ·  AdminLarry Kluger (Admin, DocuSign) responded

   The accessibility team is planning to investigate and work on this issue in 2022.

   DocuSign tracking number SIGN-27341

   Thank you for the idea.

5. SDK support for Admin API
   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  Admin API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Receive webhook events behind the firewall

   Connect sends webhook events by making an outbound request to a customer's server. The server must be accessible from the public internet.

   The host-a-server-on-the-public-internet requirement is very costly and forbidding to many customers. Their information security rules either prohibit such servers or often require expensive and slow procedures before a publicly accessible server can be installed. Then there are additional costs and complexities to make the incoming notification messages accessible to the business applications which live behind the firewall.

   This Idea: DocuSign could send the notifications to AWS Simple Queuing Service or similar PAAS queuing services. Customers can then, from behind the firewall, receive the notification messages. No changes to the customer's firewall is needed.

   There are code examples from DocuSign on how to do this, see https://www.docusign.com/blog/dsdev-webhook-listeners-part-4 but it'd be even better if a Connect webhook could be directly configured to work with AWS SQS or equivalents from the other major PAAS vendors.

   CONNECT-1646

   Connect sends webhook events by making an outbound request to a customer's server. The server must be accessible from the public internet.

   The host-a-server-on-the-public-internet requirement is very costly and forbidding to many customers. Their information security rules either prohibit such servers or often require expensive and slow procedures before a publicly accessible server can be installed. Then there are additional costs and complexities to make the incoming notification messages accessible to the business applications which live behind the firewall.

   This Idea: DocuSign could send the notifications to AWS Simple Queuing Service or similar PAAS queuing services. Customers can then, from… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  eSignature API  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Postman Collection for ID Evidence API

   Postman collection for DocuSign APIs would be very helpful.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   under review  ·  0 comments  ·  ID Evidence API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

9. 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

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  eSignature API  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close