Skip to content

APIs

Do you have ideas or feedback to help improve our APIs, tools, or documentation? If so, we would love to hear from you. Please submit your idea using the form below.You can also vote for your favorite ideas suggested by others.

APIs

Categories

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

44 results found

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Postman collection for DocuSign APIs would be very helpful.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Hello,

    I am an onboarding consultant, and my client has feedback in regards to the Pipedrive integration with Docusign Esignature:

    1. To apply a template: we have separate clicks to go back to parts of the first page of the envelope. So to change the document/apply template, to change recipients and to change the email message, can be done separately. Yet you can't go back to the first page. That is a bit annoying, can this feedback be taken into consideration, or forwarded to the Pipedrive feedback team ?
    2. Pipedrive and Docusign Integration does not work with Safari.. can this be…
    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. The formula field does not update when previewing envelopes. So currently the only way to test that the formula is correct is by sending a test envelope.
    It would be nice if there where a way to update all formula fields in the envelope while previewing

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Including the "includeData" field in a JSON webhook notification gives lots information of documents. Unfortunately, it includes the request of "pdfBytes" - binaries of the document files themselves.

    This is problematic because it will transfer a large volume of data, which we don't need (and it's not recommended to send document data via webhooks).

    It would be great to see DocuSign connect updated so that we can receive the "envelopeDocuments" field from webhooks excluding the pdfBytes field.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. I just solved an issue with my python code using
    docusign-esign-python-client, where I was attempting to create a document with a SignHere field, and the field would not show up.

    It turns out I pulled a signature field example from a different language which used camelCase for variables instead of snake_case.

    This was extremely hard to pin down though because nothing errored. The python client happily took my SignHere() class definition. And if the API errored in any way during creation it was not presented to me.

    I ended up having to call a bunch of other methods and try…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3
  • Don't see your idea?