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

25 results found

  1. 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)
  2. 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)
  3. 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)
  4. 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

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

    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 Next →
  • Don't see your idea?