Core concepts
Templates, schemas, and data
Understand the boundary between visual document design and application-owned data.
Reviewed 2026-08-05 · PDFDesignAPI Engineering
Templates own presentation
A template defines page dimensions, components, visual styles, bindings, repeat behavior, and conditions.
Treat templates as presentation artifacts. Keep prices, tax calculations, permissions, and other business rules in your application.
The schema is the contract
Each template has a structured data schema and example values used while designing.
Bindings refer to fields in this schema. Validate production payloads against the selected template version or environment before rendering.
Bindings connect the two
Text, images, QR codes, tables, repeaters, and conditions can consume values from the request data.
Use realistic example data, including long text and large arrays, to test layout behavior before promotion.