Templates. Your wording.

A preset template is a layout registered by this deployment. Its catalog entry includes a complete, editable request example; in the API response the existing example property means a ready-to-submit request body, not a separate template definition. The production deployment exposes its production catalog. The downloadable application defaults to the smaller generic catalog. Preset catalog reads, detail pages, and request-example downloads require a valid X-Api-Key. Browse the preset references or use GET /api/v1/templates/{id} with the key in a request header.

Each PDF request can provide labels and data maps. Text fields in a layout can refer to them as {{labels.heading}} and {{data.name}}. You provide the printable labels and values on each call. Every referenced key must be present.

{
  "template": {
    "title": "{{data.title}}",
    "pages": [{ "layout": "flow", "blocks": [
      { "type": "heading", "text": "{{labels.heading}}" },
      { "type": "paragraph", "text": "{{data.summary}}" }
    ] }]
  },
  "labels": { "heading": "Project overview" },
  "data": { "title": "October update", "summary": "Prepared by Alex Example." }
}

Labels must be strings. Data may be strings, numbers, or booleans. Every referenced key is required. Legacy preset templates also accept a compact body containing only labels, data, and optional options; the selected preset supplies the layout, and your maps replace its sample values. For other request types, send the full request example. Images and fonts are supplied as base64; use each catalog entry and the OpenAPI schema for supported fields.