CloudConvert API

Name: CloudConvert API
Brand: CloudConvert API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData Transformationbearer14 EndpointsREST

For Agents

Convert files between hundreds of formats by composing import, convert, and export tasks into a CloudConvert job using a bearer token.

Install Jentic One Beta

Connect the CloudConvert API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CloudConvert 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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: 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

Step 2: 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 CloudConvert API.

Create conversion jobs that chain import, convert, and export tasks

Wait synchronously for a job to finish via /jobs/{id}/wait

Upload source files directly through /import/upload or pull from a URL

GET STARTED

Start building with CloudConvert API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use CloudConvert API for, with concrete tasks.

★ PDF Document Conversion

Convert PDFs into editable formats like DOCX, XLSX, or images for downstream processing. Build a Job with an import-url task, a convert task targeting the destination format, and an export-url task to retrieve the result. Polling /jobs/{id}/wait blocks until the chain completes, typically in seconds for single-page documents.

POST /jobs with tasks=[import-url, convert(input_format=pdf, output_format=docx), export-url], then GET /jobs/{id}/wait and return the export URL.

Video and Audio Transcoding

Re-encode media files between codecs and containers. CloudConvert supports MP4, MOV, WebM, MP3, WAV, FLAC, and many more formats. A single job can chain a transcode plus a thumbnail extraction so a content pipeline gets both deliverables in one call.

POST /jobs with a convert task input_format=mp4, output_format=webm, video_codec=vp9 and a thumbnail task, then GET /jobs/{id}/wait.

Bulk Office Document Processing

Process spreadsheets, presentations, and Word documents in batch - for example converting an upload folder of XLSX files to PDF for archival. Combine /import/upload, /jobs, and webhooks so the application is notified asynchronously when each job completes rather than polling.

POST /import/upload for each file, POST /jobs to convert to pdf, register a webhook via POST /webhooks, and listen for job.finished events.

AI Agent File Conversion

Let a Jentic-powered agent convert user-uploaded files on demand. The agent searches Jentic for 'convert a file format', loads the CloudConvert createJob operation, and executes a job with the source URL and target format. The bearer token stays in your Jentic One instance.

Search Jentic for 'convert a PDF to DOCX', load the CloudConvert createJob operation, and execute it with the source URL and output_format=docx.

Key Endpoints

14 endpoints — jentic publishes the only available openapi specification for cloudconvert api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/jobs

Create a conversion job with chained tasks

GET

/jobs/{id}

Get job status and tasks

GET

/jobs/{id}/wait

Wait synchronously for job completion

POST

/import/upload

Create an upload task for a source file

POST

/import/url

Import a file from a public URL

GET

/operations

List supported conversion operations

POST

/webhooks

GET

/users/me

Get authenticated user and credit balance

POST

/jobs

Create a conversion job with chained tasks

GET

/jobs/{id}

Get job status and tasks

GET

/jobs/{id}/wait

Wait synchronously for job completion

POST

/import/upload

Create an upload task for a source file

POST

/import/url

Import a file from a public URL

Why Jentic?

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

Credential isolation

Your CloudConvert token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'convert a PDF to DOCX' or 'transcode a video', and Jentic returns the create-job operation with its task schema so the agent composes the correct task chain without browsing the reference docs.

Time to first call

FAQs

Specific to using CloudConvert API through Jentic.

Why is there no official OpenAPI spec for CloudConvert API?

CloudConvert does not publish a structured OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CloudConvert API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the CloudConvert API use?

The API uses bearer token authentication. Generate an API token in the CloudConvert dashboard, scope it to the operations you need, and pass it as Authorization: Bearer <token>. Through Jentic, the token is stored encrypted and never enters the agent's context.

How do I convert a PDF to DOCX with the CloudConvert API?

Create a job at POST /jobs with three tasks: an import task (import-url or import-upload), a convert task with input_format=pdf and output_format=docx, and an export-url task. Then call GET /jobs/{id}/wait to receive the export URL when it completes.

Can the CloudConvert API notify my app when a job finishes?

Yes. Register a webhook via POST /webhooks subscribing to job.finished or task.finished events. CloudConvert posts the event payload to your URL so you avoid polling /jobs/{id}.

How do I run a CloudConvert job through Jentic?

Run jentic search 'convert a file with CloudConvert', load the createJob operation, and execute with the import source and target format. Jentic handles the bearer token from the stored credential.

Does CloudConvert have regional endpoints for data residency?

Yes. The spec lists EU (https://eu-central.api.cloudconvert.com) and US (https://us-east.api.cloudconvert.com) base URLs in addition to the global https://api.cloudconvert.com/v2. Pick the regional host to keep file processing inside a specific region.

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

Yes. Because you run Jentic One yourself, you decide exactly which CloudConvert operations your agent may call, so you can grant creating a job, importing a file, and waiting on a result while withholding anything else. CloudConvert's job and operation ids are ephemeral rather than fixed resources, so scoping is done at the operation level rather than by pinning ids in the URL path. Operations such as registering a webhook are only in reach if you explicitly include them, and your bearer token is injected at execution time without entering the agent's context.

CloudConvert API

Connect the CloudConvert API to your agent

Capabilities

Start building with CloudConvert API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs