DocuSign connection guide for Jitterbit App Builder

Overview

This guide describes the system requirements and instructions for connecting App Builder to a Docusign Online database server as a prerequisite to being utilized as a service in an application.

System requirements

Database server

DocuSign Developer Account

Client web browser

• Chrome TM 60 or newer

• Firefox ® 55 or newer

• Safari ® 11.0.2 or newer

• Postman v9.10 or newer

Connection instructions

Acquire credentials from DocuSign sandbox

1. Login to DocuSign here: https://account-d.docusign.com/

2. Click on Settings on the top right corner of the landing page

3. On left hand sidebar, scroll down to Integrations and click on Apps & Keys

4. Create an application by clicking the ADD APP AND INTEGRATION KEY button.

   

5. Type in application name (this example is App Builder DocuSign)

6. Copy Integration Key and store for next step

   • You will also use the API Account ID and the Account's Base URI in later steps

7. Click on + ADD SECRET KEY button under Authentication and copy this value, you need this key and will not be able to view the whole key later.

8. Scroll down to Additional Settings and add this Redirect URI: https://oauth.pstmn.io/v1/callback (This is only applicable when using Postman, if using other API development tool, please reference their documentation)

9. Click Save

10. Click on Templates on the top bar menu

11. Click on New on the top left corner to create a new template to be used during the connection set-up

12. Name your template and upload a document, click Next; optionally, add signature areas to the document, then click Save.

13. Under the name of your new template, Click on TEMPLATE ID, copy and save this value, you will need this in a later step.

Acquire refresh token using postman

1. Create a new POST request with the following parameters:

   • URL: https://account-d.docusign.com/oauth/token>/

   • Authorization: Basic Auth

     • Username = Integration Key from previous section

     • Password = Secret Key from previous section

   • Body: x-www-form-urlunencoded

     • Key: grant_type

     • Value: authorization_code

     • Key: code

     • Value: *you will get this second value in the next step

2. In a web browser go to the following website and substitute in the values that are between < and >, i.e. <value>.

   https://account-d.docusign.com/oauth/auth?response_type=code&scope=signatureextended&client_id=<Integration Key from DocuSign Sandbox>&state=a39fh23hnf23&redirect_uri=https://oauth.pstmn.io/v1/callback
   

3. After hitting Enter with the above URI, copy what is in the URL field and paste it somewhere you can see the whole URL (it is extremely long). Copy the value after code= and before &state=, this is your code value, paste it into the Value from step 1 in this section and click Send in Postman. **This step needs to be done quickly, the refresh token from the web browser only lasts about 2 minutes. **

   

Set up refresh token API in App Builder

1. From the Connect menu, click on the Connect to your enterprise link

2. Click Data Servers on the left-hand side and click Create

3. Configure server as follows:

   • Name: Recognizable name

   • Type: REST API

   • URL: https://account-d.docusign.com

   • Request Content Type: Form

   • Response Content Type: JSON

   

4. Click Save.

Add an API endpoint

1. Close out of the Create Data Server pop-up, then click on the name of the Server you just created in the list of data servers.

2. In the Endpoints panel on the bottom left, click Create

3. Add the following details:

   • Name: Name your endpoint

   • Endpoint: /oauth/token

   • Method: POST

4. Next you will add the following endpoint parameters by clicking Create in the Endpoint Parameters panel in the top right and add the following details:

   • Parameter 1

     • Name: Authorization

     • Data Type: String

     • Test Value: Basic {Authorization from Postman}

       This value can be found in Headers tab in Postman after the POST call to retrieve refresh token. It will say basic followed by a long ID. (You might have to look in hidden headers)

     • Type: Header

     • Direction: Input

   • Parameter 2

     • Name: grant_type

     • Data Type: String

     • Test Value: refresh_token

     • Type: Query

     • Direction: Input

   • Parameter 3

     • Name: refresh_token

     • Data Type: String

     • Test Value: The refresh token you retrieved in Postman in the previous step

     • Type: Query

     • Direction: Input

   

5. Click Save

6. Click Test Connection to get access token for next step

7. Add to the sample input the Query parameters as follows:

   { "grant_type": "refresh_token", "refresh_token": "<refresh token from postman>"}
   

8. Click Import

Configure App Builder for DocuSign

1. From the Connect menu, click on the Connect to your enterprise link

2. Click Data Servers on the left-hand side and click Create

