Page Comparison

...

E-signing a document with DocuSign generally requires three major steps:

1. Creating an envelope containing documents, recipient information, and sign field locations (performed by Quik!)

2. Calling DocuSign for the status of the envelope (performed by Customer)

3. Downloading, processing, archiving, and/or submitting the signed document (performed by Customer)

The first step requires significant processing and set-up including:

...

Please review the technical requirements below for integrating Quik! with DocuSign regardless of the implementation model used:

1. Create an OAuth token with DocuSign - In order for users to sign, the Quik! Master Account must be set up with an OAuth token for the user/customer's DocuSign account (partners will need to set up OAuth Tokens for each of their customer accounts). OAuth tokens can be set up on the Quik! Forms Enterprise Manager or via web service (REST or SOAP). Partners who offer Quik! to multiple customers will need to address how each of their customers will set up OAuth tokens on their Quik! accounts. The ideal solution is for the partner to build a user interface that asks the customer to enter their DocuSign credentials which can be passed to our web service to establish the token. Quik! does not store the customer credentials, just the token (which never expires). This enables customers to change their DocuSign password without affecting their integration with Quik!. Note that customers must identify their DocuSign environment (NA1, NA2, Demo, etc.) to establish the token. If customers don't know which environment to select, Quik! recommends contacting their representative at DocuSign, and they will inform. Alternatively, you can check your accounts environment by navigating to Settings > Plan and Billing within your Docusign account.
   

2. Set relevant DocuSign properties in the request when generating forms - Once a token is established, customers must include the following properties in their Execute request when generating HTML forms:

   1. ESignTypeDocuSign (establishes DocuSign as the e-signature service used)

   2. AuthUserID (indicates which OAuth token will be used, also known as ‘CustomerUserID’ when using /docusign/oathtokens)

   3. SignEnvironmentID (indicates which DocuSign environment will be used, see Docusign environment table below)

   4. SignCallBackURL or SignURL (indicates which implementation model will be used)

   5. QuikFormID (indicates which forms will be generated, always required in any Execute request)

   6. Any other DocuSign settings (optional - see a complete list of DocuSign properties here)

Docusign Environments:

Sample REST Execute request

...