Skip to main content
Use the error groups API to list, filter, and inspect the grouped issues for a project.

​
List error groups

Common query parameters:
  • from - optional ISO 8601 start timestamp
  • to - optional ISO 8601 end timestamp
  • status - one of unresolved, resolved, ignored, muted, or all
  • priority - one of low, medium, high, or critical
  • level - severity level filter
  • service - service.name filter
  • environment - deployment environment filter
  • q - substring search across title, type, fingerprint, service, and environment
  • limit
  • offset
  • sort - one of last_seen, first_seen, event_count, or priority
Example:
List responses include each group’s priority, bookmarked, subscribed, service_name, and environment when known, plus facets arrays for service, environment, and level filter dropdowns. Each group also exposes assigned_to and ai_assigned; when ai_assigned is true and assigned_to is null the Squasher agent currently owns the group (auto-triage assignment).

​
Get one error group

The response can include the group title, fingerprint, priority, bookmark and subscription state for the current user, event counts, timestamps, current AI triage fields, merged_into when the group is an active duplicate, and merged_from for active duplicates merged into this canonical group. Optional query parameters:
  • include_replay - set to false to skip replay linkage when you only need the core group fields
  • from - optional ISO 8601 start timestamp for replay linkage lookup
  • to - optional ISO 8601 end timestamp for replay linkage lookup

​
Update workflow metadata

JSON body:
Use assigned_to to assign or clear an owner. Setting assigned_to also clears the response field ai_assigned, signalling that a human has taken over from the Squasher agent. Use status to move the error group through unresolved, resolved, ignored, or muted. Use priority to set triage urgency. Use bookmarked and subscribed to update the current user’s saved and notification state; those two fields require an OAuth user session and are rejected for API-key-only requests. Include at least one field in the body. CLI:

​
Merge duplicate groups

Use the canonical error group id in the URL. The request body lists duplicate groups to merge into it:
Merged duplicate groups are hidden from normal unresolved list results. Fetching a merged duplicate returns merged_into so callers can link to the canonical group. Future runtime events that match a merged duplicate fingerprint increment the canonical group.

​
Unmerge a duplicate group

Use the duplicate error group id in the URL. Unmerge restores the group to normal list results and future events for its fingerprint increment that restored group again.
Optional query parameters:
  • from - optional ISO 8601 start timestamp
  • to - optional ISO 8601 end timestamp

​
List suspect commits

Optional query parameters:
  • from - optional ISO 8601 start timestamp
  • to - optional ISO 8601 end timestamp

​
List AI triage runs

Use this endpoint to fetch the history of automatic and manual AI triage runs for one error group.

​
Create or reuse AI triage

Optional JSON body:
Set force to true to create a fresh manual run even when the current automation cycle already has a completed triage result.

​
Agent handoff

Use this sequence for incident or bug investigation:
  1. List unresolved groups with a bounded time window.
  2. Fetch one error group detail.
  3. Fetch related traces, suspect commits, and triage-run history.
  4. Ask before updating status, assigning ownership, or forcing a new triage.
The same workflow is available through squasher errors ... or MCP search("errors") followed by execute.