Route HTTP uploads into an on-premise folder
Accept file uploads via HTTP POST and have them appear in a folder on your own server. DocEvent queues each upload and the Filerouter agent pulls it down over outbound HTTPS — no exposed endpoints on your network, full audit trail included.
From
HTTP Upload
To
Filerouter (on-premise)
Receive endpoints
Amazon S3
HTTP Upload
Email
FTP Pull
SFTP Pull
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
FTP / FTPS
SFTP
Webhook
Email
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How HTTP Upload to Filerouter (on-premise) routing works
Source
HTTP Upload
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
DocEvent Channel
routes · retries · logs
Destination
Filerouter
Files are delivered into a local folder on your own server by the Filerouter agent.
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 Filerouter (on-premise)
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Common use cases
Real workflows that teams automate with a HTTP Upload → Filerouter (on-premise) channel.
- Accept files from web apps or APIs and land them on an internal server
- Let customers POST files over HTTPS that arrive in your local processing folder
- Bridge cloud upload endpoints to software that only reads local directories
- Collect field-device HTTP uploads into one on-premise ingest folder
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the HTTP Upload or Filerouter (on-premise) side under their own account, with their own credentials. Learn how shared channels work.
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:
Filerouter
The agent connects out to DocEvent over HTTPS — no inbound ports to open — and writes each delivered file into the folder you choose, acknowledging every file so restarts and dropped connections never lose one or deliver it twice.
Files are delivered into a local folder on your own server by the Filerouter agent.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
Related channel integrations
Other destinations from HTTP Upload
Other sources to Filerouter (on-premise)
- Amazon S3 → Filerouter (on-premise)
- Email → Filerouter (on-premise)
- Filerouter (on-premise) → Filerouter (on-premise)
- FTP Pull → Filerouter (on-premise)
- SFTP Pull → Filerouter (on-premise)
- S3 Compatible (pull) → Filerouter (on-premise)
- GCS Blob Pull → Filerouter (on-premise)
- Azure Blob Pull → Filerouter (on-premise)
- Azure Data Lake Pull → Filerouter (on-premise)
- Azure Files Pull → Filerouter (on-premise)
- DocEvent Agent (on-prem) → Filerouter (on-premise)