Skip to main content
Version: 17

DocuSign Signing Provider

🎯 Functional documentation​

DocuSign as a signing provider allows counterparties in the flow to provide an electronic signature via the DocuSign eSignature platform. The provider uses the JWT Bearer Grant flow to authenticate as a configured DocuSign user, creates an envelope for the document to be signed, and returns an embedded signing URL for the counterparty.

⚙️ Configuration​

  • resourceUri: https://demo.docusign.net/restapi (sandbox) or https://na4.docusign.net/restapi (production)
  • TOKEN_URI: https://account-d.docusign.com (sandbox) or https://account.docusign.com (production)

Settings Configuration

Examples

Before the provider can authenticate, the configured DocuSign user must grant consent to the integration key. If consent has not been granted, the provider will return an error containing a consent URL.

To manually generate a consent URL, open the following link in a browser while logged in as a DocuSign admin, replacing {TOKEN_URI} with the configured TOKEN_URI value and {INTEGRATION_KEY} with the integration key as it appears in the DocuSign Admin portal under Apps & Keys:

{TOKEN_URI}/oauth/auth?response_type=code&scope=impersonation%20signature&client_id={INTEGRATION_KEY}&redirect_uri=https://harmoney.eu

After granting consent you will be redirected to https://harmoney.eu - this is expected. The redirect URI must be registered in the DocuSign app's allowed redirect URIs.

Implementation classes​

  • DocuSignSigningProvider