Before You Begin

Before you begin the DocuSign configuration, your DocuSign Administrator must obtain the API login information. (Your ClientSpace Professional Services representative may also be able to help you obtain this information.)

You will need the login information at the end of the API configuration process to authorize the connection from ClientSpace to DocuSign. In addition to login information, you will need additional information from DocuSign such as an RSA Key and an Integration Key.

The table below lists the information you need from DocuSign to set up the DocuSign API in ClientSpace.

You must have

Description

Username

DocuSign user account code. The account code is provided by DocuSign as the API UserName and is in the form of a Globally Unique Identifier or GUID, a 32-digit character string formatted as xxxxxxxx-xxxx-Mxxx-Nxxx-xxxxxxxxxxxx.

Endpoint

This is the DocuSign server URL to connect to their system and is determined and provided to you by DocuSign. In production environments, this is typically entered as account.docusign.com.

Secondary ID

Integration key.

 

Your DocuSign Administrator (or ClientSpace Professional Services representative) can obtain the Secondary ID from Docusign.com. See Configuring the API Record for steps to acquire this information.

Key

OAuth2 RSA Key required by DocuSign for all DocuSign API integrations.

 

Your DocuSign Administrator (or ClientSpace Professional Services representative) can obtain the Key from Docusign.com. See Configuring the API Record for steps to acquire this information.

The ClientSpace API for DocuSign requires the purchase of DocuSign licensing. Before configuring DocuSign in your ClientSpace installation, please log an Extranet case to discuss DocuSign licensing.