Files.com records an audit log of every API request made to your site, regardless of the interface used. This includes requests originating from the web, desktop, and mobile interfaces, file transfer protocols, integrations, automated systems, and inbound and outbound services.

Every API request that reaches your site is captured in the API logs, including both successful operations and failed attempts.

Native Files.com Remote Server connections from another Files.com site using your site's API key do not create API request entries or login events on your site. Their file actions appear in History Logs, attributed to the key's owner when a user API key is used. Use that history to review native file operations that do not appear in API logs.

We retain these logs for 180 days.

Request-ID

The Request-ID uniquely identifies a single API request. When you need to contact Support about unexpected behavior, it's often helpful to locate the error in your API Logs first so that you can provide the relevant Request-ID for troubleshooting.

Details Recorded in API Logs

Each API log entry includes the following details.

Column	Details
Date	Start time of the action.
User	Username associated with the action.
Impersonator User	The username of the Site Administrator who initiated the impersonation for the request.
User from Parent Site?	Displays Yes if the request is from a parent site.
Interface	API interface associated with the action.
API Key ID	Shows API key ID (if applicable).
API Key prefix	Shows API key prefix (if applicable).
API Name	Name of the API endpoint.
Request Method	HTTP method associated with the action.
Path	API request path.
Request IP	IP address of the requesting client.
Request-ID	Unique ID of the request.
Request Host	Hostname the request was sent to.
Response Code	HTTP response code sent.
User Agent	User-agent details of the requesting client.
Error Type	Error type, if available.
Error Message	Error message details, if available.
Status	Status such as Success or Failure for each API request. Shows as failure if the HTTP response code is 4xx or 5xx.
Duration	Time taken in milliseconds for the execution of the action.