Direct To Docusign Model

Overview

The Direct to DocuSign model allows you to generate and send DocuSign envelopes directly through Quik!'s eSignature API. Rather than building your own envelope creation service, you provide form IDs, prefill data, and recipient information — Quik! handles document rendering, tab mapping, and all DocuSign API communication.

This model is a good fit if you:

• Don't want to build or host your own envelope creation service

• Want Quik! to fully manage tab placement and role mapping

• Need draft review capability before sending

• Need to bundle multiple forms into a single envelope

Compared to the Self Service model, Direct to DocuSign removes the infrastructure burden while still supporting role-based signing, draft workflows, and multi-package envelopes.

Authentication

All requests require a Bearer token obtained via the Resource Owner Password Credentials OAuth flow.

Include the token in the Authorization header of every request:

http

Contact Quik! support for your token endpoint URL and credentials.

The Two-Call Flow

Sending an envelope requires two sequential API calls:

1. Generate SignData and PrintData — Call the QFE engine to render your forms and produce the tab mapping and recipient data needed for signing.

2. Create the Envelope — Pass the output from Call 1 into the envelope creation endpoint, which constructs and sends (or drafts) the DocuSign envelope.

Call 1 — Generate SignData and PrintData

Endpoint

http

Request

To use the Direct to DocuSign model, include GenerateSignData: true and GeneratePrintData: true in your request body alongside your form and recipient data.

json

Response

The response contains three key fields inside ResultData that are used to construct the Call 2 request body:

Note: PrintData, SignData, and SignSettings are returned as serialized JSON strings. You must JSON.parse() each one before passing them into the Call 2 request body.

json

Transforming Call 1 Output to Call 2 Input

The output of Call 1 maps directly to the packagesData and signSettings fields in the Call 2 request body. Use the following transformer to handle the conversion, including parsing the serialized JSON strings and normalizing PascalCase keys to camelCase:

javascript

Usage:

javascript

Pass any fields not sourced from Call 1 (such as enableInternationalPhoneNumber) via the options argument.

Call 2 — Create the Envelope

Endpoint

http

Headers

http

Request

The following is a complete example request body produced by transforming the Call 1 response above:

json

Key Request Fields

signSettings Fields

signEnvironmentID = is traditionally a value of 1 or 2 if your organization is testing outside of one of the following environments please contact Quik! support.

1 = //www.docusign.net

2 = //demo.docusign.net

Response

On success, the API returns the DocuSign Envelope ID:

json

Envelope Status

The status field in signSettings controls what happens after the envelope is created:

Draft Review Workflow

If you set status to "created", the envelope is saved to DocuSign Drafts. No recipients are notified. You or your team can then log into DocuSign, review the envelope, and send it manually.

You can also construct a deep link to take users directly to the draft in DocuSign:

Multi-Package Envelopes

To include multiple forms in a single DocuSign envelope, add additional objects to the packagesData array. Each package has its own printData and signData, but all packages are combined into one envelope and sent together.

json

Authorization

The customerID in the request body must either match the authenticated customer account or belong to an authorized child account. Requests with unauthorized customerID values will be rejected.

Errors

Note: This error table reflects common scenarios.

Comparison to Other Models