HTTP UPLOAD IN. FTP OUT. NO SCRIPTS.
Accept file uploads via HTTP and push to FTP servers
Accept file uploads via HTTP POST and automatically deliver them to an FTP server with DocEvent Channels. Build a seamless bridge between modern HTTP APIs and legacy FTP infrastructure — no custom code needed.
From
HTTP Upload
To
FTP
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 FTP routing works
Source
HTTP Upload
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
DocEvent Channel
routes · retries · logs
Destination
FTP Server
Files are pushed to any FTP server you configure.
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 FTP
Active and passive FTP supported. Username/password authentication. Configurable port and path.
Common use cases
Real workflows that teams automate with a HTTP Upload → FTP channel.
- Bridge modern web upload APIs to FTP-based partner systems
- Accept files from web forms or apps and route them to FTP
- API-to-FTP gateway for legacy system integration
- Receive files via REST API and distribute to FTP drop zones
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 FTP 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:
FTP Server
Active and passive FTP supported. Username/password authentication. Configurable port and path.
Files are pushed to any FTP server you configure.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