EnConvert API Guides#

These pages answer "how do I do X". The endpoint pages answer "what does this endpoint do", so start here when you know the outcome you want but not yet the route that gets you there.

The four guides#

File ingestion covers every way to hand EnConvert some bytes: a multipart upload, or a URL the API fetches for you, plus size ceilings, filename rules, and what a rejected upload looks like.

Webhooks gets you told when a job finishes instead of polling for it: the callback payloads, signature verification, and retries.

Batch processing converts many URLs in one request and collects the results either one file at a time or as a single ZIP.

Integrations lists the surfaces that are already built: the MCP server for coding agents, the n8n node, the CLI, ten SDKs, and the embeddable web widget.

Where to look instead#

• Per-route request and response shapes live under Endpoints.
• The ideas these guides assume, like sync versus async jobs and signed output URLs, are in Concepts.
• Error codes, plan quotas, request rate limits and the format list are in Reference.

New to the API? Do the quickstart first. It takes one API key and one request.