Using templates

Pick a premade template and make it yours.

The fastest way to a working document is to start from one that already works. Every published document is a real HTML template with a declared field contract — not a picture of a document.

Browsing

Documents lists what is published, grouped by the job it does: billing and payments, logistics, insurance, healthcare, education, and branded customer-facing pieces such as vouchers, passes and certificates.

Making one yours

  • Open a document and choose Use this document. It is copied into your workspace with its markup, styles, page setup and sample data intact.
  • Edit the HTML and CSS directly, and preview against sample data or against nothing at all.
  • Adjust the @field block to change the contract — add a key, rename one, mark one @derived so the engine computes it unless you send it.

Rendering it

Press Integrate on any document for the key, the exact field contract, a ready-made request in cURL, JavaScript, Python or a no-code HTTP node, and a live test button that renders it for real.

POST /v1/render renders the published version of a template, so editing it never changes what production returns. Pass "version": "draft" to render what you are currently editing. A template that has never been published renders from its live content.

Two different meanings of “published”

  • Version state decides which bytes render. Publishing freezes the current markup as the version /v1/render serves.
  • Gallery status — draft, pending_review, published — decides only whether the template is listed publicly. It never affects your own key's ability to render it.