Docusign Authentication (Create OAuth Tokens)

Create a Docusign OAuth Token

To streamline the process of signing documents, the customer’s Quik! Master Account must be set up with an OAuth token for the user/customer's Docusign account. The steps below detail how to create a Docusign OAuth token which can be used for making API requests.

Login to the Quik! App:

Navigate to Connection Settings:

  • Go to Settings in the Quik! App.

  • Select E-Signature, then Add a Connection.

Connect to Docusign:

  • Click the Docusign box.

  • Choose between Docusign or Docusign Demo.

  • Follow the prompts to log in to your Docusign account.

Grant Access:

  • Click Allow Access to let Quik! manage documents for you.

Configure Your Connection:

  • Connection Name: Pick a unique name for your Docusign connection.

    • This name is what you will use to plug into the Docusign AuthUserID property when generating forms with a Docusign connection.

  • Connection Visibility: Set to Public (for all users) or Private (for yourself).

  • Select Account: Choose your preferred Docusign account.

Finalize the Connection:

  • Click Add to complete the setup.

Manage Your Connections:

  • View or manage connections in E-Signature → Docusign Properties.

Legacy Methods

NOTE: The below methods are considered legacy. At this time, they are deprecated and no longer in use. This guide is here for documentation purposes only.

REST API or Quik! Forms Enterprise Manager

NOTE: Starting September 30 2024, this method will no longer be accepted by Docusign. Existing tokens using this method will still work, but you will not be able to create new tokens using this method.

  • OAuth tokens can still be set up through the Quik! Forms Enterprise Manager or via web service (REST or SOAP).

  • Partners offering Quik! to multiple customers must address how each of their customers will establish OAuth tokens on their Quik! accounts.

  • Partners are encouraged to build a user interface that allows customers to enter their Docusign credentials, which are then passed to our web service to establish the token. Quik! only stores the token, which does not expire, allowing customers to change their Docusign password without impacting their integration with Quik!.

  • It is essential for customers to identify their Docusign environment (e.g., NA1, NA2, Demo) to set up the token. If there is uncertainty about which environment to choose, customers should contact their representative at Docusign or check the account environment by navigating to Settings > Plan and Billing within their Docusign account.

For help regarding Quik! Forms and the Quik! API
Email: support@quikforms.com | Phone: (877) 456-QUIK