PixlDocs is an image & PDF automation API. Make a template once, send it JSON, and get back a finished PDF or image — the same document, every time, for every record. It is free for 1 year: sign up and start integrating.

Two ways to build a template

HTML API — write the template in HTML and Liquid. Best for invoices, payslips, statements, packing slips and other paginated PDFs.
Canvas API — design the template visually in the canvas editor. Best for certificates, tickets, badges and branded images.

Both are rendered by the same API with the same JSON data, so you can use one or both.

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, first render.
Core concepts — templates, field contracts, renders, credits, workspaces.
API reference — every endpoint, every error code.