API overview
Converterer exposes two APIs under one account: file conversion and website capture. Both share auth, status lifecycle, and webhooks.
The Converterer API does two things:
- File conversion, upload a file and get it back in another format. Images, video, PDF, and office documents. See File conversion.
- Website to PDF, point at a URL and get a PDF. Async (queued and stored) or synchronous (streamed back in the response). See Website capture.
Both surfaces share the same auth, status lifecycle, and webhook delivery model.
Base URLs
| Host | What it serves |
|---|---|
https://api.converterer.com | File conversions (/convert) and async URL → PDF (/jobs) |
https://download.converterer.com | URL → PDF only, synchronously: PDF bytes streamed in the response |
The PDF generated by the synchronous endpoint is also uploaded to your destination’s storage at the configured file_name (or {id}.pdf by default), so you can retrieve it from your bucket later if you want.
Defaults
- Auth: HTTP Basic. Your API key is the username, the password is blank.
- Content type for uploads:
multipart/form-datafor file conversions; form-encoded or JSON for website capture. - Response type: JSON, except the synchronous download endpoint which returns the PDF bytes.
- Rate limit: 600 requests per minute, per account.
Where to start
- New here? Read the quick start for a working PNG → JPG example you can run in 30 seconds.
- Need to wire it into a backend? See authentication and then the endpoint you need: file conversion or website capture.
- Adding event-driven delivery? See webhooks.
- Debugging a failure? See errors and the status lifecycle.