Pdftemplateapi TemplateFox API
★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting QaapiKey12 EndpointsREST
For Agents
Generate PDFs from HTML/CSS templates with Jinja2 data binding. Supports sync and async generation, template management, job tracking, and S3 delivery integration.
Use for: I need to generate a PDF from an HTML template with dynamic data, I want to check the status of an async PDF generation job, List all templates available in my account, Get the fields required by a specific template
Not supported: Does not handle URL-to-PDF conversion, visual template design via API, or document signing — use for HTML/CSS/Jinja2 template-to-PDF generation only.
Jentic publishes the only available OpenAPI specification for TemplateFox API, keeping it validated and agent-ready. TemplateFox API generates PDF documents from HTML/CSS templates with Jinja2 templating support. The service offers both synchronous and asynchronous PDF creation, template management with field extraction, job tracking, account monitoring, and S3 integration for direct file delivery. It provides 12 endpoints covering the full document generation lifecycle from template upload to PDF output.
Install Jentic One Beta
Connect the TemplateFox API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the TemplateFox API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with TemplateFox API.
Generate PDFs from HTML/CSS templates with Jinja2 variable substitution
Process PDF generation asynchronously with job status tracking
Extract template field definitions for dynamic data binding
Deliver generated PDFs directly to an S3 bucket via integration
Monitor account usage and transaction history
Manage templates with listing and field introspection
Use Cases
Patterns agents use TemplateFox API for, with concrete tasks.
★ Dynamic Document Generation from Templates
Generate personalized PDF documents by rendering HTML/CSS templates with Jinja2 variable substitution. TemplateFox accepts template data as JSON and produces formatted PDFs with full CSS styling support. This enables non-developers to maintain document layouts in HTML while developers supply dynamic data via API calls.
POST to /v1/pdf/create with template ID and Jinja2 data variables to generate a PDF document synchronously
Async Batch Document Processing
Queue multiple PDF generation jobs and track them independently. POST to /v1/pdf/create-async to start generation, then poll /v1/pdf/jobs/{job_id} for status. This handles high-volume scenarios where generating hundreds of documents without blocking the calling application is required.
POST to /v1/pdf/create-async with template data, then GET /v1/pdf/jobs/{job_id} to poll until the job status shows completion
Template Field Discovery and Validation
Extract the list of required fields from a template before generating a document. GET /v1/templates/{template_id}/fields returns the variable names expected by the Jinja2 template, enabling upstream systems to validate data completeness before submitting a generation request.
GET /v1/templates/{template_id}/fields to retrieve required field names, then validate the data payload contains all fields before calling /v1/pdf/create
AI Agent PDF Workflow via Jentic
AI agents produce PDF documents as part of automated pipelines by calling TemplateFox through Jentic. The agent discovers template operations, inspects required fields, and generates documents without managing API keys or understanding Jinja2 template syntax directly.
Search Jentic for 'generate PDF from HTML template', load the /v1/pdf/create operation schema, and execute with template ID and data variables
Key Endpoints
12 endpoints — jentic publishes the only available openapi specification for templatefox api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v1/pdf/create
Generate a PDF synchronously from a template
POST
/v1/pdf/create-async
Queue async PDF generation from a template
GET
/v1/pdf/jobs/{job_id}
Check the status of an async PDF job
GET
/v1/pdf/jobs
List all PDF generation jobs
GET
/v1/templates
List all available templates
GET
/v1/templates/{template_id}/fields
Get required fields for a template
GET
/v1/account
Retrieve account details and usage
POST
/v1/integrations/s3
Configure S3 integration for PDF delivery
POST
/v1/pdf/create
Generate a PDF synchronously from a template
POST
/v1/pdf/create-async
Queue async PDF generation from a template
GET
/v1/pdf/jobs/{job_id}
Check the status of an async PDF job
GET
/v1/pdf/jobs
List all PDF generation jobs
GET
/v1/templates
List all available templates
GET
/v1/templates/{template_id}/fields
Get required fields for a template
GET
/v1/account
Retrieve account details and usage
POST
/v1/integrations/s3
Configure S3 integration for PDF delivery
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
TemplateFox API keys are stored encrypted in the Jentic vault. Agents receive scoped access — the raw x-api-key header value never enters the agent context.
Intent-based discovery
Agents search by intent (e.g., 'generate PDF from HTML template') and Jentic returns matching operations including /v1/pdf/create with full input schemas for template ID and data variables.
Time to first call
Direct integration: 2-3 days for template setup, async polling, S3 configuration, and error handling. Through Jentic: under 20 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using TemplateFox API through Jentic.
Why is there no official OpenAPI spec for TemplateFox API?
TemplateFox (pdftemplateapi.com) does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call TemplateFox API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the TemplateFox API use?
TemplateFox API uses an API key passed in the x-api-key header. You obtain the key from your account dashboard. Through Jentic, this key is stored encrypted in the vault and injected into request headers automatically.
What templating language does TemplateFox support?
TemplateFox uses Jinja2 for template variable substitution within HTML/CSS templates. You define variables with double curly braces in your HTML template, then pass corresponding values as JSON in the API request body.
How do I check which fields a template requires?
GET /v1/templates/{template_id}/fields returns the list of Jinja2 variable names expected by the template. Use this to validate your data payload before submitting a generation request to /v1/pdf/create.
How do I generate PDFs through Jentic with TemplateFox?
Install with pip install jentic, search for 'generate PDF from HTML template', and Jentic returns the /v1/pdf/create operation schema. Execute with your template ID and data variables. Jentic handles the x-api-key header injection automatically.
Can I deliver generated PDFs directly to S3?
Yes. Configure your S3 bucket credentials via POST /v1/integrations/s3, test the connection with /v1/integrations/s3/test, and generated PDFs will be delivered directly to your bucket without needing to download them from the API response.
GET STARTED