Skip to main content
StackOne registers relevant information of requests made to the connected provider to fulfill any request it receives. This can be useful for:
  • Debugging issues with a particular account or integration
  • Auditing the operations StackOne performs on your behalf
The Request Logs page offers efficient find, filter, and analysis of API requests and HTTP status codes.
Logs are only persisted up to 90 days after the original request occurred.

Request logs

When you execute an API query and want to investigate an API response, that’s when the realization comes – logs review is inevitable. The page shows all requests made to StackOne and also allows you to see all requests that StackOne made to the underlying providers to fulfill them. By default, it shows the logs in descending order per when the request occurred.

Accessing the request logs page

After configuring Account integration and testing its connection, you can also access its specific request logs directly by clicking the View Logs option in the ellipsis menu.
Request logs interface

You will be redirected to the logs page with a filter pre-applied in the search bar

Filtering

All filters are grouped in a single search bar — hover over it and click ❌ to remove multiple filters at once. The possible filtering options are:

Viewing log details

Click ➡️ on a log entry — including successful requests — to open a detailed view with two tabs:
  1. Details: Shows the details of the request made to StackOne, including request/response headers, body, query parameters, and status.
    Note: Log storage duration can be configured in the Advanced Logs section of your Project Settings.
  1. Underlying Requests: Displays all API calls made to the provider’s API to fulfill your unified request to enable better debugging.

Programmatic access via API

You can also access request logs programmatically using the Logs API endpoints. For debugging failed calls, see Request Log Debugging. These APIs allow you to integrate log data into your monitoring, alerting, or analytics systems.

Error Explainer

The Error Explainer is a built-in AI feature that helps you resolve errors without decoding raw logs or cryptic provider messages.
Think of the Error Explainer as a smart resolution agent:
  • Extracts key information from error logs automatically — no reading through raw JSON or HTTP dumps.
  • Looks up context from multiple sources: provider documentation, StackOne documentation, and StackOne’s error guides.
  • Generates resolution steps specific to your integration and the problem at hand — typically three clear, actionable steps, prioritizing provider-specific errors as the root cause (e.g. “Refresh your access token with the correct scope”, or “Verify that the API key has permissions to call this endpoint”).
Invoke it by clicking Click to Generate wherever it appears, in three places:
  • Provider request logs — run it across all underlying requests to identify and fix broken ones
  • Individual requests — generate tailored suggestions for a single error
  • Account status page — if an account has connection issues, run it directly from the account’s page
The Error Explainer can be enabled or disabled per project under Project Settings → AI Settings, individually or via the global AI toggle. It also needs Advanced Logs enabled to have request detail to work from.
Your logs are only used to generate explanations for your own account — no PII is used in training or evaluation. Each explanation can be rated in the dashboard, on both usefulness and the accuracy of its suggested steps.