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.

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

Yes. Because you run Jentic One yourself, your own rules decide which TemplateFox operations and credentials the agent can use. For example, you can allow it to render PDFs with /v1/pdf/create and read job status at /v1/pdf/jobs/{job_id} while excluding the S3 integration setup at /v1/integrations/s3 unless you add it. Your API key stays in your own instance and is injected only for the operations you have permitted.