PDF API for developers

Automate PDF work from your own apps with a simple HTTPS API. Send a file, get the result back in the same response – nothing is stored.

Quick start

curl -X POST https://dpdfconverter.com/api/v1/merge \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -F "files=@first.pdf" -F "files=@second.pdf" \
  -o merged.pdf

Create API keys on your account page. Keys are shown once and stored only as a hash.

Endpoints

EndpointInputParametersReturns
POST /api/v1/merge2+ files–PDF
POST /api/v1/splitfileranges e.g. 1-3,4-ZIP of PDFs
POST /api/v1/rotatefileangle 90|180|270, pagesPDF
POST /api/v1/compressfilelevel screen|ebook|printer|losslessPDF
POST /api/v1/grayscalefile–PDF (vector-preserving grayscale)
POST /api/v1/pdfafile–PDF/A-2b (issues reported in X-PDFA-Problems)
POST /api/v1/protectfilepasswordPDF (AES-256)
POST /api/v1/unlockfilepasswordPDF
POST /api/v1/watermarkfiletext, opacityPDF
POST /api/v1/office-to-pdffile .docx/.xlsx/.pptx/.odt…–PDF (LibreOffice)
POST /api/v1/pdf-to-textfile–JSON {pages:[{page,text}]}
POST /api/v1/ocrfile PDFlang e.g. eng, deuSearchable PDF
POST /api/v1/infofile–JSON metadata & page sizes

Limits and errors

Data handling

Each request is processed in a private temporary folder that is deleted when the response is sent. A background sweeper removes anything left behind after 15 minutes (for example after a crash). We log the endpoint, status, size and duration for billing and abuse prevention – never file contents.