CloudConvert API

Name: CloudConvert API API
Brand: CloudConvert API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData Transformationbearer, oauth213 EndpointsREST

For Agents

Convert files between hundreds of formats and manage webhooks on CloudConvert using bearer tokens or OAuth2.

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

Cancel or retry an in-flight task at /tasks/{taskId}/cancel and /tasks/{taskId}/retry

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

List, register, and delete webhooks for job and task lifecycle events

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 an online file conversion service supporting nearly all audio, video, document, ebook, archive, image, spreadsheet, and presentation formats. This variant of the spec adds OAuth2 user-delegated auth alongside personal bearer tokens and exposes a sandbox base URL for safe testing. Conversions are modelled as Jobs containing import, convert, and export Tasks, with webhook callbacks for async completion.

Use Cases

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

★ User-Delegated File Conversion

Build a SaaS feature that converts files inside a customer's own CloudConvert account using OAuth2. The user authorises the app, the access token is stored, and the app calls /jobs on their behalf. Job credits and storage are billed to the user, not the app developer.

Complete the OAuth2 flow for the user, then POST /jobs with the import, convert, and export tasks under their token.

Resilient Conversion Pipeline

Run conversions with retry and cancellation for production workloads. Use /tasks/{taskId}/retry when a transient failure occurs and /tasks/{taskId}/cancel to abort jobs whose source is no longer needed. Webhooks at /webhooks notify the orchestrator when each task transitions state.

On task.failed webhook, call POST /tasks/{taskId}/retry; on user cancellation, call POST /tasks/{taskId}/cancel.

Sandbox Testing Before Production

Use the CloudConvert sandbox base URL (https://sandbox.api.cloudconvert.com/v2) to validate task chains without consuming production credits or producing watermark-free output. Once the workflow is correct, swap the base URL to api.cloudconvert.com/v2.

Point the client at https://sandbox.api.cloudconvert.com/v2, POST /jobs to validate the task chain, then redeploy against the production base URL.

AI Agent File Conversion via OAuth

Let a Jentic-powered agent convert a file inside the end user's CloudConvert account. The agent searches Jentic for 'convert a file', loads the createJob operation, and executes against the OAuth-issued token rather than a global app token. Jentic isolates each user's credential.

Search Jentic for 'convert file with CloudConvert', load createJob, and execute with the user's OAuth access token and chosen output_format.

Key Endpoints

13 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/{jobId}

Get job status and tasks

GET

/jobs/{jobId}/wait

Wait for job completion

GET

/tasks/{taskId}

Get a single task

POST

/tasks/{taskId}/cancel

Cancel a running task

POST

/tasks/{taskId}/retry

Retry a failed task

POST

/webhooks

GET

/users/me/webhooks

List webhooks for the authenticated user

POST

/jobs

Create a conversion job with chained tasks

GET

/jobs/{jobId}

Get job status and tasks

GET

/jobs/{jobId}/wait

Wait for job completion

GET

/tasks/{taskId}

Get a single task

POST

/tasks/{taskId}/cancel

Cancel a running task

POST

Why though Jentic?

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

Credential isolation

Personal bearer tokens and OAuth2 access tokens are stored encrypted in the Jentic vault. Agents receive scoped access tokens — raw CloudConvert credentials never enter the agent context, which is critical when an OAuth token represents an end user.

Intent-based discovery

Agents search Jentic by intent (for example 'convert a file', 'cancel a conversion task') and Jentic returns the matching CloudConvert operation with its input schema so the agent calls the right /jobs or /tasks endpoint.

Time to first call

Direct CloudConvert integration: 2-3 days to implement OAuth2, webhook handling, and task retry. 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 bearer-only auth and operations discovery.

Pick the cloudconvert.com variant when the agent needs the /operations and /import endpoints rather than the OAuth and retry-focused surface here.

Alternative

Filestack

File upload, transformation, and conversion in a single managed product.

Use Filestack when the agent also needs upload widgets, image transforms, or virus scanning alongside conversion.

Complementary

Cloudinary Upload API

Media CDN with format conversion at delivery time.

Pair with Cloudinary when converted images and videos 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 spec defines two schemes: a personal bearer token for first-party apps and an OAuth2 flow for user-delegated access. Both are passed as Authorization: Bearer <token>. Through Jentic, tokens are stored encrypted and injected at execution time.

Can I retry a failed CloudConvert task?

Yes. POST /tasks/{taskId}/retry re-runs a failed task with the same parameters and produces a new task ID. This is the standard recovery path for transient errors such as upstream import failures.

How do I cancel a running CloudConvert job?

Cancel each pending task with POST /tasks/{taskId}/cancel. Tasks that have already completed cannot be cancelled, but pending and running tasks transition to a cancelled state and stop consuming credits.

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 source URL and output_format. Jentic handles the bearer or OAuth2 token from the stored credential.

Is there a sandbox environment for CloudConvert?

Yes. The spec lists https://sandbox.api.cloudconvert.com/v2 as a server. Use it to validate task chains and webhook flows before pointing the client at the production https://api.cloudconvert.com/v2 base URL.