CloudConvert API

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

Quickstart

Get started with CloudConvert API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"convert a file with CloudConvert"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with CloudConvert API 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

List supported operations and target formats from /operations

Manage webhooks to receive job and task status callbacks

GET STARTED

Start building with CloudConvert API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for CloudConvert API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for CloudConvert API, keeping it validated and agent-ready. CloudConvert is a cloud-based file conversion service that handles documents, images, video, audio, ebooks, archives, spreadsheets, and presentations across hundreds of formats. The v2 API models work as Jobs composed of Tasks (import, convert, export) and exposes regional endpoints for EU and US data residency. Authentication uses bearer tokens with scoped permissions.

Use Cases

Patterns agents use CloudConvert API 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 the Jentic vault.

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 though Jentic?

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

Credential isolation

The CloudConvert bearer token is stored encrypted in the Jentic vault. Agents receive scoped access tokens — the raw API token never enters the agent's context or logs.

Intent-based discovery

Agents search Jentic by intent (for example 'convert a PDF to DOCX' or 'transcode a video') and Jentic returns the createJob operation with the task schema so the agent can compose the correct task chain.

Time to first call

Direct CloudConvert integration: 1-2 days to model jobs and tasks, register webhooks, and handle errors. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

CloudConvert API

Alternate import of the CloudConvert v2 spec with OAuth2 and sandbox server.

Pick this variant if the agent needs OAuth2 user-delegated auth or the sandbox base URL rather than a personal bearer token.

Alternative

Filestack

File upload, transformation, and conversion as a single managed service.

Choose Filestack when the workflow needs upload widgets and image transforms in addition to format conversion.

Complementary

Cloudinary Upload API

Image and video CDN with on-the-fly format conversion at delivery time.

Use Cloudinary alongside CloudConvert when the deliverable should be served from a CDN with URL-based transforms.

FAQs

Specific to using CloudConvert API 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 at https://app.jentic.com/sign-up.

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.