Note: 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.
Before you begin the DocuSign configuration, your DocuSign Administrator must obtain the Username.
The ClientSpace staff member assigned to assist you with DocuSign API configuration provides the Secondary ID and Key. You will need the login information at the end of the API configuration process to authorize the connection from ClientSpace to DocuSign.
The table below lists the information you need before you begin 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. |
| Password |
The DocuSign user account password is no longer used. For now, enter "password" (or any made up characters) in this field so that you can save your entries without receiving the "Password is a required field" error message.
Note: DocuSign now requires OAuth 2.0 configuration. OAuth 2.0 configuration requires a Key instead of a Password. The Password field will be removed in a future release. |
| Endpoint |
This is the server URL to which we connect. In production environments, this is typically entered as account.docusign.com. |
|
Secondary ID |
Integration key provided by the ClientSpace staff member assigned to assist you with DocuSign API configuration. |
|
Key |
OAuth2 RSA Key required by DocuSign for all DocuSign API integrations after 12/31/2023. The ClientSpace staff member assisting you with the implementation provides the Key. |