Protocol & API Logs

A file-transfer problem often needs evidence from the connection that performed it. Protocol Logs give administrators the request and transfer details needed to determine whether a client reached Files.com, authenticated, and completed its operation.

Use these records when investigating a particular client or integration, confirming a transfer result, or reviewing connection activity. Start with the protocol, approximate time, user, and file path so you can narrow the search to the relevant operation. A failed login needs different investigation from an authenticated request that cannot access its destination.

API Logs provide a broader request-level view across interfaces, including requests from the web, Desktop App, integrations, and automated systems. They also record login failures that do not appear in file History. This distinction matters when you need the individual requests behind a summarized activity record.