Relay and forward files between HTTP endpoints

Receive files via HTTP and forward them to another HTTP endpoint automatically. DocEvent Channels buffers, retries, and reliably delivers every file — decoupling your upload endpoint from downstream processing.
From
HTTP Upload
To
HTTP Webhook
Get started for free — our basic plan is free forever.

How HTTP Upload to HTTP Webhook routing works

HTTP Upload
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
DocEvent Channel
HTTP Webhook
Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.
1

File arrives via HTTP Upload

REST endpoint accepts multipart/form-data file uploads with optional authentication headers.
2

Channel routes it

DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3

Delivered to HTTP Webhook

Multipart POST with configurable headers. Automatic retry on failure. Supports TLS.

Common use cases

Real workflows that teams automate with a HTTP Upload HTTP Webhook channel.
  • Fan out uploaded files to multiple downstream HTTP services
  • Forward files from one API endpoint to another reliably
  • Buffer and retry HTTP file deliveries with guaranteed delivery
  • Decouple file upload from downstream processing via HTTP relay

Technical details

Source:
HTTP Upload
REST endpoint accepts multipart/form-data file uploads with optional authentication headers.
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
Destination:
HTTP Webhook
Multipart POST with configurable headers. Automatic retry on failure. Supports TLS.
Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.
Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages

You focus on integration,
we'll focus on delivery.

Copyright © 2018-2026 DocEvent Pty Ltd, ACN 632 307 781