3. Configure server as follows:

   • Name: Recognizable name

   • Type: REST API

   • URL: https://demo.docusign.net/restapi (This is from the DocuSign Sandbox, reference first section)

   • Request Content Type: JSON

   • Response Content Type: JSON

   

Add an API endpoint for DocuSign template

1. Close out of the Create Data Server pop-up, then click on the name of the Server you just created in the list of data servers.

2. In the Endpoints panel on the bottom left, click Create

3. Add the following details:

   • Name: Name your endpoint

   • Endpoint: /v2/accounts/<AccountID>/envelopes

   • Method: POST

4. Next you will add the following endpoint parameters by clicking Create in the Endpoint Parameters panel in the top right and add the following details:

   • Parameter 1

     • Name: AccountID

     • Data Type: String

     • Test Value: API Account ID from DocuSign Sandbox (reference first section)

     • Type: Query

     • Direction: Input

   • Parameter 2

     • Name: Authorization

     • Data Type: String

     • Test Value: Bearer <Returned Access Token from the Token API>

     • Type: Header

     • Direction: Input

   • Parameter 3

     • Name: EmailBody

     • Data Type: String

     • Test Value: Email body of your choice, in this example, "A document needs signing"

     • Type: Query

     • Direction: Input

   • Parameter 4

     • Name: EmailSubject

     • Data Type: String

     • Test Value: Email subject of your choice, in this example, "Signing"

     • Type: Query

     • Direction: Input

   • Parameter 5

     • Name: status

     • Data Type: String

     • Test Value: sent

     • Type: Query

     • Direction: Input

   • Parameter 6

     • Name: TemplateID

     • Data Type: String

     • Test Value: The Template ID from the first section

     • Type: Query

     • Direction: Input

5. Click Test Connection to ensure parameters have been input correctly and to view test results, the EnvelopeID will be used in the next step.

6. Click the back button on the top left to return to Web Service to add additional endpoint

Add an API endpoint for document status

1. In the Endpoints panel on the bottom left, click Create

2. Add the following details:

   • Name: Name your endpoint

   • Endpoint: /v2/accounts/<AccountID>/envelopes/<EnvelopeID>

   • Method: GET

3. Next you will add the following endpoint parameters by clicking Create in the Endpoint Parameters panel in the top right and add the following details:

   • Parameter 1

     • Name: AccountID

     • Data Type: String

     • Test Value: API Account ID from DocuSign Sandbox (reference first section)

     • Type: Query

     • Direction: Input

   • Parameter 2

     • Name: Authorization

     • Data Type: String

     • Test Value: Bearer <Returned Access Token from the Token API>

     • Type: Header

     • Direction: Input

   • Parameter 3

     • Name: EnvelopeID

     • Data Type: String

     • Test Value: Envelope ID that was returned when testing the previous endpoint

     • Type: Query

     • Direction: Input

4. Click Test Connection to ensure parameters have been input correctly and to view test results

Make DocuSign tables public for later use

1. From the App Builder IDE, Click on Build Your Application

2. Click on the Data Storage Layer and under Web Services find the DocuSign Rest API you created in the previous step

3. Click on the Tables cog icon

4. For each table, double click on the table and click on Edge Case Settings

5. Under Public Access Click on Allow Read and Allow Write

6. Perform the same steps for the DocuSign Token REST API and any other endpoints you created for DocuSign Information.

Configure App Builder rules for DocuSign

Add columns for DocuSign information

1. From the App Builder IDE, Click on Build Your Application

2. Click on the Business Logic Layer and find the Datasource in which you wish to store DocuSign information

3. On the Business Layer Data Source panel on the right-hand side, click Link Sources and add the DocuSign REST API you created in the previous step *ensure you have marked tables as Allow Read/Write*

4. Click on the Business Objects icon and find the table where you would like to store DocuSign settings (this example will use ParamDocusign)

5. On the table, create the following columns:

   • DocusignBaseURL (NVarchar(50))

   • DocusignGrantType (NVarchar(50))

   • DocusignRefreshToken (NVarchar(-1))

   • DocusignClientIDSecretID (NVarchar(-1))

6. After columns are created, click Results and add values to the following columns:

   • DocusignBaseURL: The Base URL from the DocuSign sandbox

   • DocusignGrantType: The literal string value 'refresh_token'

   • DocusignRefreshToken: The refresh_token endpoint parameter in the Token REST API (the first REST API you created)

   • DocusignClientIDSecretID: The Authorization endpoint parameter in the token REST API

