canonical: https://jentic.com/apis/prexview.com/prexview

# PrexView API

Jentic publishes the only available OpenAPI specification for PrexView API, keeping it validated and agent-ready. PrexView transforms XML or JSON data into high-quality documents in PDF, HTML, PNG, or JPG format using customizable templates with dynamic value substitution via JSON path syntax. The single /transform endpoint accepts structured data and a template reference, producing rendered output in the requested format for invoices, reports, certificates, or any templated document.

## For AI agents

Transform XML or JSON data into PDF, HTML, PNG, or JPG documents using customizable templates with dynamic value substitution.

## Scope

Does not handle template design, document signing, or file storage - use for data-to-document transformation only.

## Capabilities

- Generate PDF documents from JSON or XML data using pre-defined templates
- Render HTML output from structured data with dynamic value substitution
- Produce PNG and JPG image outputs from template-based document rendering
- Substitute values dynamically using JSON path syntax within templates
- Support multiple output formats from a single template definition

## Use cases

### Invoice and Receipt Generation

Generate professional PDF invoices and receipts from structured JSON data containing line items, totals, customer details, and tax information. PrexView applies a pre-designed template with dynamic value substitution to produce pixel-perfect documents ready for email delivery or archival. This replaces manual document composition with a single API call that accepts data and returns a rendered PDF.

Example prompt: Submit a JSON payload with invoice line items, customer name, and total to the /transform endpoint with output format set to PDF and retrieve the generated invoice document

### Report and Certificate Rendering

Render formatted reports, certificates, or compliance documents from structured data sources. PrexView supports multiple output formats (PDF, HTML, PNG, JPG) from the same template, enabling both web display and print-ready output from a single data submission. The JSON path substitution syntax allows complex nested data to map to any position in the template layout.

Example prompt: Send XML data representing a compliance report to the /transform endpoint requesting HTML output, then re-request with PDF format for a printable version

### AI Agent Document Production

AI agents use PrexView through Jentic to produce formatted documents as part of larger automation pipelines. The agent collects or generates structured data, searches Jentic for document transformation operations, loads the transform endpoint schema, and produces PDF or image output without managing template rendering infrastructure. This enables agents to generate customer-facing documents on demand.

Example prompt: Search Jentic for 'generate PDF from JSON template', load the transform operation schema, and execute with sample invoice data to produce a PDF document

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/transform` | Transform data into a document using a template |

## Key resources

- **Transform** — Convert JSON or XML data into PDF, HTML, PNG, or JPG documents via templates

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 63 / 100
- **View full report:** https://jentic.com/apis/prexview.com/prexview/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring PrexView by hand means setting its API key on the Authorization header, targeting api.prexview.com/v1, and shaping the transform payload with data, template, and output format yourself. Through Jentic you install once, import PrexView from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** PrexView exposes a single transform operation with no resource id in the URL path, so scope the agent by operations: allow it the transform call it needs and nothing more. You choose the operations it may call, so it only runs the document generation you permit.
- **Credential handling:** Your PrexView API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'generate a PDF from JSON data', and Jentic returns the PrexView transform operation with its input schema showing data format, template reference, and output options so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **PDF Generator API** — Template-based PDF generation with a visual template editor
- **PDFMonkey API** — PDF generation from HTML/CSS templates with dynamic data injection
- **PandaDoc API** — Document creation with e-signature and workflow management

## FAQ

### Why is there no official OpenAPI spec for PrexView API?

PrexView does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PrexView API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the PrexView API use?

The PrexView API uses API key authentication passed in the Authorization header. You obtain your API key from the PrexView account dashboard. Through Jentic, this key is stored encrypted in your Jentic One instance and agents receive requests with the Authorization header pre-configured.

### What output formats does PrexView support?

The /transform endpoint supports four output formats: PDF for print-ready documents, HTML for web display, and PNG or JPG for image outputs. You specify the desired format in your request along with the data and template reference.

### What are the rate limits for the PrexView API?

Rate limits depend on your PrexView subscription tier. The API processes document transformations synchronously, so throughput scales with your plan. For high-volume generation, queue requests client-side and process sequentially to avoid exceeding your plan limits.

### How do I generate a PDF from JSON data through Jentic?

Install the SDK with pip install jentic, set your JENTIC_AGENT_API_KEY, then search for 'generate PDF from JSON template'. Jentic returns the /transform operation schema showing required fields: input data (JSON or XML), template reference, and output format. Execute to receive the generated document.

### Does PrexView support dynamic value substitution in templates?

Yes. Templates use JSON path syntax to reference values from your input data. When you submit JSON or XML data to the /transform endpoint, the engine resolves all path expressions in the template against your data, inserting values at the designated positions in the rendered output.

### Can I limit what my agent is allowed to do with the PrexView API?

Yes. Because you run Jentic One yourself, your own rules decide which PrexView operations and credentials your agent may use. PrexView exposes a single transform operation with no resource id in the path, so you scope the agent by operation: grant it only the /transform call that turns your JSON or XML data into a PDF, HTML, PNG, or JPG document, and withhold anything else. Your PrexView API key stays with your instance and is attached only when the agent runs the transform calls you have permitted.