canonical: https://jentic.com/apis/ilovepdf.com/main

# iLovePDF API

iLovePDF is a PDF and image processing API with electronic signature support. It authenticates by exchanging a project public key for a token, then runs tasks that convert, merge, compress, and otherwise transform PDF and image files across processing servers. A signature workflow lets applications create signature requests, list them, and download signed documents.

## For AI agents

Lets an AI agent convert, merge, and compress PDF and image files through iLovePDF and manage electronic signature requests from creation to signed download.

## Scope

Does not handle document storage, text search, or accounting. Use it for PDF and image processing and electronic signatures only.

## Capabilities

- Convert, merge, and compress PDF and image files
- Start a processing task and upload files to it
- Process uploaded files and download the result
- Create electronic signature requests for documents
- List signature requests and download signed files
- Exchange a project public key for a session token

## Use cases

### Document conversion and assembly

An application needs to turn user uploads into a single clean PDF. iLovePDF starts a processing task, accepts the uploaded files, runs the chosen tool such as convert or merge, and returns a downloadable result, so a product can assemble documents without shipping its own conversion stack. Each task runs on the processing server the API assigns.

Example prompt: Start a merge task, upload the source PDFs, process them, and download the combined file

### Electronic signature workflow

A team needs signatures on contracts without a separate signing tool. iLovePDF creates a signature request for a document, lists outstanding requests, and returns the signed file once complete, letting an application drive the signing flow programmatically. Requester views expose the status of a pending request.

Example prompt: Create a signature request for a contract and download the signed document when it completes

### AI agent document processing

An AI agent handling document tasks can convert, combine, and route files for signature end to end. The agent authenticates, runs the processing task, and either returns the output or opens a signature request, keeping file operations behind the tools the operator has allowed. The token stays managed outside the agent's context.

Example prompt: Given an uploaded file, run a compression task and return the smaller PDF to the caller

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/auth` | Request a signed token using your public key |
| GET | `/start/{tool}/{region}` | Start a processing task for a tool |
| POST | `/{server}/v1/upload` | Upload a file to a processing task |
| POST | `/{server}/v1/process` | Process the uploaded files |
| GET | `/{server}/v1/download/{task}` | Download the processed output |
| POST | `/{server}/v1/signature` | Create a signature request |

## Key resources

- **Authentication** — Exchange a project public key for a session token
- **Processing** — Start tasks, upload files, process them, and download results
- **Signature** — Create signature requests, list them, and download signed files

## Why Jentic

- **Setup:** Wiring iLovePDF by hand means exchanging a project public key for a token, tracking the processing server assigned to each task, and threading the token through upload, process, and download calls. Install Jentic One once, import the API from the Jentic API Directory, and store the credential once for your agent to reuse.
- **Permission scoping:** Scope your agent to the operations it needs, such as conversion tasks or signature requests, and withhold the rest. You decide which operations are callable, so an agent can process files without gaining signing rights.
- **Credential handling:** Your iLovePDF token is stored once, encrypted, by your own Jentic One instance and injected only at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents find iLovePDF through Jentic's intent search: a query such as 'convert and merge PDF files' matches the processing operations, which the agent then calls with your stored credential.

## Related APIs

- **PDF.co** — PDF and document processing with conversion, parsing, and generation
- **PandaDoc** — Document generation and electronic signature workflows
- **Cloudinary** — Media upload, storage, and image transformation

## FAQ

### What can an AI agent do with the iLovePDF API?

An agent can start processing tasks to convert, merge, and compress PDF and image files, download the results, and drive an electronic signature workflow from request to signed download. It covers document processing and signing.

### How does the iLovePDF API authenticate?

iLovePDF authenticates with a bearer token that you obtain by exchanging your project public key. Jentic injects the token at execution time so it stays out of the agent's context.

### Can I limit what my agent is allowed to do with the iLovePDF API?

Yes. Your Jentic One instance controls which operations an agent may call, so you can allow document conversion tasks while withholding the signature operations, or the reverse. Nothing outside the operations you allow is reachable.

### What file operations does iLovePDF support?

It converts, merges, compresses, and transforms PDF and image files through processing tasks, and adds an electronic signature workflow for sending documents and downloading signed copies.

### How do I connect the iLovePDF API to my AI agent with Jentic?

Install Jentic One with its setup script, import the iLovePDF API from the Jentic API Directory, and store your credential once. Your agent can then call the processing and signature operations you allow.