For Developers

One Integration. Governed Documents For Every Application You Build.

Templx is a REST API that accepts a JSON payload and returns a governed PDF. Platform-agnostic, multi-tenant by design, and built to remove document generation logic from your codebase permanently.

Request a demo

REST API JSON / PDF Multi-tenant No CRM dependency Platform-agnostic Avg. response <50ms

POST /api/v1/generateLive endpoint
// Send your application data
POST /api/v1/generate

{
 "tenant": "first-community-bank",
 "payload": {
 "account_type": "checking",
 "customer_type": "individual",
 "state": "California",
 "account_number": "ACT-2026-88421"
 }
}

// Rules engine evaluates payload conditions
// Selects: Reg E Notice v6, Reg DD v4,
// CA State Notice v2 (all approved)

200 OK Content-Type: application/pdf
// 3 governed PDFs returned 41ms
No template ID required rules engine selects the correct approved set automatically

How It Works

JSON In. Governed PDF Out. That Is The Entire Integration.

Three things happen when your application calls the Templx API. The tenant is identified from the request. The rules engine evaluates the payload against the active rule set and selects the correct approved templates. The documents are generated and returned as PDFs.

Your application does not need to know which templates are required. It does not carry document selection logic. It sends data and receives governed documents. Everything else template authoring, approval workflows, version management, rules configuration happens in the workbench, managed by the compliance team without involving your engineering team.

See document generation in detail See how the rules engine works

Your application sends a JSON payload

Include the tenant identifier and your application data account type, state, loan attributes, or whatever fields drive document selection for your use case.

Rules engine evaluates the payload

Active rules for that tenant are evaluated against the incoming payload. The correct set of approved templates is selected automatically no template ID required in the request.

Approved templates generate the documents

Each matched template is an approved version compliance reviewed it before it went live. The documents are generated and the PDFs are returned in the response.

Your application delivers to the end user

Templx returns the governed PDFs. Your application handles delivery email, download, document management system, or whatever your workflow requires.

What You Get Out Of The Box

The Infrastructure Most Teams Build Themselves.

Six components that would each take weeks to build from scratch included in a single API integration.

Word-Native Template Authoring

A Microsoft Word add-in for mapping data fields onto existing regulatory forms. Floating placeholders, no layout disruption. Your compliance team uses it no engineering involvement.

Configurable Approval Workflows

Sequential, parallel, and conditional routing. Every template version gated by a completed workflow before it can serve documents. Visual designer, escalation engine, full audit trail. Built in not bolted on.

Multi-Tenant Architecture

Every client or department gets a completely isolated environment. Separate templates, workflows, users, and document history. Zero data bleed between tenants. Architectural default not a configuration.

Rules Engine

Payload conditions evaluated at generation time to select the correct template set. No template ID required in the request. Document selection logic lives in the platform updated by the compliance team without code changes.

Full Audit Trail

Every template version, approval action, and generation event logged automatically with a timestamp and user identity. No additional logging from your integration. Complete from the moment the platform is in use.

Embeddable Micro-Frontend

The rules engine configuration interface embeds into your own platform as a self-contained component. Your users configure document selection rules inside your product without leaving it or needing a Templx login.

Multi-Tenant By Design

One Integration Serves Every Client You Onboard.

If you are building a platform for regulated industry clients a LOS, a policy administration system, a banking platform Templx is designed for your architecture. You integrate the API once. Every client you onboard becomes a tenant with their own completely isolated environment.

When a client's regulation changes, they update their templates in the workbench. Their update does not create work for your team.
When you onboard a new client, you create a new tenant. They inherit the full governed infrastructure from the first request.
Every client's audit trail builds from day one. When their regulator asks questions, the record is already there.
Tenant data isolation is architectural, not a configuration option. Nothing in one tenant's environment can touch another.

See the ISV and platform builders solution

One integration multiple isolated tenants

Your application

Single API integration tenant resolved per request

Templx API

Tenant identified · Rules evaluated · PDF generated

Client A

Own templates

Client B

Own templates

Client C

Own templates

Complete data isolation between all tenants architectural, not configurable

One Integration. Governed Documents For Every Application You Build.

JSON In. Governed PDF Out. That Is The Entire Integration.

The Infrastructure Most Teams Build Themselves.

One Integration Serves Every Client You Onboard.

Ready To Integrate?