PixlDocs is a document API. You write a template in HTML and Liquid, declare the fields it accepts, and POST JSON to get back a print-ready PDF — the same document, every time, for every customer.

It is built for the paperwork a business has to produce on demand and cannot get wrong: invoices, payslips, statements, receipts, delivery notes, certificates, policy schedules, lab reports, tickets and labels.

What you can do

Start from a real document — browse Documents, open one, and it lands in your workspace with its field contract already declared.
Write your own in HTML and Liquid, or describe it in a sentence and let the generator draft it for you.
Render from your backend — POST /v1/render returns the file itself, synchronously.
Render markup you already have — POST /v1/render/html and POST /v1/render/url need no template at all.
Render without writing code — n8n, Zapier and Make all reach the same API. See Integrations.
Let an AI agent do it — the MCP server exposes the same endpoints as tools. See AI agents & MCP.

How a document is made

ascii

Template (HTML + Liquid, @field contract) ─┐
                                           ├──►  PixlDocs  ──►  PDF / PNG / WebP
Data (JSON)                                ─┘

The template carries the design and declares which keys it accepts. The data carries the content. The engine handles pagination, fonts, page geometry and vector-clean export — and refuses the call rather than quietly dropping a key it cannot bind.

Where to next

Quickstart — key, template, rendered PDF, in five minutes.
Core concepts — templates, field contracts, renders, credits, workspaces.
API reference — every endpoint, every error code.