HTTP UPLOAD IN. DOCEVENT AGENT (ON-PREM) OUT. NO SCRIPTS.
Route HTTP uploads into a folder on your own machine
Accept file uploads via HTTP POST and have them appear in a folder on your own machine. DocEvent queues each upload and the DocEvent Agent writes it locally — outbound TLS only, delivery folder picked from the web console, full audit trail.
From
HTTP Upload
To
DocEvent Agent (on-prem)
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Filespull
Servers & protocols
SFTP / FTPS Serverhosted · you push
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How HTTP Upload to DocEvent Agent (on-prem) routing works
Source
HTTP Upload
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
DocEvent Channel
routes · retries · logs
Destination
DocEvent Agent
Files are delivered into a local folder on your own machine by the DocEvent 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 DocEvent Agent (on-prem)
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Common use cases
Real workflows that teams automate with a HTTP Upload → DocEvent Agent (on-prem) channel.
- Accept files from web apps or APIs and land them on an internal machine
- Let customers POST files over HTTPS that arrive in your local processing folder
- Bridge cloud upload endpoints to software that 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 DocEvent Agent (on-prem) 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:
DocEvent Agent
The agent connects outbound over TLS — no inbound ports to open — and writes each delivered file into the folder you pick from the web console. Every file is acknowledged, so restarts and dropped connections never lose or duplicate one.
Files are delivered into a local folder on your own machine by the DocEvent 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 sources to DocEvent Agent (on-prem)
- Amazon S3 → DocEvent Agent (on-prem)
- SFTP / FTPS Server → DocEvent Agent (on-prem)
- Email → DocEvent Agent (on-prem)
- AS2 → DocEvent Agent (on-prem)
- Filerouter (on-premise) → DocEvent Agent (on-prem)
- FTP Pull → DocEvent Agent (on-prem)
- SFTP Pull → DocEvent Agent (on-prem)
- S3 Compatible (pull) → DocEvent Agent (on-prem)
- GCS Blob Pull → DocEvent Agent (on-prem)
- Azure Blob Pull → DocEvent Agent (on-prem)
- Azure Files Pull → DocEvent Agent (on-prem)
- SharePoint → DocEvent Agent (on-prem)
- DocEvent Agent (on-prem) → DocEvent Agent (on-prem)