POST a file over HTTPS and have it sent as AS2
POST a file to your DocEvent endpoint and it is signed, encrypted and transmitted to your trading partner over AS2. The MDN receipt is verified and recorded against the transfer, so a simple HTTPS call becomes a fully compliant AS2 delivery.
From
HTTP Upload
To
AS2
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
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
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 AS2 routing works
Source
HTTP Upload
Files arrive via HTTP POST to a dedicated DocEvent channel endpoint.
DocEvent Channel
routes · retries · logs
Destination
AS2
Files are delivered to an AS2 trading partner — signed, encrypted, and tracked until the MDN receipt comes back.
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 AS2
Outbound AS2 (RFC 4130) delivery to your partner's AS2 URL. Messages are signed (SHA-256, SHA-384 or SHA-512) and encrypted (AES-256, AES-192, AES-128 or 3DES for legacy partners) using the partner's certificate, and can be compressed. Ask for a synchronous MDN, an asynchronous MDN, or none at all — signed receipts are verified and recorded, and a message whose receipt never arrives is parked for reprocessing instead of being quietly lost. Re-sends carry the same Message-ID, so a partner's duplicate detection suppresses them.
Common use cases
Real workflows that teams automate with a HTTP Upload → AS2 channel.
- Give any application an AS2 outbox behind a simple HTTPS POST
- Send EDI from a web app or serverless function with no AS2 SDK
- Add AS2 to a product without shipping certificate handling
- Let an internal service transmit to trading partners over one API call
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 AS2 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:
AS2
Outbound AS2 (RFC 4130) delivery to your partner's AS2 URL. Messages are signed (SHA-256, SHA-384 or SHA-512) and encrypted (AES-256, AES-192, AES-128 or 3DES for legacy partners) using the partner's certificate, and can be compressed. Ask for a synchronous MDN, an asynchronous MDN, or none at all — signed receipts are verified and recorded, and a message whose receipt never arrives is parked for reprocessing instead of being quietly lost. Re-sends carry the same Message-ID, so a partner's duplicate detection suppresses them.
Files are delivered to an AS2 trading partner — signed, encrypted, and tracked until the MDN receipt comes back.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