SDKs
Official client libraries for the Enconvert API. Each SDK exposes the full conversion surface as type-safe methods, handles authentication, and includes built-in recovery for long-running conversions that exceed reverse-proxy timeouts.
Available SDKs
| Language | Package | Status | Source |
|---|---|---|---|
| Node.js / TypeScript | @enconvert/node-sdk |
Stable | enconvert/enconvert-js |
Why use an SDK?
Calling the REST API directly works, but the SDKs add several conveniences on top:
- Type-safe options. Editor autocomplete for every parameter, every endpoint.
- Automatic timeout recovery. Long conversions (heavy URL-to-PDF, large documents) sometimes exceed the 60-second reverse-proxy timeout. The SDKs generate a client-side
job_id, send it with the request, and transparently fall back to pollingGET /v1/convert/status/{job_id}if the original request returns 5xx — no extra code on your side. - Streaming downloads. When you pass
saveTo, the SDK streams the response straight to disk with backpressure — constant memory regardless of file size. - Consistent errors. A small hierarchy (
AuthenticationError,RateLimitError,APIError) lets youtry/catchwithout parsing status codes.
Same wire format. The SDK hits the same public REST endpoints documented in the rest of this site. You can mix SDK calls and raw HTTP calls against the same project.
Get started
- Node.js / TypeScript — Node 18+, zero runtime dependencies, dual ESM + CJS, full type definitions.
Get an API Key
The SDK needs a private API key (sk_live_...). Generate one from the dashboard and pass it to the constructor — never hardcode it in client-side code.