Developer ToolsFree templatePDF, Excel, Word export

EDI AS2 Connection Parameters Request Template

Before any EDI file moves over AS2, both sides must agree on identifiers, URLs, certificates and security options. A single wrong AS2 ID or an expired certificate stops the connection. This form collects every parameter in one document you can send to the partner and file afterwards.

Fill in

Live preview
Download:

EDI AS2 Connection Parameters Request Template

AS2 Connection Parameters

Prepared by: Acme Precision Ltd Trading partner: Northwind Retail Date: 2026-10-20

Identifiers and endpoints

ParameterOur valuePartner value
AS2 IDACMEPRECISIONNORTHWINDEDI
Receive URLhttps://as2.acme.example:4080/as2/receivehttps://as2.northwind.example/as2/inbound
Technical contactRahul Mehta, edi@acme.example, +1 555 0100
Emergency contact

Security and message options

OptionAgreed setting
Signing algorithmSHA-256
Encryption algorithmAES-256
MDN receiptSynchronous signed
CompressionNone
Content typeapplication/edi-x12 or application/edifact
TLS versionTLS 1.2 or higher
Filename in header

Certificates

Our public certificate expires: 2027-09-30

Exchange public certificates only, never private keys. Confirm the signing certificate, the encryption certificate and any intermediate certificates. Agree on a renewal notice period so both sides can update before expiry.

Network access

Source IP addresses that will connect to the partner: 203.0.113.10 203.0.113.11

Partner source IP addresses to allow on our firewall: (to be provided by partner)

Test and go-live

StepOwnerDateDone
Exchange certificates
Connectivity test
Signed and encrypted test file
MDN received and verified
Production cutover

Approvals

Our EDI coordinator / Date
Partner EDI contact / Date

This form records agreed settings only. Exchange certificates through a secure channel and never send private keys or passwords on this form. Confirm algorithms against your own security policy and the partner's guide.

Review your AS2 and certificate setup

Optional: ask for a second pair of eyes on connectivity and certificate management.

Optional. The tool and every export work without this. No spam.

How to use the form

Fill in your own values, export to PDF or Word and send it to the partner's technical contact, asking them to complete the second column. AS2 IDs are case sensitive in many products, so copy them exactly. Agree on signing, encryption and MDN type before testing, because mismatches show up as vague decryption or verification failures. Use the test and go-live table to track who does what.

  • AS2-From and AS2-To must match each side's configuration exactly
  • Decide synchronous or asynchronous MDN before testing
  • Record certificate expiry dates and set reminders

What each parameter does

The AS2 ID identifies each partner in the message headers. The receive URL is where the other side posts messages. Signing proves the sender and integrity, encryption protects content in transit, and the MDN is the receipt that confirms the message arrived and, if signed, was not altered. SHA-256 and AES are the usual modern choices, while SHA-1 and 3DES remain only for legacy partners. TLS on the transport is a separate layer.

Certificate management

Expired certificates are the most common cause of sudden AS2 outages. Put every certificate expiry into a shared calendar at least 60 days ahead. Agree how renewals are exchanged and whether the partner supports two active certificates during a changeover. Public certificates only should ever travel by email or portal. Store private keys in your integration platform's key store with restricted access.

Common mistakes

Wrong IP allow lists, a firewall that blocks the inbound port, mismatched MDN modes and sending the wrong certificate (signing instead of encryption) cause most failed first tests. Another is forgetting that load balancers can alter source addresses. Test with a small file first, then with a realistic one.

Frequently Asked Questions

What is an AS2 ID?

It is the name each party uses to identify itself in AS2-From and AS2-To message headers. IDs are agreed between partners, are often case sensitive and should be unique for each trading relationship.

What is an MDN in AS2?

A Message Disposition Notification is the receipt returned after a message is received and processed. It can be signed to prove the content arrived intact. Sync MDNs return on the same connection, async MDNs return later to a separate URL.

Which hash and encryption should I choose?

Choose what your partner supports from the stronger options, typically SHA-256 for signing and AES-128 or AES-256 for encryption. Avoid SHA-1 and 3DES unless a legacy partner insists, and follow your security policy.

Can I send private keys with this form?

No. Only public certificates should be exchanged. Private keys must stay inside your own key store and never travel by email, chat or forms.

Netray can help review your integration platform's AS2 setup and certificate calendar if your partner connections are managed ad hoc.

Talk to an ExpertExplore More Free Tools

Related Tools

Supply Chain & Inventory

EDI Partner Test Plan and Sign-Off Template

A test plan document with cases for inbound and outbound transaction sets, pass criteria and go-live sign-off for a new trading partner.

ERP Operations

EDI Error Escalation Runbook Template

A runbook defining what counts as an EDI incident, who responds, how fast, and how to resend and communicate with trading partners.

Supply Chain & Inventory

EDI Routing Guide Requirements Matrix Worksheet

Summarize each customer's vendor guide: documents required, ASN timing, label standard, pack rules and routing, so the team works from one table.

Supply Chain & Inventory

EDI 997 Functional Acknowledgment Reject Log Worksheet

Log every rejected or partially accepted 997 with the AK3/AK4 error, root cause, owner and resend status, and export it to Excel.

More Developer Tools tools

See all
Back to All Tools