What is the Transloadit REST API?
The Transloadit REST API is an HTTP(S) interface for initiating and managing encoding jobs programmatically. It can be called from any compatible language or platform, directly or through a Transloadit SDK.
How the Transloadit REST API works
An HTTP client creates an Assembly by submitting structured instructions and authentication data to a service endpoint, then reads the returned Assembly status and identifiers. The interface exposes resources through conventional requests and representations rather than requiring a language-specific runtime. Processing is asynchronous, so callers often combine the creation response with polling or notifications. It belongs at the boundary between application code and Transloadit’s media-processing infrastructure.
A client authenticates and submits files or references together with workflow instructions. The platform validates the request, schedules dependent operations, records state transitions, and exposes results through a response, polling endpoint, or notification.
Platform concepts become reliable only when their lifecycle is explicit. Authentication, idempotency, retries, timeouts, observability, quotas, and terminal states should be designed together rather than added after failures occur.
Key facts
- 1Direct REST integration leaves retry policy, timeouts, response validation, and multipart construction under application control; an SDK can encapsulate many of those details.
- 2Assembly creation can include uploaded files and JSON instructions in one multipart request, while imported inputs can be referenced by processing steps instead.
- 3An accepted HTTP request does not by itself mean every media step succeeded; clients must inspect Assembly and result states before treating outputs as complete.
When the Transloadit REST API matters
Use the REST API when an application needs direct control over request construction or lacks a suitable SDK. Requests must handle authentication, serialization, network errors, and API responses correctly.
- Running repeatable upload, import, processing, AI, storage, and notification pipelines.
- Tracking long-running media work independently from an application request.
- Applying credentials, quotas, retries, and error policies consistently across integrations.
Working with platform at scale
Guidance that holds across every platform term in this glossary, not just the Transloadit REST API.
What you gain
- Reusable workflows separate application intent from processing infrastructure.
- Stable job identifiers and lifecycle events improve observability and recovery.
- Managed queues and workers let products scale without embedding every media tool.
What it costs
- Synchronous responses are simple but keep connections open while long work executes.
- Aggressive retries improve recovery from transient faults but can duplicate work or overload a dependency.
- Higher concurrency reduces queue time until resource contention or a downstream limit becomes the bottleneck.
Answer these before production
- 1Define authentication, authorization, idempotency, retries, and terminal error behavior.
- 2Observe queue time, execution time, callbacks, and partial results with stable identifiers.
- 3Exercise malformed, duplicate, interrupted, and unauthorized requests before launch.
How Transloadit helps with the Transloadit REST API
When the Transloadit REST API is relevant to your workflow, you can hand the surrounding platform work to Transloadit instead of maintaining the processing stack yourself. Transloadit models file workflows as reusable Assembly Instructions. Upload, import, processing, AI, storage, delivery, status updates, and error handling can be composed without operating the underlying media tools yourself.
Support for a specific codec, container, parameter, or combination can vary by Robot and processing stack. Check the linked documentation for the exact inputs and outputs available for your use case.