iLovePDF API

Name: iLovePDF API API
Brand: iLovePDF API
Availability: InStock

✓ Official Vendor SpecMediaImage Processingbearer9 EndpointsREST

For Agents

Run PDF and image processing tasks like merge, split, compress, convert, and electronic signature requests through iLovePDF's task-based pipeline.

Connect the iLovePDF API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the iLovePDF API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with iLovePDF API API.

Authenticate with project credentials and obtain a bearer token for subsequent calls

Start a processing task for a specific tool such as merge, split, or compress

Upload one or more files to the worker server assigned to a task

Run a configured task and download the resulting PDF or image bundle

GET STARTED

Start building with iLovePDF API API

Explore with Jentic

View OpenAPI Document

iLovePDF API exposes the PDF and image processing tools from iLoveAPI as a programmatic service. Developers authenticate, start a task for a tool such as merge, split, compress, or convert, upload files to the assigned worker server, run the process, and download the result. The API also covers electronic signature workflows so PDFs can be sent for signing and the signed copies pulled back. It targets SaaS apps that need PDF transformations or signature flows without bundling a local toolchain.

Use Cases

Patterns agents use iLovePDF API API for, with concrete tasks.

★ PDF Generation Pipeline for SaaS

Back-office and customer-facing apps frequently need to merge, compress, or convert PDFs before emailing or storing them. iLovePDF's task model fits this well: start a task for the chosen tool, upload the source files, run the task, and download the output. The four-call pattern keeps long-running jobs off the main app server.

POST /auth to get a token, GET /start/merge/{region}, POST /{server}/v1/upload for each PDF, POST /{server}/v1/process, then GET /{server}/v1/download/{task}.

Contract E-Signature Flow

Send sales or HR contracts for electronic signature without standing up a separate signing service. The signature endpoints accept signer details, route the document to each signer, and expose a download endpoint for the completed PDF. This works well for low-volume signing in apps that already use iLovePDF for document conversion.

POST /{server}/v1/signature with signer emails and the prepared PDF, then GET /{server}/v1/signature/{token}/download-signed once all parties have signed.

Bulk Document Compression

Archival systems and email gateways often need to shrink PDFs before storage or delivery. Looping the start, upload, process, and download steps over a folder of files lets a job worker apply the compress tool at scale without a local PDF library. Worker server assignment per task keeps throughput predictable.

For each PDF in a queue: GET /start/compress/{region}, upload, process, then download and store the compressed output.

Agent-Initiated Document Workflows

An AI assistant in an internal tool can accept a request like 'merge these three contracts and send the result for signature' and chain the iLovePDF operations behind one Jentic search. The agent does not need to know the task lifecycle - Jentic returns the right operations in order, with their input schemas, so the assistant can run the chain end to end.

Search Jentic for 'merge PDFs and send for signature', execute the merge chain, then execute the signature operation against the merged output.

Key Endpoints

9 endpoints — ilovepdf api exposes the pdf and image processing tools from iloveapi as a programmatic service.

METHOD

PATH

DESCRIPTION

POST

/auth

Authenticate and receive a bearer token

GET

/start/{tool}/{region}

Start a task for a tool and get the worker server

POST

/{server}/v1/upload

Upload a file to a started task

POST

/{server}/v1/process

Run the configured task

GET

/{server}/v1/download/{task}

Download the processed file bundle

POST

/{server}/v1/signature

Create an electronic signature request

GET

/{server}/v1/signature/{token}/download-signed

Download a signed PDF by token

POST

/auth

Authenticate and receive a bearer token

GET

/start/{tool}/{region}

Start a task for a tool and get the worker server

POST

/{server}/v1/upload

Upload a file to a started task

POST

/{server}/v1/process

Run the configured task

GET

/{server}/v1/download/{task}

Download the processed file bundle

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

iLovePDF project credentials are stored encrypted in the Jentic vault. The agent receives short-lived bearer tokens scoped to a single execution rather than the long-lived project secret.

Intent-based discovery

Agents search by intent (e.g., 'merge PDFs and download the result') and Jentic returns the start, upload, process, and download operations together with their schemas, so the multi-step task lifecycle is wired without docs lookup.

Time to first call

Direct iLovePDF integration: 1-2 days to wire the auth, task start, upload, process, download flow. Through Jentic: under 30 minutes - search, load, execute the chain.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

PDF.co

PDF.co offers a similar set of PDF transformation and extraction tools through a flat REST surface.

Choose PDF.co when the agent needs OCR, structured data extraction, or PDF parsing in addition to merge or compress.

Complementary

Cloudinary Upload API

Cloudinary handles image and asset hosting and transformation alongside PDF generation.

Choose Cloudinary when the agent needs CDN-backed delivery for the generated PDFs and images after iLovePDF processing.

Alternative

PandaDoc

PandaDoc is a fuller-featured contract and e-signature platform with templates and workflow.

Choose PandaDoc when the agent needs signed audit trails, document templates, and CRM integrations rather than per-task PDF tooling.

FAQs

Specific to using iLovePDF API API through Jentic.

What authentication does the iLovePDF API use?

The API uses bearer token authentication. Call POST /auth with project credentials to receive a token, then send Authorization: Bearer {token} on subsequent requests. Through Jentic the project key stays in the encrypted vault and the bearer flow is handled automatically.

Can I run an end-to-end PDF merge through this API?

Yes. Call /auth, then GET /start/merge/{region} to receive a worker server, POST each PDF to /{server}/v1/upload, POST /{server}/v1/process to execute the merge, and GET /{server}/v1/download/{task} to retrieve the merged file.

Does the API support electronic signatures on PDFs?

Yes. POST /{server}/v1/signature creates a signature request with signer details, GET /v1/signature/list returns the requests on your account, and GET /{server}/v1/signature/{token}/download-signed returns the signed PDF once complete.

How do I trigger a PDF compression through Jentic?

Run pip install jentic, search for 'compress a PDF with iLovePDF', then load and execute the start, upload, process, and download operations in order. Jentic chains the worker server URL across calls so the agent does not have to track it manually.

What are the rate limits for the iLovePDF API?

The OpenAPI spec does not list explicit rate limits. iLovePDF enforces per-plan quotas on tasks per month and concurrent worker usage; consult your project dashboard and back off on HTTP 429 responses.