Protocol Logs record activity from the transfer protocols your site accepts: API requests, FTP and FTPS connections, SFTP sessions, AS2 transmissions, and WebDAV access. Each log gives administrators a per-protocol view of who connected, what they transferred, and whether operations succeeded or failed.

Use Protocol Logs when you need to investigate a transfer issue tied to a specific protocol, audit access patterns for a particular client type, or confirm that a scheduled automated process ran and completed successfully. Because each protocol has its own authentication and transfer mechanics, keeping the logs per-protocol makes it easier to isolate a problem to the right layer.

Logs in This Section

API Logs record every request made to your site regardless of the interface: web, desktop, mobile, protocol clients, integrations, and automated systems. API Logs are the most granular source of activity on the platform, capturing individual requests including login failures that other logs consolidate or omit.

FTP Logs record FTP and FTPS file transfer activity. Use these to audit FTP access, investigate failed transfers, and confirm that FTP-based integrations are operating as expected.

SFTP Logs record SFTP session and transfer activity. Each entry captures the time of action, remote IP, user, action type, file path, and status, making SFTP Logs useful for auditing scripted transfers and troubleshooting client connectivity issues.

AS2 Logs record inbound and outbound AS2 transmissions between your site and your AS2 trading partners, including Message Disposition Notification (MDN) details when available. Use AS2 Logs to confirm delivery and diagnose transmission failures with trading partners.

WebDAV Logs record actions performed by WebDAV clients against your site. Use these to audit WebDAV access and investigate activity from WebDAV-based integrations or desktop clients.