ConvertAPI

Name: ConvertAPI API
Brand: ConvertAPI
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey, bearer4 EndpointsREST

For Agents

Convert a file from one format to another with a single POST call to ConvertAPI. Agents authenticate with an API secret query parameter or bearer token.

Connect the ConvertAPI to your agent

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

Convert a file between any supported source and destination format via POST /convert/{sourceFormat}/to/{destinationFormat}

Upload a file with POST /upload to use as input on subsequent conversions

Discover supported source and target formats via GET /info

Inspect account usage and remaining quota via GET /user

GET STARTED

Start building with ConvertAPI API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for ConvertAPI, keeping it validated and agent-ready. ConvertAPI converts files between document, image, and web formats through a single POST /convert/{sourceFormat}/to/{destinationFormat} endpoint that returns the converted output synchronously. The API also supports uploading files for later conversion, listing available converters, and inspecting account usage. Authentication is either an API secret in the query string or a bearer token in the Authorization header.

Use Cases

Patterns agents use ConvertAPI API for, with concrete tasks.

★ Synchronous Document-to-PDF Conversion

Convert documents — DOCX, XLSX, HTML, Markdown — to PDF on demand by POSTing the source file to /convert/{sourceFormat}/to/pdf. The response carries the converted file directly, so there is no polling step. Suited to applications that need instant export-as-PDF behaviour for user-facing documents.

POST a DOCX file to /convert/docx/to/pdf and stream the resulting PDF back to the user

Format Discovery and Capability Reporting

Build user interfaces that show only the conversions actually supported by ConvertAPI by reading GET /info at startup. The endpoint returns the full source-to-destination matrix, so dropdowns and file pickers stay in sync with the live capability list. Useful for SaaS dashboards exposing conversion options to end users.

Call GET /info and return the full list of formats that can be converted to PDF

Two-Step Upload-Then-Convert Workflow

Upload a large file once via POST /upload, then run multiple conversions against the same uploaded file by referencing its ID on the convert endpoint. This avoids re-transferring large source files when the same input needs PDF, PNG, and TXT outputs. Useful for archival and indexing pipelines that produce several derivative formats from each source.

Upload report.docx via POST /upload, then trigger conversions to PDF, PNG, and TXT against the returned upload ID

Agent-Driven File Conversion via Jentic

An AI agent converts user files end-to-end through Jentic without holding the API secret. The agent searches Jentic for 'convert a file', loads the schema, and executes POST /convert/{sourceFormat}/to/{destinationFormat} with the desired formats. Through Jentic the secret or bearer token is injected from the vault so authoring loops stay safe.

Search Jentic for 'convert a docx to pdf', load the ConvertAPI schema, then convert the user's uploaded DOCX and return the PDF URL

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for convertapi, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/convert/{sourceFormat}/to/{destinationFormat}

Convert a file between two formats

POST

/upload

Upload a file to reuse on later conversions

GET

/info

List all available converters

GET

/user

Get the authenticated user's account information

POST

/convert/{sourceFormat}/to/{destinationFormat}

Convert a file between two formats

POST

/upload

Upload a file to reuse on later conversions

GET

/info

List all available converters

GET

/user

Get the authenticated user's account information

Why though Jentic?

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

Credential isolation

ConvertAPI secrets and bearer tokens are stored encrypted in the Jentic vault. Agents receive scoped access at execution time, and the credential is injected as either the Secret query parameter or Authorization header — raw secrets never enter the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g., 'convert a docx to pdf') and Jentic returns the matching POST /convert operation with its input schema, so the agent can build the request without browsing docs.

Time to first call

Direct ConvertAPI integration: a few hours for auth, multipart uploads, and error handling. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

CloudConvert API

File conversion across 200+ formats with an upload-then-task flow.

Choose CloudConvert when broader format coverage or queued task semantics are needed; pick ConvertAPI for a one-shot synchronous call.

Alternative

Conversion Tools API

File conversion with sandbox testing and 100GB streaming uploads.

Pick Conversion Tools when very large files (>1GB) or sandbox testing is required; pick ConvertAPI for fast small-file conversions.

Complementary

Filestack API

File ingestion, transformation, and CDN delivery that pairs with conversion services.

Pair with ConvertAPI when files arrive via Filestack uploaders and need format conversion before downstream storage.

FAQs

Specific to using ConvertAPI API through Jentic.

Why is there no official OpenAPI spec for ConvertAPI?

ConvertAPI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ConvertAPI 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 ConvertAPI use?

Two schemes are supported: the Secret query parameter (apiKey) for the simplest direct use, and HTTP Bearer authentication via the Authorization header. Through Jentic the secret or bearer token is stored in the vault and injected at execution time so it never enters the agent's prompt.

How do I convert a DOCX file to PDF with ConvertAPI?

POST your DOCX file to /convert/docx/to/pdf with multipart form data and the API returns the converted PDF synchronously. There is no separate task or polling step — the response body carries the result.

Which formats can ConvertAPI convert between?

Call GET /info to retrieve the live list of supported source and destination formats — documents, images, web pages, and more. The endpoint returns the matrix so applications can stay in sync as ConvertAPI adds converters.

How do I check my ConvertAPI account quota?

Call GET /user with your bearer token or Secret. The response includes account information and the remaining quota for the authenticated user.

How do I run a conversion through Jentic?

Run jentic search for 'convert a file', load the POST /convert/{sourceFormat}/to/{destinationFormat} operation, then execute it with the source format, destination format, and file. Jentic injects the credential from the vault and returns the converted file as a structured response.

Can I upload a file once and convert it to multiple formats?

Yes. POST /upload returns an ID for the uploaded file, which can be referenced on subsequent /convert calls to produce different output formats without re-uploading the source. This is efficient for derivative-format pipelines.