Query and resolve application error/exception issues and events in Sentry via the Sentry REST API.

Provided free and as is, without warranty of any kind — including merchantability, fitness for a particular purpose, and the accuracy or completeness of any result. See the licence. You are responsible for checking what this produces before relying on it.

Sentry

Query and resolve application error/exception issues and events via the Sentry REST API.

Operations

Operation	Description
`list-issues`	List issues for an organization (optionally filtered by project, query, time window)
`get-issue`	Retrieve full details for a single issue by ID
`update-issue`	Resolve, ignore, unresolve, or reassign an issue
`list-events`	List individual error events that belong to a specific issue

API Key Setup

In Sentry, go to Settings > Auth Tokens (or Settings > Developer Settings > Auth Tokens).
Create a new token with at least the following scopes:
event:read — for list-issues, get-issue, list-events
event:write — for update-issue
Copy the token and supply it as apiKey.

Auth header used: Authorization: Bearer <token>

Base URL: https://sentry.io/api/0

Inputs

Field	Required	Description
`apiKey`	Yes	Sentry auth token
`operation`	Yes	One of: `list-issues`, `get-issue`, `update-issue`, `list-events`
`organizationSlug`	Yes (all ops)	Your org slug from the Sentry URL
`issueId`	Yes (get/update/list-events)	Sentry numeric issue ID
`projectSlug`	No	Filter list-issues to a project
`query`	No	Search query for list-issues (default: `is:unresolved`)
`limit`	No	Max results, up to 100 (default: 25)
`statsPeriod`	No	Time window: `24h`, `7d`, `14d` (default: Sentry default)
`status`	No	For update-issue: `resolved`, `unresolved`, `ignored`
`assignedTo`	No	For update-issue: username, email, or `team:<team_id>`

Outputs

Field	Description
`result`	JSON string containing the Sentry API response
`status`	`ok` on success

Examples

List the 10 most recent unresolved errors:

operation:    list-issues
organizationSlug: my-org
query:        is:unresolved
limit:        10
statsPeriod:  24h

Get details for a specific issue:

operation:    get-issue
organizationSlug: my-org
issueId:      1234567890

Resolve an issue:

operation:     update-issue
organizationSlug: my-org
issueId:       1234567890
status:        resolved

Assign an issue to a team member:

operation:     update-issue
organizationSlug: my-org
issueId:       1234567890
assignedTo:    [email protected]

List events for an issue:

operation:     list-events
organizationSlug: my-org
issueId:       1234567890
limit:         25
statsPeriod:   7d

Publishes

The keys a later task may reference as {{taskName.key}}. Referencing anything not listed here resolves to nothing at run time.

error
result
status

Input Properties

Every property this tool accepts, from its own tool.iml.

Property	Type	Required	Default	Description
`apiKey`	string	yes	—	Sentry auth token (Bearer). Create one at Settings > Auth Tokens with event:read and event:write scopes.
`operation`	string	yes	—	One of: list-issues, get-issue, update-issue, list-events
`organizationSlug`	string	no	—	Your Sentry organization slug (found in the Sentry URL, e.g. my-org).
`issueId`	string	no	—	Sentry issue ID. Required for get-issue, update-issue, and list-events.
`projectSlug`	string	no	—	Filter list-issues to a specific project slug.
`query`	string	no	—	Search query string for list-issues (e.g. 'is:unresolved'). Defaults to 'is:unresolved'.
`limit`	string	no	`25`	Maximum number of results to return for list operations (max 100).
`status`	string	no	—	New status for update-issue. One of: resolved, unresolved, ignored.
`assignedTo`	string	no	—	For update-issue: username, email, or team: to assign the issue to.
`statsPeriod`	string	no	—	Time window for list operations (e.g. 24h, 7d, 14d). Defaults to 24h.