AS2 for your trading partners, without an AS2 server
DocEvent runs both ends of AS2 for you. Hand a partner your AS2 URL and identifier and their messages arrive decrypted, verified and acknowledged. Point a send endpoint at their URL and your files go out signed and encrypted, with the receipt tracked until it comes back. Sync MDNs, async MDNs, or no MDN at all — all three are handled.
Get started for free — channels are free during beta.
Receive AS2, send AS2, or both
AS2 is a source and a destination like any other in Channels — which means an AS2 message can be delivered anywhere, and anything can be transmitted as AS2.
Inbound
Your trading partner
Posts an AS2 message to the URL you gave them. DocEvent decrypts it, verifies their signature, checks it against the partner pinned to that endpoint, and returns the MDN.
DocEvent Channel
decrypt · verify · MDN · route
Delivered to
Any destination
FTP, SFTP, a webhook, an inbox, a SharePoint library, a folder on your own machine — or straight back out to another AS2 partner.
Outbound
Any source
A file lands in S3, is POSTed over HTTPS, is collected from your FTP or SFTP server, is saved to SharePoint, or is dropped in a watched folder.
DocEvent Channel
sign · encrypt · transmit · track
Sent as AS2
Your trading partner
Signed with your certificate, encrypted with theirs, delivered to their AS2 URL — and not marked done until the MDN receipt is verified.
Every MDN mode, managed for you
The MDN is the receipt that says the message arrived and its signature checked out. Partners disagree about how it should travel, so DocEvent supports all three ways in both directions — you pick per endpoint, and on the receive side you simply answer whichever way the partner asked.
1
Synchronous
The receipt comes back in the same HTTP response as the message. Sending: DocEvent verifies the signed MDN and records it against the transfer before the transmission is considered done. Receiving: DocEvent builds and returns the MDN in the reply, signed if the partner asked for it.
2
Asynchronous
The receipt arrives later, as a separate HTTP request. Sending: DocEvent records that the message is awaiting a receipt before the message even leaves, then matches the MDN when the partner posts it back — a file whose receipt never arrives is parked for reprocessing rather than quietly assumed delivered. Receiving: DocEvent queues the MDN and posts it to the partner's return URL.
3
None
Some partnerships do not use receipts at all. Set the mode to none and the message is transmitted — or accepted — with no MDN expected in either direction. Delivery is still logged end to end in the channel audit trail.
Signed receipts are supported and verified in both directions — ask for them on a send endpoint, and return them on a receive endpoint when the partner requests one.
Signed and encrypted, both ways
AS2 wraps each payload in S/MIME. DocEvent does the wrapping and unwrapping — you choose the algorithms only when a partner's stack demands something specific, because AS2 has no negotiation step.
- Outbound messages are signed with your own certificate — SHA-256 by default, SHA-384 or SHA-512 where a partner requires it
- Outbound payloads are encrypted with the partner's certificate using AES-256-CBC by default, or AES-192, AES-128 or 3DES for older partner software
- Inbound messages are decrypted with your private key and the partner's signature is verified before the file is allowed into the channel
- Optional compression on the way out, for partners who want it
- A receive endpoint can require that inbound messages be signed, encrypted, or both — anything that does not meet the policy is rejected, not quietly accepted
- Private keys are encrypted at rest with AWS KMS and are never shown back to you or to anyone else
Identities, partners and certificates
A certificate is the whole trust basis of an AS2 partnership, and a lapsed one breaks it with no warning. DocEvent keeps them in one registry and tells you before that happens.
- Your AS2 identities (stations) and your trading partners both live in Channels → Partners in the web console
- Each receive endpoint is pinned to exactly one partner: a message claiming any other AS2 identity is rejected outright
- Certificate expiry is surfaced before it bites — a warning 30 days out and a critical alert inside 7, on the Channels nav, the Partners page and the partner row
- Duplicate messages are detected per RFC 4130, so a partner's retry after a lost acknowledgement does not deliver the same document twice
- Every re-send DocEvent makes carries the same Message-ID, so your partner's duplicate detection suppresses it too
What you can connect AS2 to
AS2 at the edge, whatever you already run on the inside.
Receive AS2, deliver it to…
Browse all channel integrations — any source, any destination, in any combination.