DocuSign Integration Webinar

DocuSign Integration Webinar

Please see the attachments for detailed information, recording available from within the Vimeo weblink
Click HERE for the DocuSign Integration Webinar Video 
One Attachment available + a link for the Recorded Training:

      1.  The Questions and Answers from the recorded webinar on 3/28/2023, titled "Docusign Integration Webinar Q&A.pdf"
      2.  The recorded training from 3/28/2023 explaining the DocuSign Integration

AGENDA:

1. DocuSign Integration Overview
2. DocuSign - ASPIRE Functionality Demo
3. DocuSign Document Configuration
4. DocuSign - ASPIRE Configuration
5. Technical FAQ's
6. Q&A

    • Related Articles

    • 401 error when using DocuSign integration

      401 errors indicate an unauthorized request. Most commonly, this is due to using an invalid service key. Each service key is unique to a subscriber and service address. Please check with the assigned LTi account manager to confirm authorization for ...
    • DocuSign Integration User Guide

      Please see Attachments to download the guide. This article is the holding place for the most recent version of the ASPIRE v5 - DocuSign User Guide. Throughout the Knowledge Base there are also individual articles on relevant topics related to this ...
    • DocuSign Integration - Contract Status Updates

      Background Finance companies generally have multiple credit applications in process at the same time which often means having to prepare documents for signing, getting the documents to the signers, and tracking when the documents come back signed on ...
    • 400 Error when using DocuSign Integration

      Normally, when an ASPIRE user attempts to submit an envelope to DocuSign, a “success” message will be returned along with a DocuSign Envelope ID. Occasionally, an error message will be returned. Typically, this is a 400 error. 400 errors indicate a ...
    • 404 error when using DocuSign integration

      404 errors indicate that the resource was not found. Most commonly, this is due to either an incorrect service address or due to the service being down. Recheck the Service Address, then check with LTi support to see if the requested service is ...