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:

• Bookmark: https://quikformsapp.com and log in.

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.

Who Can Create Connections?

Docusign connections must be created directly through the Quik! App.
Custom login interfaces for Docusign are not supported at this time.

Granting Client Access

You can grant your clients access to the Quik! App, allowing them to set up their own Docusign connection.
This approach removes the need for clients to share their Docusign login credentials with your team, improving security and simplifying the process.

Note:
Quik! App credentials are separate from your API "Master Credentials" and are used solely for setting up Docusign connections.

Connection Setup Options

You can configure your integration using either:

• A single Docusign Admin account shared across all end-users

• Separate Docusign accounts per user, if required by client-specific business policies

Both options are fully supported—choose the method that best aligns with your platform structure and client requirements.

🚫 Legacy Methods (No Longer Accepted)

The below methods are no longer valid for establishing new tokens:

• REST or SOAP Web Services

• Quik! Forms Enterprise Manager