Understanding Connection Methods

Modalius supports multiple methods for exchanging EDI files with partners. Understanding these methods helps you choose the right approach for your integrations.

Modalius SFTP (Internal)

The default delivery method for partners who also use Modalius.

How it works: Files are delivered directly to the partner's Modalius SFTP business unit.

Best for:

• Partners who use Modalius
• Simplest setup - no external configuration needed

External SFTP

For partners who have their own SFTP server.

How it works: Files are uploaded to or downloaded from the partner's secure server using encrypted SFTP connections.

Configurable polling frequency: For inbound SFTP connections, you can configure how often Modalius checks the partner's server for new files. The polling interval is set in minutes and can be adjusted from the connection's settings. This lets you balance between near-real-time pickup and reducing load on the partner's server.

Best for:

• Batch file transfers
• Partners with existing SFTP infrastructure
• Simple, reliable connections

Requirements: Server address, username, password or private key, directory path

AS2 (Applicability Statement 2)

A specialized protocol designed specifically for EDI.

How it works: Files are sent directly between systems using HTTP/HTTPS with digital certificates for security and non-repudiation.

Optional access credentials: AS2 connections now support optional password-based access credentials in addition to the required digital certificates. This allows partners that require basic authentication on their AS2 endpoint to be configured without needing a separate authentication step.

Best for:

• Real-time EDI transmission
• Partners requiring signed receipts (MDN)
• Compliance requirements (many retailers require AS2)

Requirements: Digital certificates, AS2 ID, partner's endpoint URL. Access credentials (password) are optional.

API (Application Programming Interface)

Direct integration using HTTP/HTTPS endpoints.

How it works: Systems communicate directly using web service calls (GET, POST, PUT, PATCH).

Best for:

• Custom integrations
• Real-time processing
• Automated workflows

Requirements: Endpoint URL and developer resources. Authentication credentials (API key, password, or OAuth) are optional and can be attached from the connection detail page if the partner's API requires them.

Enabling and Disabling Connections

All connection types can be enabled or disabled from the connection detail page using the Enabled toggle or the Manage menu.

• Enabled - The connection is active and files will be sent or received normally
• Disabled - The connection is paused. No files will be transmitted while disabled

When disabling a connection, you can choose whether to queue files while inactive. If enabled, files that would have been sent through this connection are held in a queue and will be delivered automatically when the connection is re-enabled. If disabled, files intended for this connection will not be queued.

Choosing a Method