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.
Drill-down hierarchy
Start at the list endpoint and drill down only when you need more detail — exactly as the dashboard does.| Order | Endpoint | Returns |
|---|---|---|
| 1. List | List Logs POST /logs | Paginated summary rows. Each row includes an action_run_id for drill-down. |
| 2. Detail | Get Action Log GET /logs/actions/{actionRunId} | Full metadata for a single request (status, duration, connector, account, action). |
| 3a. Steps | List Action Step Logs GET /logs/actions/{actionRunId}/steps | Connector execution steps within the request. Requires page and page_size query parameters. |
| 3b. Advanced | Get Action Advanced Log GET /logs/actions/{actionRunId}/advanced | HTTP request and response bodies. |
| 3c. Defender | Get Action Defender Log GET /logs/actions/{actionRunId}/defender | Defender scan output for AI agent tool calls. |
| 4. Single step | Get Step Log / Get Step Advanced Log | Summary or full payloads for a single step. |
List filters
List Logs accepts aPOST body with filters and pagination. Common filters mirror the dashboard search bar:
| Filter | Use for |
|---|---|
account_ids | Scope to one or more linked accounts (required for customer-facing views) |
connector_keys / providers | Filter by integration (e.g. bamboohr, workday) |
start_time / end_time | Time window |
success / status_codes | Errors only, or specific HTTP statuses |
action_ids | Filter by specific action |
Example: list recent errors for an account
- cURL
- Python
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.| Order | Endpoint | ID from previous call |
|---|---|---|
| 1. Find the log | List Logs | — |
| 2. Get request summary | Get Action Log | action_run_id from order 1 |
| 3. List execution steps | List Action Step Logs | same action_run_id |
| 4. Inspect a failed step | Get Step Advanced Log | action_run_id + step_index from order 3 |
| 5. (Optional) Full request payload | Get Action Advanced Log | same action_run_id |
| 6. (Optional) Defender scan | Get Action Defender Log | same action_run_id |
Defender security review
Review Defender scan results for AI agent tool calls.- List flagged requests — List Logs and filter by
risk_level(returned on log records when Defender is enabled). - Get Defender details — Get Action Defender Log for the full scan output including
risk_level,tier2_score, and classification metadata. - Inspect the response — Get 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:| Scope | Endpoint |
|---|---|
| Entire request | Get Action Advanced Log |
| Single step | Get 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.
Legacy endpoints
The following endpoints remain available for integrations that generate request logs via legacy unified connectors:| Legacy endpoint | Replacement |
|---|---|
GET /requests/logs | List Logs POST /logs |
/logs/unified/* | List Logs + Get Action Log |
/logs/provider/* | List Action Step Logs + Get Step Advanced Log |
Related
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