Introduction
Introduction
The BastosConvert API is the same engine that powers the site, exposed as a simple REST API. Convert PDFs, images, audio and video in the cloud — files are transferred over an encrypted connection and auto-deleted right after conversion, never stored or shared.
Base URL
https://bastosconvert.com/api/v1All endpoints live under this prefix. Requests and error bodies are JSON
(application/json); file inputs are sent as multipart/form-data.
Two ways to convert
The API has two complementary flows:
| Flow | Endpoints | Shape | Auth |
|---|---|---|---|
| Instant tools | /pdf/*, /media/* | Upload multipart/form-data, get the converted file back in the response | Public (rate-limited per IP) |
| Conversion jobs | /convert, /conversion_jobs | Enqueue a job, then poll for the result | API key |
- Reach for an instant tool when you have one file and want the result synchronously (the common case — merge a PDF, convert an MP4).
- Reach for conversion jobs for the asynchronous pipeline (track history, longer-running work).
Conventions
- Versioning — the surface is versioned in the path (
/api/v1). Breaking changes ship under a new version. - Errors — every error is an RFC 7807
application/problem+jsondocument with a stablecode. - Request IDs — every response carries an
x-request-idheader; include it when you contact support. - Rate limits — see Rate limits.
Next steps
- Quickstart — your first conversion in one
curl. - Authentication — when and how to use an API key.
- Conversions & jobs — the asynchronous flow.