Official REST API

One HTTP API. Every conversion, one base URL.

Forty nine conversion endpoints across web pages, data formats, documents and images, plus six web intelligence endpoints that render, search, extract and monitor live pages. Everything hangs off api.enconvert.com, and every conversion answers with a presigned download link.

curl -X POST https://api.enconvert.com/v1/convert/url-to-pdf -H "X-API-Key: sk_..." -d '{"url":"https://example.com"}'
Authentication

Two key types, one header away.

Pick the key that matches where the request comes from. Both are created and revoked from the dashboard.

Private keys for your server

Send a key that starts with sk_ in the X-API-Key header. Full access to every endpoint, including sync, async and batch. Keys are stored as SHA-256 hashes, so the plaintext is shown once at creation and never again.

X-API-Key: sk_...

Public keys for the browser

Exchange a key that starts with pk_ for a short-lived JWT at POST /v1/auth/token, then send it as Authorization: Bearer. Public keys only work from the domains you whitelist, and POST /v1/auth/refresh renews the token before it expires.

Authorization: Bearer <token>

A private key used from a browser is rejected outright. The API reads the Origin header and refuses sk_ keys from browser environments, so a leaked server key cannot be replayed from a page.

Read the authentication guide
Endpoints

Forty nine conversions. Six more for the web itself.

Web page endpoints take a JSON body of URLs. Data format, document and image endpoints take a multipart/form-data upload. The V2 endpoints take JSON and share the same keys and domain allowlist on their own quota counters.

  1. Web pages

    5 endpoints

    Render any URL as a PDF, a screenshot or clean markdown, and roll a whole site into one document. Batch and async are both supported.

    POST /v1/convert/url-to-pdf

  2. Data formats

    11 endpoints

    JSON to and from XML, YAML, CSV and TOML, CSV to and from XML, and markdown to HTML. Structured data in, structured data out.

    POST /v1/convert/json-to-xml

  3. Documents to PDF

    11 endpoints

    HTML, markdown, Word, Excel, PowerPoint, the OpenDocument family, Pages and Numbers, all rendered to PDF with the same request shape.

    POST /v1/convert/doc-to-pdf

  4. Image conversions

    22 endpoints

    JPEG, PNG, WebP, HEIC and SVG in any combination, plus PDF to JPEG and a quality-aware compressor.

    POST /v1/convert/heic-to-webp

  5. Web intelligence

    6 endpoints

    perceive, discover, lookup, distill, ingest and watch. Render a page, map a site, resolve an entity, pull structured fields, build embeddable passages, and get told when a page changes.

    POST /v2/perceive

Errors come back as JSON with a detail field: 401 for a missing or invalid key, 402 when the monthly limit is reached, 403 for a domain or endpoint your key cannot use, and 413 for a file above your plan size limit.

Browse every endpoint
In practice

A request and a response.

Every endpoint follows the same shape. Send a key, get a presigned download link and the metadata that goes with it.

curl -X POST https://api.enconvert.com/v1/convert/url-to-pdf \  -H "X-API-Key: sk_your_private_key" \  -H "Content-Type: application/json" \  -d '{"url": "https://example.com"}'{  "presigned_url": "https://econverter.nyc3.cdn.digitaloceanspaces.com/...",  "object_key": "live/files/12345/url-to-pdf/example_20250202_120530123.pdf",  "filename": "example_20250202_120530123.pdf",  "file_size": 45678,  "conversion_time_seconds": 3.21}
Built on this

One API, four ways in.

REST is the foundation. Every other surface is a thinner way to reach the same endpoints with the same key.

Node.js SDK

Typed methods, streaming downloads, automatic recovery from a timed-out job, and a real error hierarchy instead of status-code branching. Zero runtime dependencies, ESM and CJS.

View on npm

Command-line tool

The whole API as one terminal command, for shells, scripts and CI jobs where an HTTP client is more ceremony than the task deserves.

See the CLI

n8n node

Convert, scrape and crawl inside a workflow without writing a request or handling a job poll yourself.

See the n8n node

MCP server

The same endpoints exposed as tools your agent can call directly, for Claude, Cursor and Windsurf.

See the MCP server

Questions about the API

https://api.enconvert.com. Every v1 and v2 endpoint hangs off that one base URL, so there is nothing regional or per-tenant to configure.
For server-to-server calls, send a private key that starts with sk_ in the X-API-Key header. For browser calls, exchange a public key that starts with pk_ for a short-lived JWT at POST /v1/auth/token and send it as Authorization: Bearer. Public keys only work from the domains you whitelist in the dashboard.
V1 is the 49 conversion endpoints: files and web pages in, converted files out. V2 is six web intelligence endpoints (perceive, discover, lookup, distill, ingest and watch) that render, search, extract and monitor live pages. They use the same keys and the same domain allowlist, and are metered on separate counters.
Both, depending on the endpoint. The five web page endpoints take a JSON body containing the URL. The data format, document and image endpoints take a multipart/form-data file upload.
The API answers 402 with a detail field naming the used and allowed counts. A batch that would push you past the remaining allowance is rejected upfront rather than partially processed, so you are never charged for a half-finished run.
Yes, @enconvert/node-sdk for Node.js and TypeScript. It calls the same public endpoints with zero runtime dependencies and ships both ESM and CJS builds, so SDK calls and raw HTTP calls mix freely in one codebase.

Start with one request.

The quickstart walks through your first conversion in three steps, with cURL, Python and JavaScript examples.

Read the quickstartGet an API key