Document Generation

JSON In. Governed PDF Out. Any Application. One API Call.

A platform-agnostic REST API that accepts a JSON payload and returns a correctly formatted, approved PDF. Works with any application that can make an HTTP request. No CRM required. Average response under 50ms.

Document Generation Logic Should Not Live In Your Application Code.

Most teams end up with document selection logic hardcoded into the application that needs it: which templates to call, under which conditions, for which states. It works until a regulation changes or a new state gets added. Then it means a pull request, a review, and a deployment for something that has nothing to do with your application's core function.

Templx moves that logic out of your codebase and into the rules engine, where it can be updated by the compliance team without involving engineering. Your application sends a data payload. The platform handles document selection, version resolution, and generation.

How The Generation API Works.

  1. 01
    Platform-Agnostic REST API
    One endpoint. Works with any application that can make an HTTP request. The generation API accepts a standard JSON payload and returns a governed PDF in the response body. No SDK required. No platform-specific integration.
  2. 02
    Approved-Only Generation
    The API will only generate from templates that have completed their approval workflow. No override exists. When a generation request arrives for a template that is not approved and active, the request returns an error rather than generating from an unapproved version.
  3. 03
    Rules Engine at Generation Time
    Payload fields evaluated against configured rules with no template ID required in the request. When rules are configured in the workbench, the platform selects the correct approved template automatically based on incoming payload values.
  4. 04
    Tenant Isolation at the API Level
    Every request resolved within the tenant scope. No cross-tenant data access at any layer. The tenant is identified in every request and the rules engine, template library, and generation history all operate within that tenant boundary.
  5. 05
    Embeddable Rules Engine
    Surface document selection rules configuration inside your own application UI as a self-contained component. For ISVs and platform builders, the rules engine can be embedded as a micro-frontend so end users configure document rules inside your product without needing workbench access.

Generation Is The Last Step. Governance Is What Makes It Safe.

The generation API is the final step in the platform workflow. Every document it produces has been authored on an approved template, versioned through a completed workflow, and selected by rules configured in the workbench. The API does not operate independently. It is the delivery mechanism for a governed process that starts in the Word add-in.

Platform flow
Template Authoring
Template created in Word
View
Approval Workflows
Template approved and versioned
View
Rules Engine
Conditions configured in workbench
View
Document Generation
You are here

One Endpoint. Any Application. Governed Every Time.

Request a demo to see the full platform in action, or go straight to the developer documentation.