API Logs

Last updated on November 20, 2026

API Logs help you debug calls to the REST API and to the MCP server, including requests made by users and Stations. Review the recorded caller, endpoint, outcome, and diagnostic traces from one place.

API Logs are an operational log, kept for 90 days. For a permanent record of who changed what in your organization, use the Audit Log.

What gets logged

Activity entries can contain the following information. Some fields are present only when the request supplies them or creates a related record.

FieldValue
Entry IDThe activity record's unique identifier.
Start and end timesRecorded processing times, in UTC with millisecond precision. Their difference gives the duration.
Method and endpointThe request method and the endpoint being called.
StatusThe recorded response status code.
CallerThe user or station associated with the request.
Client and versionRecognized client information, when available.
Related recordThe run, procedure, unit, revision, or part linked to the call, when available.
Message and tracesDiagnostic messages with their level and timestamp, when recorded.
Request IDIdentifies the request, generated by TofuPilot. The audit events of a write carry the same ID.

Request bodies are not stored in API Logs. The Audit Log keeps the input of every write, with credentials redacted.

Activity logging is best-effort: a failure to save an activity entry does not block the original API operation. The activity log is not a guarantee that every request has been recorded.

Dashboard

Open API Logs in the sidebar (Monitor group). You see requests in reverse-chronological order, and the top of the page renders a 144-bucket histogram of request volume over the selected window, stacked by status category (2xx, 3xx, 4xx, 5xx). This lets you spot waves of failures or traffic spikes at a glance.

You can filter by:

  • Date range: preset or custom window. The default is the last month.
  • Endpoint: narrow the table to a recorded endpoint, such as the run or procedure endpoint.
  • Method: only POST, only DELETE, etc.
  • Status: 2xx, 3xx, 4xx, 5xx categories.
  • Client: recognized client information. Python is currently the recorded client category; other requests may have no client label.
  • Created by: narrow to a specific user or Station.

The Messages column shows how many traces a request recorded and its most severe message. Calls made through MCP are listed with the method MCP and the endpoint mcp/<tool>.

Click a row to open the activity details and follow its related Run, Unit, or Procedure, when available. For a write, Audit events opens the audit log entries the request produced.

Retention

API Logs are kept for 90 days, then deleted. The Audit Log is not affected: its events are kept for the lifetime of the organization.

Export

Use the dashboard export menu to download the currently loaded activity rows as CSV or JSON. Apply the filters you need, then load the rows you want to include. The export contains those loaded rows; it does not fetch every matching record automatically.

Exports contain the entry ID, method, endpoint, status, start and end times, client information, caller names, message, and request ID. Diagnostic traces are not included in these dashboard exports.

API activity is not currently exposed through a public REST export endpoint.

Permissions

Access to API Logs inherits the organization's role model, so a member sees what their role allows.

RoleSees
Owner, Admin, DeveloperAPI activity within their organization.
Viewer, OperatorNo access.

How is this guide?

On this page