API logs

Use API logs to view a detailed record of all incoming API requests across your workspace. Logs help you monitor usage, troubleshoot failures, and track performance over time.

API logsAPI logs

The logs table includes the request date and time, status, API collection, endpoint, client identity, IP address, and response time.

Filters

Use the filters at the top of the Logs tab to narrow the results. You can filter by the following:

Filter typeDescription
PeriodFilter logs by time period, such as Last 30 days.
StatusFilter logs by status, such as 200 OK or 404 Not Found.
ClientFilter logs by specific clients, such as Customer Success Team.
Collection typeFilter logs by Recipe collections or Proxy collections types.
CollectionSelect specific API collections to include in the results.

Filters reset after you leave the page.

Download logs as a CSV file

Select the Download results button to export the logs table as a CSV file. The CSV includes all visible fields from the logs UI and additional details to help diagnose API behavior.

Download logs as a CSV fileDownload logs as a CSV file

The exported CSV includes the following fields:

FieldDescription
DateTimestamp when the API request was received.
TypeGeneral outcome of the request, such as Success or Error.
CodeHTTP status code returned, such as 200, 401, or 404.
StatusHTTP status text corresponding to the code, such as OK or Not Found.
Gateway codeExtended diagnostic code for failed requests, such as 4011 or 4012.
Status detailsDiagnostic message for failed requests, such as Unrecognized token, Missing token, and Recipe is inactive.
IPClient IP address.
TimingTime taken to process the request.
DelayTime between receiving the request and starting execution.
API collectionCollection associated with the API endpoint.
EndpointAPI endpoint path defined in the collection.
ClientName of the client making the request.
Job detailsLink to the recipe job triggered by the request, if applicable.

Status details for failed requests

The Status details column includes diagnostic messages for common client-side errors, such as 401 and 404. These messages appear in downloaded logs, but not in the logs UI or client-facing responses.

Refer to Status details for 401 and 404 errors for more information on status codes and messages.

Last updated: