Introduction

What Quik! is

Quik! is a forms automation platform built for the financial services industry. The Quik! Forms Engine generates fillable forms (HTML or PDF), prefills them with your data, routes them for e-signature, and handles the documents from start to finish. Over 30,000 forms from major financial institutions are available in the Quik! library today.

If your business involves moving people through paperwork (account openings, transfers, beneficiary changes, applications, claims) and you want the friction out, Quik! handles the form layer so your team and your clients can focus on the work, not the paperwork.

What the API gives you

The Quik! Forms Engine API is the programmatic way to use Quik!. With it, your application can:

Search and retrieve forms from the Quik! library or a private library built for you.
Generate forms as interactive HTML for users to fill out, or as finished PDFs.
Prefill data onto forms from your CRM, account system, or any other data source.
Bundle multiple forms into a single package, including multi-account households.
Send forms for e-signature through DocuSign, SIGNiX, or Quik!'s native e-signature.
Save and resume in-progress forms so users can come back later.
Apply field rules that control behavior at runtime (required, hidden, conditional, formatted, and more).
Manage attachments alongside form packages.

Who Quik! is for

Quik! is built for businesses where financial professionals interact with paperwork at scale:

Broker/Dealers
Clearing Firms and Custodians
Banks and Credit Unions
Insurance Agencies (BGAs, IMOs)
Money Managers and TAMPs
Platform integrators (CRMs, financial planning software, advisor desktops, fintech apps)

The end users of forms generated through Quik! are usually financial advisors, insurance agents, and back-office staff. The end clients (the people the forms are about) interact through their advisor's workflow.

How these docs are organized

Section	What it covers
Get Started	This section. A linear path from "I have an account" to "I generated my first form."
Concepts	The mental models behind the API: how the Field Definition works, what a role prefix is, how Form Group Instances behave, how Sessions and UNIDs tie a form together.
Guides	Task-oriented recipes. "How do I launch a form?" "How do I map my data?" "How do I save a form for later?"
Integrations	Setting up the connections that workflows depend on: DocuSign, SIGNiX, CRMs. One-time setup per integration.
API Reference	Generated from the OpenAPI spec. Every endpoint, every field, every error code. The lookup material when you know what you're looking for.

Where to start

If your account is brand new, the next thing to do is generate your first OAuth token. Continue to Authentication.

If you want to skip ahead, read Concepts > Data Model > Fields and Field Names to understand how Quik! talks about form data. Most of the rest of the docs build on that.

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

Authentication — Learn how to connect securely before making API requests.
Library Subscription — Understand how form access works before launching or testing forms.
Launch a Form — See the basic workflow for generating and opening a Quik! form.

Account Setup & Environments