SAP Cloud Platform Open Connectors

DocuSign Authenticate a Connector Instance

On this page

You can authenticate with DocuSign to create your own instance of the DocuSign connector through the UI or through APIs. Once authenticated, you can use the connector instance to access the different functionality offered by the DocuSign platform.

Authenticate Through the UI

Use the UI to authenticate with DocuSign and create a connector instance. Because you authenticate with DocuSign via OAuth 2.0, all you need to do is add a name for the instance and enter the credentials you identified in DocuSign API Provider Setup. After you create the instance, you'll log in to DocuSign to authorize SAP Cloud Platform Open Connectors to access your account. For more information about authenticating a connector instance, see Authenticate a Connector Instance (UI)

After successfully authenticating, we give you several options for next steps. Make requests using the API docs associated with the instance, map the instance to a virtual data resource, or use it in a formula template.

Authenticate Through API

To provision your DocuSign Connector, use the /instances API.

Step 1. Call the /instances API

  • HTTP Headers: Authorization- User , Organization
  • HTTP Verb: POST
  • Request URL: /instances
  • Request Body: Required – see below
  • Query Parameters: none

Description: token is returned upon successful execution of this API. This token needs to be retained by the application for all subsequent requests involving this connector instance.

A sample request illustrating the /instances API is shown below.

HTTP Headers:


This instance.json file must be included with your instance request. Please fill your information to provision. The “key” into SAP Cloud Platform Open Connectors DocuSign is "docusign". This will need to be entered in the “key” field below depending on which Connector you wish to instantiate.

  "element": {
    "key": "docusign"
    "configuration": {
    "username": "<INSERT_DOCUSIGN_USERNAME>",
    "password": "<INSERT_DOCUSIGN_PASSWORD>",
    "oauth.api.key": "<INSERT_DOCUSIGN_INTEGRATOR_KEY>",
    "docusign.environment": "<INSERT_DOCUSIGN_ENVIRONMENT>"
  "tags": [

Here is an example cURL command to create an instance using /instances API.

Example Request:

curl -X POST
-H 'Authorization: User <INSERT_USER_SECRET>, Organization <INSERT_ORGANIZATION_SECRET>'
-H 'Content-Type: application/json'
-d @instance.json

If the user does not specify a required config entry, an error will result notifying her of which entries she is missing.

Below is a successful JSON response:

  "id": 12,
  "name": "Test",
  "token": "cuED0/DezalhhzK2OtO6kMP7NvPnMyNcRDZc=",
  "element": {
    "id": 161,
    "name": "DocuSign Beta",
    "key": "docusign",
    "description": "The future of business is digital. DocuSign helps businesses of all sizes easily and securely sign, send, and manage documents in the cloud, with unmatched availability and legal enforceability.",
    "image": "",
    "active": true,
    "deleted": false,
    "typeOauth": false,
    "trialAccount": false,
    "hub": "esignature",
    "parameters": []
  "provisionInteractions": [],
  "valid": true,
  "disabled": false,
  "maxCacheSize": 0,
  "cacheTimeToLive": 0,
  "configuration": {
    "base.url": "",
    "oauth.token.url": "https://{docusign.environment}",
    "pagination.max": "100",
    "event.vendor.type": "polling",
    "oauth.scope": "api",
    "oauth.user.token": "DOCUSIGN_USER_TOKEN",
    "pagination.offset": "false",
    "password": "DOCUSIGN_PASSWORD",
    "event.notification.callback.url": null,
    "event.poller.refresh_interval": "5",
    "oauth.user.refresh_token": null,
    "event.poller.urls": "envelopes|/hubs/esignature/envelopes?where=from_date='${gmtDate:yyyy-MM-dd'T'HH:mm:ss'Z'}'",
    "oauth.user.refresh_interval": "3600",
    "oauth.api.key": "DOCUSIGN_ITEGRATOR_KEY",
    "oauth.user.refresh_time": null,
    "docusign.environment": "demo",
    "username": "DOCUSIGN_USERNAME",
    "event.notification.enabled": "false"
  "eventsEnabled": false,
  "cachingEnabled": false

Note: Make sure you have straight quotes in your JSON files and cURL commands. Please use plain text formatting in your code. Make sure you do not have spaces after the in the cURL command.

Instance Configuration

The content in the configuration section or nested object in the body posted to the POST /instances or PUT /instances/{id} APIs varies depending on which connector is being instantiated. However, some configuration properties are common to all connectors and available to be configured for all connectors. These properties are -

  • event.notification.enabled: This property is a boolean property, and determines if event reception (via webhook or polling) is enabled for the connector instance. This property defaults to false.
  • event.vendor.type: When event.notification.enabled property is set to true, this property determines the mechanism to use to receive or fetch changed events from the service endpoint. The supported values are webhook and polling. Most connectors support one mechanism or the other, but some like support both mechanisms. This property is optional.
  • event.notification.type: This property can be used to determine how an event notification should be sent to the consumer of the connector instance, in most cases your application. Currently, webhook is the only supported value for this property. This means that when an event is received by the connector instance, it will get forwarded to the provided event.notification.callback.url via a webhook to you. This property is optional.
  • event.notification.callback.url: As mentioned above, the value of this property is an http or https URL to which we will post the event for consumption by your application. This property is optional.
  • filter.response.nulls: This property defaults to true, i.e., it's boolean property, and determines if null values in the response JSON should or should not be filtered from the response returned to the consuming application. By default, all null values are filtered from the response before sending the response to the consuming application.