DocuSign

What this does

Connect your DocuSign account to your Quik! Master Account so any e-signature workflow you run through Quik! (sending forms for signature, Direct to DocuSign, embedded signing) can talk to DocuSign on your behalf. You do this once per account. After that, every API call that references the connection picks up the right credentials automatically.

When to use this

Set up a DocuSign connection before you do any of the following:

• Send a Quik! form for e-signature using DocuSign.
• Use the Send Direct to DocuSign workflow.
• Allow your end users to e-sign forms inside your application.

If your account has never been connected to DocuSign, every e-signature API call will fail. The connection is a prerequisite.

Before you start

You need:

• A DocuSign account (Production or Demo). Quik! does not sell DocuSign accounts. You must already have one.
• Quik! App credentials for the account you're connecting on behalf of. These are separate from your API Master Credentials. Quik! App credentials are used solely for setting up integrations like this.
• A decision about whether to use one shared DocuSign Admin account for all your users or separate DocuSign accounts per user. Both are supported. The right choice depends on your business policy.

Steps

1. Log in to the Quik! App at https://quikformsapp.com.
2. Navigate to Settings → E-Signature → Add a Connection.
3. Click the DocuSign box and choose either DocuSign (Production) or DocuSign Demo.
4. Follow the prompts to log in to your DocuSign account.
5. Click Allow Access to authorize Quik! to manage documents on your behalf.
6. Configure the connection:
   • Connection Name. A unique label you choose. This name is the value you'll use as AuthUserID in any API call that needs to reach this DocuSign connection. Pick something memorable and consistent (e.g., MainAccount_Production).
   • Connection Visibility. Public makes the connection available to every user in your Quik! account. Private keeps it scoped to the user who created it.
   • Select Account. If your DocuSign login has access to more than one DocuSign account, pick the one you want this connection to use.
7. Click Add to save the connection.

View and manage existing connections in Settings → E-Signature → DocuSign Properties.

Connection setup options

One shared Admin account for all users

A single DocuSign account is connected to your Quik! Master Account. Every form your platform sends for e-signature uses the same DocuSign credentials, and signed envelopes appear in one DocuSign inbox.

Best for: platforms where DocuSign is centralized and your team manages all envelopes from one place.

One DocuSign account per user

Each of your end users connects their own DocuSign account to your Quik! platform. Their signed envelopes land in their own DocuSign inbox.

Best for: platforms where each advisor, agent, or end client manages their own DocuSign account and is responsible for their own signed documents. You can grant your clients access to the Quik! App so they can complete the connection setup themselves without sharing DocuSign credentials with your team.

Using your connection in API calls

When you make an API call that involves DocuSign (form generation with the Sign button, Send Direct to DocuSign, etc.), reference your connection by its Connection Name in the AuthUserID property of the ESignType object.

For example, if you named your connection MainAccount_Production, your generation request includes:

{
  "ESignType": {
    "Type": "DocuSign",
    "AuthUserID": "MainAccount_Production",
    "SignEnvironmentID": 1
  }
}

SignEnvironmentID identifies which DocuSign environment to use (Production NA1, Demo, EU1, etc.). Match this to the environment you chose when creating the connection.

Pitfalls

• Quik! is not a reseller of DocuSign. You need your own DocuSign account before this flow will work. Quik! cannot create a DocuSign account for you.
• Quik! App credentials are not your API Master Credentials. They are separate accounts. App credentials are used only for setting up integrations like this. API Master Credentials are used to make REST API calls. Don't try to use one in place of the other.
• The legacy methods for creating connections are no longer accepted. REST and SOAP token creation endpoints, and the token-creation UI in the Quik! Forms Enterprise Manager, were deprecated in September 2024. Connections must be created in the Quik! App. Existing tokens created the old way still work, but new ones must use the App.
• The Connection Name is what you reference in API calls, not the DocuSign account name. Pick a Connection Name that's easy for your developers to remember and consistent across environments.
• An unfamiliar App ID labeled "App name not known" is expected in DocuSign. Following DocuSign's OAuth changes in July 2024, some authorized apps show up without a visible app name. You can confirm valid connected apps in DocuSign under My Profile → Connected Apps.
• Picking the wrong environment (Production vs Demo) causes silent confusion. If your connection was set up against Demo and you try to use it with Production data (or vice versa), the API call will not error, but envelopes won't behave as expected. Use a Connection Name that includes the environment, and double-check SignEnvironmentID matches.

Related articles

Continue with these articles to understand the related concepts and workflows:

• Authentication — Review the authentication concepts that support secure API and e-signature setup.

• Send Direct to DocuSign — Learn how connected DocuSign credentials are used to send forms for signature.

• Roles and Role Prefixes — Understand how Quik! roles connect to DocuSign signers.

• Form Groups and Instances — See how multiple form instances affect signer setup.