Html2pdf App Html2PDF API
★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey5 EndpointsREST
For Agents
Convert HTML strings or web URLs into PDF documents synchronously or asynchronously, then poll job status and check account usage.
Use for: I need to convert an HTML invoice into a PDF, Generate a PDF from a public web page URL, Queue a long PDF render asynchronously and check it later, Check the status of a pending PDF generation job
Not supported: Does not handle PDF parsing, OCR, form filling, or e-signature workflows — use for generating PDFs from HTML or URLs only.
Jentic publishes the only available OpenAPI specification for Html2PDF API, keeping it validated and agent-ready. Html2PDF is a hosted service that converts raw HTML markup or live URLs into PDF documents using a headless browser rendering engine. The API supports both synchronous and asynchronous generation, custom page sizes, headers and footers, and account inspection for usage tracking. It is designed for applications that need to generate invoices, reports, certificates, or web archives without running a Chromium pipeline themselves.
Install Jentic One Beta
Connect the Html2PDF API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Html2PDF 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 Html2PDF API.
Render an inline HTML string into a PDF document with a single POST to /v1/generate
Convert a live URL into a PDF using the dedicated /v1/generate/url endpoint
Queue large or slow renders asynchronously through /v1/generate/async and reclaim the result later
Poll the status of an async PDF job by jobId via /v1/status/{jobId}
Inspect remaining quota, plan tier, and usage on /v1/account before triggering bulk renders
Use Cases
Patterns agents use Html2PDF API for, with concrete tasks.
★ Generate Invoice PDFs from HTML Templates
Render branded invoice PDFs from server-side HTML templates after each checkout or billing event. Html2PDF accepts the inline HTML string, applies the requested page format, and returns the PDF binary in a single call to /v1/generate. Integration takes under an hour because there is no headless Chromium fleet to operate.
POST an HTML invoice template with totals and line items to /v1/generate using format A4 and return the resulting PDF URL or binary.
Archive Web Pages as PDF Snapshots
Capture full-page PDF snapshots of public URLs for compliance archives, content moderation evidence, or report distribution. /v1/generate/url accepts the target URL and renders the page exactly as a real browser would, including web fonts and JavaScript-rendered content.
Call /v1/generate/url with the URL of yesterday's status page and store the returned PDF in object storage with the date as the filename.
Bulk Async PDF Rendering for Reports
Generate hundreds of monthly statement PDFs without blocking on each render by submitting jobs to /v1/generate/async and polling /v1/status/{jobId}. This pattern keeps the calling agent or worker free while the rendering fleet processes the queue.
Submit 50 monthly statements to /v1/generate/async, then poll /v1/status/{jobId} every 10 seconds until each job completes.
AI Agent PDF Generation via Jentic
An AI agent receives a user request like generate a PDF from this report HTML and uses Jentic to discover and call the Html2PDF endpoint without browsing docs. Jentic returns the input schema, validates the API key from the vault, and executes the call.
Search Jentic for generate a pdf from html, load the Html2PDF /v1/generate operation, and execute it with the user-supplied HTML body.
Key Endpoints
5 endpoints — jentic publishes the only available openapi specification for html2pdf api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/v1/generate
Generate PDF from HTML or URL
POST
/v1/generate/url
Generate PDF from URL
POST
/v1/generate/async
Queue an async PDF render
GET
/v1/status/{jobId}
Get the status of an async job
GET
/v1/account
Inspect account quota and plan
POST
/v1/generate
Generate PDF from HTML or URL
POST
/v1/generate/url
Generate PDF from URL
POST
/v1/generate/async
Queue an async PDF render
GET
/v1/status/{jobId}
Get the status of an async job
GET
/v1/account
Inspect account quota and plan
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Html2PDF API key is stored encrypted in the Jentic vault and injected into the Authentication header at execution time. Agents never see the raw token.
Intent-based discovery
Agents search Jentic with natural language like generate a pdf from html and Jentic returns the matching Html2PDF operation with its input schema, ready to execute.
Time to first call
Direct integration: 1-2 hours for auth, error handling, and async polling. Through Jentic: under 10 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Html2PDF API through Jentic.
Why is there no official OpenAPI spec for Html2PDF API?
Html2PDF.app does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Html2PDF 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 Html2PDF API use?
The Html2PDF API uses an API key passed in the Authentication header in the format Token <api-key>. Through Jentic, the key is held in the encrypted vault and never enters the agent context — Jentic injects it at execution time.
Can I generate a PDF from a URL with the Html2PDF API?
Yes. POST the target URL to /v1/generate/url and the service renders the live page with a headless browser, returning the PDF binary or a hosted URL depending on the request mode.
What are the rate limits for the Html2PDF API?
Limits depend on the plan tier attached to your API key. Call GET /v1/account to inspect remaining quota and plan details before launching a bulk render so the agent does not exhaust credits mid-job.
How do I generate a PDF asynchronously through Jentic?
Search Jentic for generate a pdf from html, load the /v1/generate/async operation, execute it with the HTML body, then poll /v1/status/{jobId} until the job state becomes complete and download the result.
Is the Html2PDF API free?
Html2PDF.app offers a free tier with a monthly request quota and paid plans for higher volumes. Check current quota at /v1/account before bulk runs.
GET STARTED