iLovePDF integrations and automation

The iLovePDF developer API, sold as iLoveAPI, exposes the same tools as the website: compress, merge, split, convert Office files to PDF, PDF to JPG, images to PDF, page numbers, watermarks, rotation, repair, PDF/A, OCR, protect and unlock. The work is useful when documents arrive in a steady stream and someone currently drags each file through the browser by hand: scanned invoices that need OCR before filing, contract bundles that must become one PDF, or exports too large for an email attachment.

Every job follows the same four calls: start a task for a named tool, upload one or more files to it, process with the tool options, then download the result. Authentication uses the public and secret keys of a developer project. Keep that sequence in mind when writing a brief: a merge needs every file uploaded to the same task before processing, and the file order you supply is the page order you get back. iLoveAPI also caps how many tasks can be open at once, so a large batch should process each task before opening the next.

Usage is counted against the file allowance of your developer project, so check the iLoveAPI pricing page before planning a high-volume job. A sensible brief names the source folder or mailbox, the tool and its settings (compression level, OCR language, watermark text), and the destination. Keep the original file alongside the processed copy until you have checked a few outputs; a heavy compression level can make small text in a scan hard to read.

The signature product is a separate part of the same API with its own requests for creating signature jobs and tracking signer status. Treat it as its own design: who signs, in which order, and where the signed file should land. Because processing happens on iLovePDF servers, files you would not upload to a third party should not go through this route at all.