EnConvert File Conversion API#

Enconvert is a RESTful file conversion API for converting documents, images, data formats, and web pages between formats — for example, turning a URL into a PDF via /v1/convert/url-to-pdf. It gives developers programmatic access to 49 conversion endpoints plus six V2 web intelligence endpoints, without managing conversion infrastructure. Requests run in synchronous or asynchronous mode, and batch processing converts multiple files or URLs in a single request.

Beta: The Enconvert API is currently in beta. Endpoints, parameters, and response formats may change as we refine the platform based on developer feedback. We recommend pinning to specific behavior rather than relying on undocumented fields.

Base URL:

https://api.enconvert.com

All API requests should be made to this base URL, followed by the appropriate endpoint path (e.g., https://api.enconvert.com/v1/convert/url-to-pdf).

Key Features#

49 conversion endpoints covering documents, data formats, images, and web pages
Web intelligence (V2, beta) -- perceive, discover, search, extract, ingest, and monitor web pages through six /v2 endpoints
Two authentication methods -- private keys for server-to-server integration and public keys with JWT for client-side usage
Batch processing -- convert multiple files or URLs in a single request
Synchronous and asynchronous modes -- get results immediately or poll for completion on long-running jobs
Job notifications -- receive webhook callbacks when async conversions complete
Web widgets -- embed conversion functionality directly into your web application
No SDK required -- use standard HTTP requests from any language or platform

Supported Conversions#

Web Pages#

Conversion	Endpoint
URL to PDF	`/v1/convert/url-to-pdf`
URL to Screenshot	`/v1/convert/url-to-screenshot`
URL to Markdown	`/v1/convert/url-to-markdown`
Website to PDF	`/v1/convert/website-to-pdf`
Website to Screenshot	`/v1/convert/website-to-screenshot`

Data Formats#

Conversion	Endpoint
JSON to XML	`/v1/convert/json-to-xml`
XML to JSON	`/v1/convert/xml-to-json`
JSON to YAML	`/v1/convert/json-to-yaml`
YAML to JSON	`/v1/convert/yaml-to-json`
JSON to CSV	`/v1/convert/json-to-csv`
CSV to JSON	`/v1/convert/csv-to-json`
JSON to TOML	`/v1/convert/json-to-toml`
TOML to JSON	`/v1/convert/toml-to-json`
CSV to XML	`/v1/convert/csv-to-xml`
XML to CSV	`/v1/convert/xml-to-csv`
Markdown to HTML	`/v1/convert/markdown-to-html`

Documents to PDF#

Conversion	Endpoint
HTML to PDF	`/v1/convert/html-to-pdf`
Markdown to PDF	`/v1/convert/markdown-to-pdf`
Word to PDF	`/v1/convert/doc-to-pdf`
Excel to PDF	`/v1/convert/excel-to-pdf`
PowerPoint to PDF	`/v1/convert/ppt-to-pdf`
Pages to PDF	`/v1/convert/pages-to-pdf`
Numbers to PDF	`/v1/convert/numbers-to-pdf`
ODT to PDF	`/v1/convert/odt-to-pdf`
ODS to PDF	`/v1/convert/ods-to-pdf`
ODP to PDF	`/v1/convert/odp-to-pdf`
OTS to PDF	`/v1/convert/ots-to-pdf`

Image Conversions#

Conversion	Endpoint
JPEG to PNG	`/v1/convert/jpeg-to-png`
PNG to JPEG	`/v1/convert/png-to-jpeg`
JPEG to SVG	`/v1/convert/jpeg-to-svg`
SVG to JPEG	`/v1/convert/svg-to-jpeg`
JPEG to HEIC	`/v1/convert/jpeg-to-heic`
HEIC to JPEG	`/v1/convert/heic-to-jpeg`
JPEG to WebP	`/v1/convert/jpeg-to-webp`
WebP to JPEG	`/v1/convert/webp-to-jpeg`
PNG to SVG	`/v1/convert/png-to-svg`
SVG to PNG	`/v1/convert/svg-to-png`
PNG to HEIC	`/v1/convert/png-to-heic`
HEIC to PNG	`/v1/convert/heic-to-png`
PNG to WebP	`/v1/convert/png-to-webp`
WebP to PNG	`/v1/convert/webp-to-png`
SVG to HEIC	`/v1/convert/svg-to-heic`
HEIC to SVG	`/v1/convert/heic-to-svg`
SVG to WebP	`/v1/convert/svg-to-webp`
WebP to SVG	`/v1/convert/webp-to-svg`
HEIC to WebP	`/v1/convert/heic-to-webp`
WebP to HEIC	`/v1/convert/webp-to-heic`
PDF to JPEG	`/v1/convert/pdf-to-jpeg`

Web intelligence (V2)#

The V2 endpoints turn a URL into something an application can use: clean Markdown, structured data, a search result set, RAG-ready chunks, or a change alert. They run on the same headless Chrome engine and the same API keys as the conversion endpoints, but they are metered on separate quota counters and have their own beta status.

Endpoint	What it does
`/v2/perceive`	Render a URL once and return Markdown, HTML, a screenshot, a PDF, links, and structured data from that single render.
`/v2/discover`	Enumerate a site's URLs from its sitemap and an HTTP crawl, without rendering each page.
`/v2/lookup`	Run a web, news, scholar, or maps search and optionally perceive the top results.
`/v2/distill`	Extract data matching a JSON schema, with a free CSS pass and a Claude LLM fallback.
`/v2/ingest`	Crawl a site into RAG-ready chunks and one JSONL file, delivered asynchronously.
`/v2/watch`	Monitor a URL for changes and notify you by webhook or email when it changes.

Separate quota: V2 operations do not draw from your V1 conversion quota, and V1 plans include no V2 quota. You need a V2-inclusive plan to call these endpoints. See the V2 overview and the pricing page for per-tier allowances.

Frequently asked questions#

What file formats can I convert with the Enconvert file conversion API?#

The API exposes 49 conversion endpoints across four categories: web pages (URL to PDF, screenshot, or Markdown), data formats (JSON, XML, YAML, CSV, TOML, Markdown, HTML), documents to PDF (Word, Excel, PowerPoint, Pages, Numbers, and OpenDocument formats), and image conversions (JPEG, PNG, SVG, HEIC, WebP).

Do I need an SDK to use the file conversion API?#

No. Enconvert requires no SDK — you make standard HTTP requests from any language or platform to the base URL https://api.enconvert.com, followed by the endpoint path such as /v1/convert/url-to-pdf.

Does the API support asynchronous file conversion?#

Yes. The API offers synchronous and asynchronous modes — get results immediately or poll for completion on long-running jobs — and job notifications deliver webhook callbacks when async conversions complete.

How do I authenticate with the Enconvert API?#

Two authentication methods are supported: private keys for server-to-server integration and public keys with JWT for client-side usage.

Do the V2 web intelligence endpoints use the same quota as V1 conversions?#

No. V2 operations are metered on separate quota counters and do not draw from your V1 conversion quota, and V1 plans include no V2 quota — you need a V2-inclusive plan to call the six /v2 endpoints.

Quick Start →

API Documentation