Docupilot for developers

Build Scalable Document Workflows Into Your Product With Document Automation API

Docupilot is a programmable document automation platform for generating, processing, signing, delivering, and tracking documents from structured business data.
Start buildingView API overview
Developer implementation support
Webhooks
REST + OpenAPI
API Access on all Plans
Start with a real request

Trigger a Docupilot Workflow from your application.

Create and publish the workflow in Docupilot, then POST your business data to its execute endpoint. The workflow handles the document-specific steps you configured.
curl "YOUR_WORKFLOW_URL" \
 -H "Authorization: Bearer YOUR_AUTH_TOKEN" \
 -H "Content-Type: application/json" \
 -d '{
   "order_number": "ORD-1001",
   "order_total": 350,
   "customer": {
     "name": "Jane Smith",
     "email": "[email protected]"
   },
   "items": [
     { "name": "Desk", "quantity": 1, "price": 200 },
     { "name": "Chair", "quantity": 2, "price": 75 }
   ]
 }'

What this request means

1. Your application

Sends the workflow input

2. Docupilot Workflow

Runs the configured document steps

3. Your system

Uses the resulting output and status

Choose how your application connects to Docupilot.

Trigger a Docupilot Workflow when multiple document actions need to run together, or call individual APIs when you only need a specific action.
RUN A DOCUMENT PROCESS

Trigger a Docupilot Workflow

Configure the document steps visually in Docupilot, then send data from your application to start the published Workflow.

Use this when: You need conditions, one or more documents, PDFprocessing, signing delivery, or status handling.

You send:Business data for the workflow run.

Docupilot runs:The document-specific steps configured in the Workflow.

RUN AN INDIVIDUAL ACTION

More Consistent Processes

Use an API when your application needs Docupilot to perform one specific document action without running a multi-step Workflow.

Use this when:You only need a specific document operation.

Examples:Generate a document, convert a file, append files or transform a PDF.

View API overview:OpenAPI-based interactive documentation.

Other supported ways to connect:

Developer implementation support
eSignature APIs
File APIs
Merge Links
Hosted Forms
Bulk generation
Built for your application

Set up a workflow in Docupilot and trigger it from your application.

Keep document logic in one easy-to-manage place—and update the workflow anytime without rebuilding your application.

Your application triggers the workflow while Docupilot handles the rest.

Send your business data to a Workflow. Docupilot runs the steps you configured and sends the result to your application.

  • Set up your process in our advanced, flexible Workflow Builder
  • Trigger the Workflow with your data
  • Change the workflow whenever your process evolves
  • Debug every run with clear input and output logs
Workflow
Your application Sends business data
Docupilot Workflow Runs your document steps
Document + status Returned to your app
Need to change the process? Update the Workflow without changing the application flow.

Keep document-specific workflow logic out of your application code.

Trigger a published Docupilot Workflow by API. Docupilot can then apply conditions, generate and process documents, sign or deliver them, and return status to your system.
Input
Trigger
Receive structured workflow input
Decide
Choose a branch, template, or required document
Generate
Map values and
render one or more documents
Process
Convert, append, reorder, or transform output
Sign / deliver
eSignature, email, webhook, storage, or SFTP
Track
Return completion, delivery, or signing status
Output

Go beyond basic field replacement.

Use structured data, conditions, loops, calculations, and dynamic content to generate documents from complex payloads.

Nested, repeating & array data

Map nested objects and arrays, loop over repeating records, and sort, filter, group, join, or aggregate array data.

Conditional document logic

Include, exclude, or change content based on incoming values and conditions.

Calculations & variables

Use date, number, string, mathematical, comparison, logical operations, and dynamic variables.

Dynamic content

Insert images, rich text, maps, QR codes, barcodes, and links from structured input.

Reusable content blocks

Create and reuse shared content blocks across supported document templates.

eSignature fields & roles

Configure signing fields and recipient roles that can be resolved from document data.

Separate application logic from document logic.

Keep business logic in your application while Docupilot manages templates and document-specific workflow configuration.
Configure how application data maps into Docupilot
Payload mapping
Conditions & branches
Recipients & signing order
Delivery destinations
Callbacks & status
Your product & engineering

Own the application contract

Collect or retrieve business data.
Authenticate to the appropriate Docupilot API surface.
Define the payload contract and trigger generation or workflow execution.
Control how your product displays or uses the result.
Act on completion, failure, delivery, or signing events relevant to your application.
Docupilot & operations

Maintain document-specific behavior

Maintain template wording, formatting, branding, and reusable content.
Maintain supported conditions and template-selection rules.
Maintain recipients, delivery content, and supported destinations.
Test, preview, and publish document changes.
Use Docupilot for rendering, processing, signing, delivery, status, callbacks, and retry handling.

Build repeatable document workflows around your data.

Use the same integration to generate in-product documents, reports, conditional document packets, and transaction-driven output.

Start from your application

Send application data to Docupilot, generate the required document, and return the output to your product.

Application
data
Generate
document
Return to
product

Assemble conditional document packets

Choose the required path from data, generate the relevant documents, and combine supported files into a packet.

Payload
Rules +
 generate
PDF
packet

Create operational reports

Use structured records and repeating data to generate operational or customer-facing documents automatically.

Records
Generate
report
Deliver

Start from your application

Send application data to Docupilot, generate the required document, and return the output to your product.

Transaction
data
Select +
generate
Deliver
/ sign

Security controls you can verify.

Docupilot publishes its compliance posture and security controls in its Trust Center so technical teams can review the details directly.
View Trust CenterCompliance details

Build with technical support when you need it.

Work directly with the Docupilot team on integration design, Workflow architecture, and complex document automation requirements.

API setup

Choose the right API surface, authentication approach, and workspace setup for your integration.

Workflow design

Map document generation, processing, signing, and delivery requirements into a workable Docupilot Workflow.

Solution architecture

Design the end-to-end automation across your application, Docupilot, and connected systems.

Complex cases

Work through advanced template logic, payload structures, rendering requirements, and delivery edge cases.

Common questions from developers and technical evaluators.

How is the V2 API authenticated?

Create an API Key + Secret in API Settings. Send the Base64-encoded key:secret value as a Bearer token. Workspace-scoped APIs also require the X-Workspace header. Read the API overview.

Is API access limited to Enterprise?

No. API access is available during the free trial and from the Starter plan onward. See current pricing.

Can a Docupilot Workflow be started through an API request?

Yes. A Docupilot Workflow can be started by an API request, hosted form submission, or test run. Read about workflows.

Does Docupilot support webhooks?

Yes. Webhook delivery can POST generated output to another system, and template-generation endpoints can also be used as webhook targets in external tools. Webhook documentation.

What can a Docupilot Workflow do after it receives data?

A Docupilot Workflow can apply conditions, generate documents, convert or append PDFs, and deliver output through supported Email, Webhook, and eSign modules. See workflow modules.

Can operations teams manage documents after the integration is live?

Authorized teams can maintain supported template content, formatting, conditions, recipients, delivery configuration, and published document changes inside Docupilot. Changes to the payload contract, application logic, or integration surface may still require engineering.

Where can I access the API documentation?

Docupilot V2 APIs use an OpenAPI-based interactive reference available from your Docupilot environment. Access the API documentation.