errors.list
Retrieve recent error events with full context including message, type, stack, and user environment. Filter by time period, browser, or fingerprint to diagnose specific bugs.
Instructions
Recent error events with full context. One row per occurrence, returned newest-first. Each row carries the error itself (message, type, stack, fingerprint, handled flag) plus the standard event context (url, browser/OS/device, country, anonymous_id, session_id) — same shape ingest enriches every other event with, so an agent can correlate "errors here, traffic there" without joining a second tool.
Errors are written to the events table with name = "$error" by the SDKs' captureError() / window.onerror auto-capture. The server adds a stable error.fingerprint at ingest (sha256 of normalized message + first stack frame), so the same bug groups across occurrences regardless of which session or SDK reported it.
Examples:
"what errors fired today" → period="today" (no other filters)
"show me all TypeError occurrences this week" → message="", or use errors.groups first to find the fingerprint
"errors on Safari only" → browser="Safari"
"errors on the same fingerprint" → fingerprint=""
"only the auto-captured ones, not manual reports" → handled="false"
Limitations: returns up to limit rows (default 50, max 200). Stacks are stored verbatim from the SDK with no source-map resolution — production stacks will be minified for users on a build pipeline. For aggregate counts and dedup, use errors.groups; for breadcrumbs leading to one error, use errors.context.
Pairs with: errors.groups (find a noisy fingerprint, then list its occurrences here); errors.context (drill from one error row into the events from the same session that led to it); users.journey (full multi-session view of a user who hit an error).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | No | Target project ID (e.g. "proj_abc123"). Required when the credential has access to multiple projects. If omitted and only one project is accessible, that project is used automatically. Call `projects.list` to discover available project IDs. | |
| period | No | Time period. Use "today", "yesterday", "7d", "30d", "90d", or a custom range as "YYYY-MM-DD:YYYY-MM-DD" (e.g. "2026-01-01:2026-03-31"). Defaults to "30d". | |
| limit | No | Max rows to return (1-50). Defaults to 10. | |
| message | No | Filter by exact error message (matches the `error.message` property). Use a known message verbatim; substring matching is not supported. | |
| fingerprint | No | Filter by server-computed fingerprint (16-char hex). Get fingerprints from errors.groups; same fingerprint groups all occurrences of the same bug. | |
| handled | No | Filter to handled (manual captureError calls) or unhandled (window.onerror / unhandledrejection auto-capture). Omit to return both. | |
| browser | No | Filter by browser name (e.g. "Chrome", "Safari", "Firefox"). Case-sensitive; use the exact value the SDK reports. | |
| os | No | Filter by OS name (e.g. "macOS", "Windows", "iOS", "Android"). | |
| device_type | No | Filter by device type. Use this to isolate mobile-only bugs. | |
| country | No | Two-letter ISO country code (e.g. "US", "DE"). Useful when an error correlates with a CDN edge or a localization issue. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| period | Yes | ||
| count | Yes | ||
| errors | Yes |