View API request and execution logs in API builder

To open request history, open your API in API builder and select Request history.

Each row in the request history table represents one inbound request. The table includes the following columns:

• Time — The date and time the request was received.
• Response code — The HTTP response code returned. Codes in the 2xx range appear in green; error codes appear in red.
• Duration (ms) — How long the API took to process the request, in milliseconds.
• Method — The HTTP method used (GET, POST, PUT, PATCH, DELETE, etc.).
• Relative URI — The path of the request, relative to https://api.integrator.io/apis/<version>. Long URIs are truncated in the table view.
• Remote IP — The IP address of the client that sent the request.
• Trace key — A unique identifier assigned to each request. The trace key lets you track a specific request through every step of the API execution path and find it in request history using search. To learn how trace keys work and how to set a custom trace key, see Set a custom trace key to uniquely identify a record.
• Open trace view — Opens trace view for that request. Rows captured during an active debug session display a Debug badge next to the trace key.

Use the search bar and filter controls to narrow the request history table to the entries you need.

• Search by URI — Type a relative URI or partial URI into the search bar. The table updates to show only matching requests. If your query produces no results, the table displays: "Query may be too specific to produce results. Try another query, or clear current search query." Select Clear to reset the search.
• Filter by response code — Select the filter icon next to Response code. Select one or more codes from the list, then select Apply. Select Clear to remove all selected codes. If the active filters produce no results, the table displays: "Filtering may be too specific to produce results. Adjust selected filters, or clear current selection." Select Clear filters to reset.
• Filter by time range — Select the time range selector (default: Last 5 mins) to change the window of request history displayed.

To refresh the table and fetch the latest requests, select the refresh icon.

When a connection your API uses is offline, the request fails in one of two ways, depending on the API's Immediate error for offline connections setting:

• Setting on — The request returns 500 right away, so its Duration (ms) is short. The caller receives the message "One or more connections used by this API are offline. Contact the API publisher and try again later."
• Setting off — The request waits for the connection and returns 504 when the API times out, so its Duration (ms) is close to the API's timeout.

To find these requests, filter by response code 500 or 504, then open trace view to see the error and the step where it occurred. To change the setting, see Create and manage APIs using API builder.

Log levels control how much execution detail is captured for each API request. To set one, select Actions, and then select Change log mode. Choose the option that matches your current need.

Standard log, Detailed log, and debug mode require an admin or owner to enable payload consent at the account level. If your account doesn't have payload consent enabled, a prompt asks you to request admin approval when you try to select one of these options. See Enable debug logging for details on activating Debug mode.

Salesforce steps

Salesforce lookups, imports, and exports in your API write logs at the log level you select. In trace view, Salesforce steps show Input and HTTP response, like other lookup and import steps. Salesforce steps in APIs capture the same payload content as Salesforce steps in flows. See Log data captured by log level.

Salesforce file operations (ContentVersion, Attachment, and Document) and connection activity outside an API run aren't logged.

Debug mode temporarily raises logging to the Debug level, capturing complete execution detail for every request received while it's active. It overrides whatever log level is otherwise set while it's on.

To enable debug mode:

1. In API builder, select Enable debug mode.
2. In Capture debug logs for next, enter a duration in hours and minutes.
3. Select Start.

Debug mode takes effect immediately and logs every request received during the active window at the Debug level.

The minimum duration is 5 minutes. The maximum debug duration depends on your subscription:

Delete stored request logs to remove data you no longer need or to meet a compliance requirement. Deleting a log permanently removes its payloads and metadata for the date range you select. The request entry and status summary remain in request history.

Only admins, owners, and users with manage access can delete logs.

To delete logs:

1. In Request history, select Delete logs.
2. Select Select date range, choose a range, then select Apply.
3. In the Delete logs? confirmation dialog, select Delete logs.

Each deletion is recorded in the audit log with the time, user, action, and selected date range.

Logs are retained according to your account's data retention policy.

Trace view follows a single request end to end through your API's execution path, showing the steps it passed through, the data at each step, and how long each step took. Select Open trace view in any row to open it.

The request history table shows a message when no requests match what you're viewing:

• No request history — Displays in the default time range when the API has no requests: "You don't have any request history."
• No requests in the selected time range — Displays when you choose a different time range and no requests fall within it: "We couldn't find any request logs that match your search terms or filter criteria." Select Clear to reset.
• No search or filter results — Displays when a search query or response code filter produces no matches. For the exact messages, see Search and filter request history in this article.