Concepts#

Four things hold no matter which EnConvert endpoint you call: how you reach the API, whether a call answers inline or hands you a job to poll, how the output file gets to you, and which half of the API your task belongs to. These four pages cover them once so the endpoint reference can stay about endpoints.

The four pages#

• REST, MCP and CLI: there is one HTTP API, and the MCP server, the CLI, the n8n node and the ten SDKs are all clients of it, authenticated by the same sk_ key.
• Sync and Async Jobs: some calls return the finished result in the response body, others return an id you poll until it reaches a terminal status. This page says which endpoints do which.
• Signed URLs: output files come back as time-limited signed download links rather than inline bytes, so this page covers the expiry window, what happens after it, and how to stream the bytes directly instead.
• V1 and V2: V1 converts files and URLs between formats, V2 reads live web pages into agent-ready data. Same key, same monthly allowance, different shape of request.

Not sure where to start#

If you have not made a request yet, read the Quickstart first: it gets one working call in three steps. Authentication covers the two key types and when each applies. Once you need parameter-level detail, Endpoints is the reference, and Guides holds the task-shaped walkthroughs for uploads, webhooks and batches.