Skip to main content
StackOne records a request log for every API call it handles on your behalf — action (RPC) runs, MCP tool calls, and the connector steps behind them. This guide shows which endpoints to call, in what order, when debugging failures.
This guide covers request logs only — the same data shown on the Request Logs dashboard page. It does not cover platform or audit logs.The API follows the same drill-down hierarchy as the dashboard: list → detail → advanced / steps / defender.
To build admin or customer-facing log dashboards, see Request Log Dashboards. To export logs into Grafana, Datadog, or a data warehouse, see Observability & Log Sync.

Drill-down hierarchy

Start at the list endpoint and drill down only when you need more detail — exactly as the dashboard does.
OrderEndpointReturns
1. ListList Logs POST /logsPaginated summary rows. Each row includes an action_run_id for drill-down.
2. DetailGet Action Log GET /logs/actions/{actionRunId}Full metadata for a single request (status, duration, connector, account, action).
3a. StepsList Action Step Logs GET /logs/actions/{actionRunId}/stepsConnector execution steps within the request. Requires page and page_size query parameters.
3b. AdvancedGet Action Advanced Log GET /logs/actions/{actionRunId}/advancedHTTP request and response bodies.
3c. DefenderGet Action Defender Log GET /logs/actions/{actionRunId}/defenderDefender scan output for AI agent tool calls.
4. Single stepGet Step Log / Get Step Advanced LogSummary or full payloads for a single step.
For dashboard KPIs without listing individual rows, use Get Logs Stats Aggregate and Get Logs Stats Dimensions.

List filters

List Logs accepts a POST body with filters and pagination. Common filters mirror the dashboard search bar:
FilterUse for
account_idsScope to one or more linked accounts (required for customer-facing views)
connector_keys / providersFilter by integration (e.g. bamboohr, workday)
start_time / end_timeTime window
success / status_codesErrors only, or specific HTTP statuses
action_idsFilter by specific action
See the List Logs API reference for the full filter schema.

Example: list recent errors for an account

curl -X POST "https://api.stackone.com/logs" \
  -H "Authorization: Basic $(printf '%s' "${STACKONE_API_KEY}:" | base64)" \
  -H "Content-Type: application/json" \
  -d '{
    "filter": {
      "start_time": "2024-01-15T00:00:00Z",
      "end_time": "2024-01-15T23:59:59Z",
      "account_ids": ["45355976281015164504"],
      "success": false
    },
    "page": 1,
    "page_size": 50
  }'
Each list row includes an action_run_id. Pass that to the detail and drill-down endpoints.

Debug a failed request

Trace a single failed call from the list through to the step that failed.
OrderEndpointID from previous call
1. Find the logList Logs
2. Get request summaryGet Action Logaction_run_id from order 1
3. List execution stepsList Action Step Logssame action_run_id
4. Inspect a failed stepGet Step Advanced Logaction_run_id + step_index from order 3
5. (Optional) Full request payloadGet Action Advanced Logsame action_run_id
6. (Optional) Defender scanGet Action Defender Logsame action_run_id
Use the Error Explainer in the StackOne dashboard for AI-generated resolution steps when investigating errors in the request logs UI.

Defender security review

Defender must be enabled in your project settings before defender log endpoints return scan results.
Review Defender scan results for AI agent tool calls.
  1. List flagged requestsList Logs and filter by risk_level (returned on log records when Defender is enabled).
  2. Get Defender detailsGet Action Defender Log for the full scan output including risk_level, tier2_score, and classification metadata.
  3. Inspect the responseGet Action Advanced Log to see the sanitized payload Defender evaluated.

Advanced logs: request and response bodies

List Logs, Get Action Log, and Get Step Log return metadata only. To retrieve full HTTP request and response bodies, use the advanced endpoints:
ScopeEndpoint
Entire requestGet Action Advanced Log
Single stepGet Step Advanced Log
Advanced log retention depends on your project’s Advanced Logs settings. Configure retention period and error-only mode in the StackOne dashboard.
Fetch advanced logs on demand — not for every row in a high-volume feed.

Legacy endpoints

Only use these endpoints if you are debugging request logs from legacy unified connectors. For action-based connectors, use the drill-down hierarchy above.
The following endpoints remain available for integrations that generate request logs via legacy unified connectors:
Legacy endpointReplacement
GET /requests/logsList Logs POST /logs
/logs/unified/*List Logs + Get Action Log
/logs/provider/*List Action Step Logs + Get Step Advanced Log

Request Log Dashboards

Build admin or customer-facing log dashboards

Observability & Log Sync

Sync logs to Grafana, Datadog, or custom pipelines

Request Logs (Dashboard)

View and filter logs in the StackOne dashboard

List Logs API

List request logs endpoint reference

Defender

Scan AI tool responses for prompt injection