Doctavian's Document Generation API lets you produce rich, data-driven documents entirely server-side. You define a template in the tools your team already uses, connect it to your data, and Doctavian handles the rendering — synchronously for fast, on-demand generation or asynchronously for high-volume batch workloads.
The output can be a PDF, DOCX, XLSX, CSV, PPTX, or a native Google format. The use case can be anything: contracts, invoices, onboarding packs, compliance reports, financial summaries, or any document your business runs on.
Document generation in Doctavian is built around three connected building blocks. Understanding how they fit together is the fastest way to get productive.
A Document Solution is the top-level configuration that ties everything together. It links a template to a data source and defines how the document should be generated — output format, locale, processing mode (sync or async), storage destination, and more.
Once configured, a Document Solution becomes a named, reusable pipeline. Triggering a generation request against it produces a Document Request — a trackable record of the generation job that carries the status (New, Processing, Completed, Error) and, on completion, a reference to the output file.
Learn about Document Solutions →
A Data Source tells a Document Solution where its data comes from. The simplest and most common approach is uploading a JSON file already structured to match your template. More advanced load methods are also available for connecting to live external data.
A Data Source belongs to one Document Solution, which is what ties it to a template and a generation pipeline. The same Data Source can be reused across multiple Document Solutions — useful when the same data needs to drive several different layouts or output formats.
A Document Template is the file that defines the structure and appearance of your output document. Templates are built in the authoring tools your team already knows — Microsoft Word (DOCX), Excel (XLSX), PowerPoint (PPTX), Google Docs, Google Sheets, or Google Slides.
Inside the template, you place Elements — the building blocks that tell Doctavian where and how to inject data, from simple text fields to repeating tables, conditional sections, images, barcodes, QR codes, hyperlinks, and charts.
Expressions add logic on top — formatting values, applying conditions, and controlling visibility dynamically at generation time. A template can produce multiple output formats from a single source file.
Learn about Document Templates →
Doctavian supports six template formats, each producing a specific set of output formats. See the full Supported File Formats for the complete matrix including PDF conformance and version settings.
All data is transmitted over HTTPS and processed in isolated, per-request transactions. Doctavian does not persist any business data after generation — your data lives only for the duration of the merge and ends up in the generated document. Output files are stored in the destination of your choice. The platform complies with GDPR and undergoes annual penetration testing.