What is an Auth Key?
An Auth Key is the public identifier for a Transloadit account and functions similarly to a username in automated requests. It identifies the account but does not independently prove authorization.
How Auth Keys work
The Auth Key selects the Transloadit account under which an API operation is evaluated. It is an identifier included in request authentication material, while proof of authorization comes from a signature derived with private credentials. This public-versus-secret distinction lets clients reference the account without embedding the signing secret. Integration logs may retain the key for diagnosis, but authorization decisions must never rely on possession of it alone.
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
- 1An Auth Key can be sent with client-visible request data because it identifies an account; exposing the corresponding Auth Secret would instead permit unauthorized signing.
- 2Changing or mistyping the key directs verification toward the wrong account and causes authentication to fail even when the request was signed with a valid secret elsewhere.
- 3Access controls should distinguish account identification from request integrity: the key supplies the former, while the computed signature and its parameters supply the latter.
When Auth Keys matter
Include the Auth Key when an integration must associate an automated request with the correct Transloadit account. Because it is public, pair it with the required signature rather than treating it as a secret.
- 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 Auth Keys.
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 Auth Keys
When Auth Keys are 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.