Get started

Turn inbound AS2 messages into HTTP webhook calls

Receive AS2 from your trading partners and have each decrypted, verified payload POSTed to your own HTTPS endpoint. DocEvent handles the AS2 protocol — certificates, encryption, signatures and MDN receipts — and your application just receives an ordinary webhook.
From
AS2
To
HTTP Webhook
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 AS2 to HTTP Webhook routing works

Source

AS2

Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.
DocEvent Channel
routes · retries · logs
Destination

HTTP Webhook

Files are POSTed to any HTTP/HTTPS endpoint you configure as a webhook.
1

File arrives via AS2

A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
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 AS2 → HTTP Webhook channel.
  • POST partner EDI documents straight into your application or API
  • Trigger an order-processing pipeline the moment an AS2 message lands
  • Give a microservice AS2 connectivity without any AS2 library
  • Feed inbound AS2 into an iPaaS or serverless workflow over HTTPS
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the AS2 or HTTP Webhook side under their own account, with their own credentials. Learn how shared channels work.

Technical details

Source:
AS2
A hosted AS2 (RFC 4130) receive endpoint with its own URL — nothing to install and no AS2 server to run. Each source is pinned to one trading partner, so a message claiming any other AS2 identity is rejected, and the partner's certificate must verify every message. Encrypted payloads are decrypted and signatures verified automatically, and the MDN receipt is returned the way the partner asked for it: synchronously in the HTTP reply, asynchronously to their return URL, or not at all. Duplicate messages are detected per RFC 4130.
Files arrive from an AS2 trading partner over the internet — signed, encrypted, and acknowledged with an MDN receipt.
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

Related channel integrations

Other destinations from AS2
Other sources to HTTP Webhook
View all 112 channel integrations

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

Get started for free