Skip to content

Templates

Branded documents generated from your data.

7 tools — 4 read, 3 write.

ToolWhat it does
delete_templatewritePermanently delete a template.
get_templatereadFetch a template's full definition — chrome (page geometry, header/footer, css), ordered blocks, inputs JSON Schema, formats, and audit fields.
get_template_schemareadFetch a template's metadata + inputs JSON Schema.
list_templatesreadList all HTML templates registered in the active org, ordered most-recent-first.
register_templatewriteRegister a deterministic, block-based template that renders to a PDF (server-side via WeasyPrint).
render_templatereadRender a registered template with the given inputs.
update_templatewritePartially update an existing template (id or slug).

Calling these

Over MCP, find one with search_tools, then run it with execute_tool. Over REST, POST /api/capabilities/<tool> with the arguments as the JSON body. Either way, fetch the input schema for the tool you're about to call rather than guessing — get_tool_schema over MCP, or GET /api/capabilities?name=<tool> over REST.

See How the API works for auth, errors and the shared envelope.

Docs as of 2026-08-31.