What is a Webhook?
A webhook is an HTTP request sent by one system to notify another that an event occurred. Reliable implementations verify signatures, tolerate retries, and process duplicate deliveries idempotently.
How Webhooks work
A webhook producer serializes an event and sends it to a consumer-controlled HTTP endpoint, decoupling asynchronous state changes from polling. Delivery is normally at least once rather than exactly once, because a lost response leaves the sender unable to know whether processing succeeded. The receiver therefore authenticates the original request, records an event identity, acknowledges promptly, and moves expensive media or business work to a durable queue.
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
- 1Signature verification often covers the exact request bytes plus a timestamp. Parsing and reserializing the body first can change those bytes and cause valid requests to fail verification.
- 2Returning a success response only after lengthy downstream work increases timeouts and retries; persisting the event before acknowledging allows processing to continue asynchronously.
- 3Retries can duplicate or reorder events, so the event identifier and current resource version are safer guards for side effects than assuming each endpoint call is unique.
When Webhooks matter
Webhooks can continue application logic when asynchronous media processing completes or fails. Consumers must authenticate requests and avoid repeating side effects when the sender retries an event.
- 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 Webhooks.
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 Webhooks
When Webhooks 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.