7. You can also add other columns to edit them in the UI, such as Email Body, Email Subject, and Role (these are DocuSign Template parameters).

Create XP insert rule to insert credentials to token post call

1. From the previous step, navigate back to the App Workbench

2. On the middle panel click Add a Business Rule to create a new Business object.

3. Fill out the following details:

   • Name: Table (Insert Refresh Access Token)

   • Purpose: XP CRUD

   • Uncheck "Skip Business Layer"

   • Action: Insert

   • Source Date Source: Database where the table with the DocuSign information is stored

   • Target Data Source: The first REST API you created to refresh Access Token

   • Target: Table from refresh Token API (in this example, Token)

   

4. In the Tables panel, click +Tables and add the Table from your source data source where the DocuSign information is being stored. In this case, ParamDocusign.

5. In the columns tab find the columns you designated to store the refresh token, the ClientID/SecretID, and the grant type, target them to their corresponding columns in the Token table as shown below.

   

Create XP update rule to refresh access token

1. From the previous step, navigate back to the App Workbench

2. On the middle panel click Add a Business Rule to create a new Business object.

3. Fill out the following details:

   • Name: Table (Update Refresh Access Token)

   • Purpose: XP CRUD

   • Uncheck "Skip Business Layer"

   • Action: Update

   • Source Date Source: The first REST API you created to refresh Access Token

   • Target Data Source: Where table with DocuSign information is located

   • Target: Table where DocuSign information is stored, ParamDocusign in this example

   

4. In the Tables panel, click Create and add the Table with the access token (this is the name of the endpoint you created in the first REST API).

5. Click All to add all columns from the table

6. Find the column called access_token and target it to the DocusignClientIDSecretID column you created in the table.

7. Add API Account ID to ParamDocusign as a column and input its value

8. Add API Account ID as a parameter on the Refresh Token Endpoint and input its value

9. In the Update Rule, Set the Refresh Token's API Account ID to Target the ParamDocusign's AccountID on type binding, and set it as PK. This has the added benefit that if you decide to add more DocuSign accounts to the application this will help accommodate that configuration.

   

Create schedule to run refresh access token event

1. Because the Access Token expires and needs to be updated regularly, add this rule to an event and create a schedule.

2. Create the event by navigating to the business Logic layer and Under Events popup for ParamDocusign, click on +Table Event.

   • Name: RefreshToken

   • Refresh Scope: Row

   Note

   Make sure under Edge case the Execution Type it is set to Launch Via Schedule with Max Concurrency: 1.

   

3. Under Actions, click on Register Existing and add the previously created CRUD rule: Table (Update Refresh Access Token).

4. Next, navigate to App Builder Monitor (in the bottom left corner)  Schedules. Name your schedule and choose the Application where the event you created for the rule is created. Leave Frequency as is at "Periodic Execution of Schedule". Under Scheduling Information, set frequency for the schedule to run, 4 hours is recommended.

   

   

Now that you are refreshing your access token on a schedule, you can maintain a connection to your DocuSign API. Create other XP CRUD rules as needed to send or retrieve information from the connected DocuSign account, such as the Document Status and Template endpoints created in the second REST API.

Some capabilities may incur costs, such as returning a file using a webhook. Another option is using the HTTP retriever plugin.

Promoting application to DocuSign production

When the endpoints and CRUD rules you have created are working consistently, you are ready to promote this application to DocuSign Production. To do this, you will need to have the API reviewed in DocuSign. To pass the review, you must have 20 successful API calls in a single day.

1. Navigate to the DocuSign Sandbox link the first step and click on Admin, then click on Apps & Keys on left hand side menu

2. Under Apps and Integration Keys find the app you created in the first step and click Actions, then select Start Go-Live Review and enter a date with 20 or more successful API calls

3. A DocuSign administrator will manually review and authenticate the request, this can take up to 3 business days.

4. After Go-Live is authenticated, the previous steps will need to be repeated with the Production DocuSign credentials. The Integration Key will remain unchanged, but the other credentials will be different and need to be updated in Postman and App Builder.

5. Changes to steps from above:

   • In Postman, create a new GET call with the URL: https://account.docusign.com/oauth/userinfo

   • In the response of the GET call, copy the "base_uri" to use in the POSTs, GETs, and HTTP Retrieve URLs for the production environment.

   • When creating the Refresh Token API for production, the URL is https://account.docusign.com