Self-Service Integration refers to customers or partners who typically represent multiple users and want the ability to work directly with the e-sign vendor's APIs. In this scenario, Quik! will provide the customer with the form as a PDF, all the relevant XML data needed by the vendor and any other data. The customer will then submit this information through the e-sign vendor's API to fully control the signature process. This method enables customers to use their own workflows and integrations with e-sign vendors and to eliminate the need to further rely on Quik! to retrieve signature data and documents.
...
Enter your values in each appSetting key per the key attributes described below.
NOTE: You must set up a DocuSign API key on your account to use DocuSign!
Keys
Property | Description |
strAPIAccountId | Enter your DocuSign account ID (found in your DocuSign account in the API screen) |
strAPIUserName | Enter your DocuSign username (found in your DocuSign account in the API screen) which has the naming convention of [API-Key-Value]email.com: [########################-############]email@email.com |
strUserPassword | Enter your DocuSign password (found in your DocuSign account in the API screen) |
strAPIUrl | The default demo URL should be used during development and changed according to instructions from DocuSign upon approval and go-live. |
SupportEmail | Enter your company's support email address for any issues that arise from using the system. |
SupportPhone | Enter your company's support phone number for any issues that arise from using the system. |
...
When you're certified with DocuSign and ready to go live, be sure to change the endpoint URLs to the appropriate production URLs as indicated by DocuSign's documentation.
NOTE: The sample production URLs below may not be the ones you end up using – be sure to read the documentation from DocuSign.
| Code Block | ||
|---|---|---|
| ||
<client> <endpoint address="https://demo.docusign.net/api/3.0/credential.asmx" binding="basicHttpBinding" bindingConfiguration="CredentialSoap" contract="CredentialService.CredentialSoap" name="CredentialSoap"/> <!--Change this to the production API (https://www.docusign.net/api/3.0/credential.asmx) once certified by Docusign IF you modify this project. Otherwise, use the production URL now.--> <endpoint address="https://demo.docusign.net/api/3.0/api.asmx" binding="basicHttpBinding" bindingConfiguration="APIServiceSoap" contract="APIService.APIServiceSoap" name="APIServiceSoap"/> <!--Change this to the production API (https://www.docusign.net/api/3.0/api.asmx) once certified by Docusign IF you modify this project. Otherwise, use the production URL now.--> </client> |
...
By default, when you run the QuikESignTransport web service an envelope will be created in DocuSign automatically. It is then up to you to poll for status using the EnvelopeID returned by the web service and to download the final document.
It is important that you modify the QuikESignTransport to do something with the EnvelopeID that is returned. See line 161 in the QuikSignTransport.aspx.cs file for the EnvelopeID.
Download this project on the Downloads page.
Build Your Own DocuSign API Calls
...
- Byte[] pdfBytes – (QuikSignTransport.aspx.cs line 154) contains the byte stream of the PDF returned by Quik!, including the forms and any external documents, arranged in the order specified when the QuikFormsEngine software was run.
- string XML – (QuikSignTransport.aspx.cs line 156) contains the raw XML returned by the Quik! server which contains the envelope data formatted to work with DocuSign.
NOTE: Any modifications to the PDF and XML are at your own risk to ensure it conforms to DocuSign's API.
Quik!'s Docusign API Web Service
...