DocuSign : API Integration

Owned by Priyanka Patil (Unlicensed)
Last updated: Jan 16, 2024 by Christine Gross
4 min read

Note: Zilla recommends using the API Integration. To switch over to the API integration, first archive the ZUS (Browser Extension) application instance and then create a new DocuSign instance enabling the API Integration.

Additionally, it’s important to call out that Docusign API Integrations require a ‘Go-Live’ Review Process to be completed. This consists of first setting up the API Integration in a Docusign Developer Account, where 20 successful API Calls must be made. Once this is satisfied, the API Integration will then be eligible to be promoted to Docusign Production.

How-To Go-Live in 3 Steps

 

 Get the API Account ID and Account Base URI

  1. Visit your DocuSign account.

  2. Navigate to the Settings tab at the top of the page.

     

  3. Scroll down and click Apps and Keys.

     

  4. Copy the API Account ID and Account Base URI ( copy Account Base URI without https:// like demo.docusign.net ) and save for a later step.

     

Get the Integration Key and Secret Key

  1. Click ADD APP AND INTEGRATION KEY.

     

  2. Enter the App Name and click CREATE APP.

     

  3. Copy the Integration Key and save it for a later step.

     

  4. Select Authorization Code Grant and click + ADD SECRET KEY. Copy the Secret Keys and save for a later step.

     

  5. Go to the Additional settings and add redirect URI. Click + ADD URI and add the `https://app.zillasecurity.com/api/auth/callback/docusign` URL.

     

  6. Click SAVE.

     

Set up DocuSign Application Integration on Zilla.

 

  1. Start the Go-Live Review Process in Docusign.

  1. Locate your DocuSign application instance in the Zilla Applications library, click Sync now in the top right and enable API Integration. Copy the Account Base URI, API Account ID, Integration Key and Secret Key you obtained in the previous steps and enter them into the corresponding boxes, then click Sync Now.

  2. Sync Docusign Developer Environment (Yes/No): For initial syncs this must be set to Yes as the integration is first set up in the Docusign Developer Environment. Once the Go-Live Review Process is completed and the API Integration is able to be promoted to Docusign Production, update this field to No so that it knows to sync from the correct environment.

  3. Enable account modifications? (Yes/No): Yes will automatically revoke group memberships that have been flagged for revocation after an access review during a sync. Note: Currently revocation of permissions and revocation of group memberships of Administrators and Everyone is not supported as Docusign does not support this. Defaults set to No.

     

  4. Click Next.

     

  5. Grant access by clicking ALLOW ACCESS. Your sync will start once you have granted Zilla access.

     

  6. Click Done on Zilla.

     

  7. Docusign Requires that 20 successful API calls must be made, so sync a handful of times and wait several minutes until this quota is reflected on the Docusign side. Once it is reflected in Docusign, you should now see the option to Submit for Review:

7.) Once about 20 minutes or so has passed, you will now see the Go-Live Status of Review passed, with the option to Promote to production.

 

 

8.) Select Select Go-Live account:

9.) You will be prompted to choose the Production account ID to use to promote to Docusign Production:

 

10.) It may take some more time for this final step of promotion to production, but once it completes you will be notified via email that everything is ready. Once it has been promoted to production, make sure to switch the Developer Environment setting to No in the Zilla app instance config. Also update integration key, secret key, url, API AccountID with the production integration’s credentials and then re-sync.