List issues with the Sentry API

Lists the issues of an organization, by default the unresolved ones ordered by last seen. Each issue has id, shortId, title, status, level, count of events, count of users, first and last seen and project. Returns up to 100; narrow with query, project and statsPeriod.

Identifier
sentry_list_issues

The request

POST https://connect.reportei.com/api/tools/sentry_list_issues/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "organization_id_or_slug": "<organization_id_or_slug>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
organization_id_or_slugstringYesSlug or id of the organization, from List organizations.
querystringNoSearch in Sentry syntax, such as is:unresolved level:error firstSeen:-24h. Defaults to is:unresolved; send an empty text for every issue.
projectarrayNoIds or slugs of the projects to keep, from List projects. Omit it for every project the token reaches.
environmentarrayNoNames of the environments to keep, such as production.
statsPeriodstringNoRelative period, such as 24h, 14d or 2w. It overrides start and end.
startstringNoStart of the period, in ISO 8601.
endstringNoEnd of the period, in ISO 8601.
sortstringNoOrder: date is last seen, new is first seen, freq is events, user is users affected. Defaults to date.Values: date, new, trends, freq, user, inbox, recommended
shortIdLookupstringNoSet to 1 to find an issue by the short id shown in Sentry, such as PROJECT-1A2, sent in query. The other filters are then ignored.Values: 0, 1
limitintegerNoIssues to return, up to 100.

Supported connections

Your customer connects their Sentry account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

When connecting, your customer also enters {region}: the address of their account on the app's API.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/sentry_list_issues. It becomes your agent's tool definition with no conversion.

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.