For SaaS developers

Generate documents from the data your product already owns.

Teleza is built for teams that want reporting output behind their own application experience: one scoped key, one template key, rows from the product database, and a PDF or spreadsheet response.

Run the quickstart Choose a template Request a key

The shortest path

  1. Pick a template key from the public gallery.
  2. Call the schema endpoint to inspect canonical fields and accepted aliases.
  3. Query your own database or service for the rows needed for one document.
  4. Preview the render to catch missing fields, mapping errors, totals, grouping, or photo warnings.
  5. Export PDF, Excel, CSV, JSONL, or NDJSON.

Payload-first

Best when the buyer should keep database access inside their own app. Send only the rows needed for the document.

Data-source backed

Best when Teleza should connect to a customer-owned REST API, PostgreSQL, SQL Server, CSV, or Excel source.

Saved-report workflow

Best for reusable definitions, preview, scheduled delivery, execution history, and usage review.

Developer contract

X-API-Key: <customer-scoped-api-key> GET /api/whiteLabelEngine/v1/templates/{key}/schema GET /api/whiteLabelEngine/v1/templates/{key}/sample GET /api/whiteLabelEngine/v1/templates/design-themes POST /api/whiteLabelEngine/v1/render/preview POST /api/whiteLabelEngine/v1/render POST /api/whiteLabelEngine/v1/template-mappings/validate POST /api/whiteLabelEngine/v1/template-mappings POST /api/whiteLabelEngine/v1/data-sources PUT /api/whiteLabelEngine/v1/data-sources/{key} POST /api/whiteLabelEngine/v1/reports POST /api/whiteLabelEngine/v1/reports/{reportId}/execute?format=pdf

Client options are deliberately staged for private beta: use the packaged .NET SDK, Python/TypeScript copy-paste kits, or raw REST/OpenAPI today. Teleza also captures generated SDK evidence for future TypeScript, Python, and Go packages, but those generated clients are not official public package releases yet.

Review client options

Customization without layout work

For early pilots, many changes can come through the payload instead of a custom designer session: company name, logo text, header lines, footer note, safe colors, currency, locale, decimal places, page size, orientation, grouping, and totals placement. If the buyer wants a faster visual starting point, set branding.designTheme to an original Teleza preset such as typecentric-minimalist, corporate-high-contrast, or bold-geometric.

Sensitive payload fields can be protected with masking.rules so emails, card references, identification numbers, or claim/member references are redacted before preview and export.

Every render preview returns lineage.contractHash with template, schema, design-theme, mapping, option-hash, column, and row count evidence. That lets a developer capture a deterministic support fingerprint before exporting the final binary document.

Because Teleza is payload-driven during private beta, a design partner can send application rows straight to the render preview endpoint and inspect a visual result before payment automation or custom production terms are in place.

When source columns are stable, save a mapping once so future renders can reference a mappingKey rather than repeating every field name.