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

# PDF Endpoint API

Jentic publishes the only available OpenAPI specification for PDF Endpoint API, keeping it validated and agent-ready. PDF Endpoint API converts HTML content or URLs to PDF documents through a single REST endpoint. The service accepts either raw HTML markup or a public URL and returns a rendered PDF with configurable page size, orientation, and margin settings. It is designed for lightweight, on-demand document generation without managing headless browser infrastructure.

## For AI agents

Convert HTML content or a URL to a PDF document with configurable page settings. Single-endpoint service for on-demand PDF generation.

## Scope

Does not handle template management, batch processing, or format conversion beyond PDF - use for single-call HTML/URL to PDF conversion only.

## Capabilities

- Convert raw HTML markup into a downloadable PDF document
- Render a live webpage at a given URL as a PDF snapshot
- Configure page size, orientation, and margins for PDF output
- Generate PDFs without provisioning headless browser infrastructure
- Return PDF as a binary download or hosted file URL

## Use cases

### Invoice and Receipt Generation

Generate PDF invoices or receipts from HTML templates populated with transaction data. PDF Endpoint API accepts the rendered HTML and returns a formatted PDF document in a single API call. This eliminates the need to run headless Chrome or wkhtmltopdf on your own servers, reducing infrastructure costs for transactional document generation.

Example prompt: POST to /v1/convert with HTML containing a populated invoice template and return the generated PDF binary

### Webpage Archiving

Capture a point-in-time PDF snapshot of a public webpage for compliance, archival, or evidence purposes. PDF Endpoint API renders the page exactly as a browser would, including CSS styling and images, producing a faithful visual record without maintaining screenshot infrastructure.

Example prompt: POST to /v1/convert with a target URL and A4 landscape orientation to capture a full-page PDF archive

### Report Export

Export dashboard reports or data summaries to PDF by sending rendered HTML output from a reporting engine. PDF Endpoint API handles the conversion so that downstream consumers receive portable, print-ready documents without needing PDF rendering libraries installed locally.

Example prompt: Submit HTML report content to /v1/convert with custom margins and letter page size to produce a formatted PDF report

### AI Agent Document Generation via Jentic

AI agents generate PDF documents on the fly by calling PDF Endpoint API through Jentic. The agent searches for a PDF conversion operation, receives the schema for /v1/convert, and executes the call with HTML payload. This enables automated document workflows where agents produce PDFs as part of larger task chains without manual integration work.

Example prompt: Search Jentic for 'convert HTML to PDF', load the /v1/convert operation schema, and execute with HTML content to produce a PDF document

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /v1/convert | Convert HTML or a URL to a PDF document |

## Key resources

- **Convert** — Convert HTML content or a URL to a PDF document with layout options

## Why Jentic

- **Setup:** Wiring the PDF Endpoint API by hand means managing the Authorization API-key header and shaping the HTML or URL conversion payload yourself. Through Jentic you install once, import PDF Endpoint from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** PDF Endpoint exposes a single conversion operation that takes its HTML or URL in the request body, so the agent's scope is exactly that operation: convert to PDF, and nothing more. You choose whether to grant it, so no other capability is available.
- **Credential handling:** Your PDF Endpoint API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'convert HTML to PDF', and Jentic returns the /v1/convert operation with its full input schema so the agent calls the endpoint without reading the reference docs.

## Related APIs

- **HTML2PDF API** — Another HTML-to-PDF service with additional rendering options
- **PDFmyURL API** — URL-to-PDF conversion with watermarks, headers, footers, and encryption
- **CloudConvert API** — Multi-format file conversion including PDF to other formats

## FAQ

### Why is there no official OpenAPI spec for PDF Endpoint API?

PDF Endpoint does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PDF Endpoint 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 PDF Endpoint API use?

PDF Endpoint API uses an API key passed in the Authorization header. Through Jentic, this key is stored encrypted in the credential vault and agents receive scoped access without handling the raw key directly.

### Can I convert a URL to PDF with the PDF Endpoint API?

Yes. The /v1/convert endpoint accepts a url parameter with a publicly accessible web address. The service renders the page with full CSS and image support, then returns the PDF output.

### What page layout options does the PDF Endpoint API support?

You can configure page size (A4, Letter, Legal, and others), orientation (portrait or landscape), and custom margins (top, bottom, left, right in millimeters) when calling /v1/convert.

### How do I generate a PDF from HTML through Jentic?

Install the SDK with pip install jentic, then search for 'convert HTML to PDF'. Jentic returns the /v1/convert operation schema. Execute the call with your HTML payload in the body and receive the PDF binary in the response.

### Are there rate limits on the PDF Endpoint API?

Rate limits depend on your subscription plan. The API returns HTTP 429 responses when the limit is exceeded. Check your account dashboard for current allocation details.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. The PDF Endpoint API exposes a single operation, POST /v1/convert, which turns HTML or a URL into a PDF, so you can grant your agent exactly that one call and nothing else. Your stored API key is injected only when that operation runs, so the agent can convert documents without gaining any wider access.