List issue events with the Sentry API

Lists the events of an issue, 100 per page. With full true each event brings the stack trace, and the page drops to 10.

Identifier
sentry_list_issue_events

The request

POST https://connect.reportei.com/api/tools/sentry_list_issue_events/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>",
    "issue_id": "<issue_id>"
  }
}

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.
issue_idstringYesId of the issue, the numeric id from List issues.
querystringNoSearch in Sentry syntax over the events, such as browser.name:Chrome.
environmentarrayNoNames of the environments to keep.
statsPeriodstringNoRelative period, such as 24h or 14d. It overrides start and end.
startstringNoStart of the period, in ISO 8601.
endstringNoEnd of the period, in ISO 8601.
fullbooleanNoTrue to include the full body of each event, with the stack trace.
per_pageintegerNoEvents per page, up to 100.
cursorstringNoPage cursor as 0:offset:0, for example 0:100:0 for the second page of 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_issue_events. It becomes your agent's tool definition with no conversion.

Other Sentry tools

See all 11 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

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