Developer API

The Azpy API lets you convert files programmatically with a simple, predictable HTTP interface. It shares the same engine as the website, so the conversion you test in the browser behaves identically through the API.

Endpoints

POST

/api/v1/convert/:slug

Convert an uploaded file. The :slug is the conversion id, e.g. docx-to-pdf.

GET

/api/v1/convert/:slug

Check whether a server conversion is available and its current limits.

GET

/api/v1/tools

List all supported conversions with their processing mode and accepted formats.

Example, convert DOCX to PDF

curl -X POST https://azpy.es/api/v1/convert/docx-to-pdf \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "file=@report.docx" \
  --output report.pdf

Response

200 OK
Content-Type: application/pdf
Content-Disposition: attachment; filename="report.pdf"

[PDF bytes]

Authentication

Requests are authenticated with an API key sent as a Bearer token. API keys are issued on the Business plan. Without a key, unauthenticated requests are limited and rate-limited per IP.

Limits

Business API keys benefit from higher file size limits and usage quotas per the plan. In-flight conversions are temporary and never stored; files are deleted immediately after conversion.