The Request history tab in API builder shows every inbound request your API has received, with the response code, duration, HTTP method, relative URI, remote IP address, and a trace key for each one. Use it to monitor API activity, investigate errors, and — when you need more detail — turn on debug logging, or set the log mode, and open trace view to follow a single request step by step through your API's execution path.
Anyone with access to API builder can view request history. Execution logs are available in non-production environments for accounts with multiple environment licenses, depending on your account permissions.
Note
Standard, detailed, and debug logging require an admin or owner to enable payload consent at the account level. See Enable debug logging for details.
To open request history, navigate to your API in API builder and click the Request history tab.
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 allows you to track a specific request through every step of the API execution path and locate it in the 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 — Click the icon in this column to open the trace view for that request. Rows captured during an active debug session display a Debug badge next to the trace key. Click the Open trace view icon in the same row to follow the request step by step.
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." Click Clear to reset the search.
- Filter by response code — Click the filter icon next to the Response code column header to open the response code filter. Select one or more codes from the list and click Apply. Click 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." Click Clear filters to reset.
- Filter by time range — Click 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, click the refresh icon.
Log levels control how much execution detail is captured for each API request. Choose the level that matches your current need.
| Log level | What it captures | When to use |
|---|---|---|
| No logging | A request entry in request history only. No response payloads or step details are stored. | You don't want to store any data that might contain sensitive information. |
| Basic | Request URL, HTTP method, status code, duration, remote IP, and trace key. Request and response payloads are stored only for requests that error. | Routine monitoring. This is the default. |
| Standard | Everything in Basic, plus request and response payloads for every request, not just errored ones. Available only at the individual API and Model Context Protocol (MCP) server level. | Capture the full request and response payload for every invocation, for compliance or auditing. |
| Detailed | Everything in Standard, plus request and response payloads and headers for each step. | Data validation and troubleshooting. |
| Debug | Complete execution detail, including inputs and outputs for internal step components such as mappings and transformations, and full request and response payloads. Time-limited. | Short-term in-depth investigation. |
Basic logging is enabled by default. Detailed and Debug logging require payload consent to be enabled at the account level. If your account does not have payload consent enabled, you will see a prompt to request admin approval when attempting to enable either level. See Enable debug logging for details on activating Debug mode.
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
- In API builder, click the debug icon in the toolbar.
- In the Capture debug logs for next panel, enter a duration in hours and minutes.
- Select Start.
Debug mode takes effect immediately, and it 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:
| Subscription | Maximum debug duration |
|---|---|
| Free trial | 15 minutes |
| Standard | 1 hour |
| Professional | 24 hours |
| Enterprise | 72 hours |
Warning
Debug logs may increase latency and cause timeouts, especially for high-volume or one-to-many APIs.
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 afterward.
Only admins, owners, and users with manage access can delete logs.
To delete logs
- In the Request history tab, select Delete logs.
- Select a date range, then select Apply.
- 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 the Open trace view icon in any row to open it.
The left panel shows the API path: a tree of every step the request passed through, including the API request node, branching, lookups, imports, mappings, and success or error response nodes. Each node shows its execution time. Select a node to view its data in the right panel.
What appears in the right panel depends on which node you select.
API request node
- HTTP request — General details (request URL, HTTP method, remote IP), headers, and request body.
- Parsed output — The parsed payload passed downstream to subsequent steps.
All other nodes (lookups, imports, mappings, response nodes)
- Input — The data received by this step.
- HTTP Response — General details (status code, response time), headers, and response body.
Note
Authentication tokens, API keys, and other sensitive information are always masked in trace view.
The request history table shows different messages depending on why no results are displayed.
- No request history yet — Displays when the API has not received any requests in the selected time range: "You don't have any request history."
- No search results — Displays when a search query produces no matches: "Query may be too specific to produce results. Try another query, or clear current search query." Click Clear to reset the search.
- No filter results — Displays when active response code filters produce no matches: "Filtering may be too specific to produce results. Adjust selected filters, or clear current selection." Click Clear filters to reset.