List project events with the Sentry API
Lists the error events of a project, 100 per page. With full true each event brings the stack trace, and the page drops to 10.
- Identifier
- sentry_list_project_events
The request
POST https://connect.reportei.com/api/tools/sentry_list_project_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>",
"project_id_or_slug": "<project_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
| Parameter | Type | Required | Description |
|---|---|---|---|
| organization_id_or_slug | string | Yes | Slug or id of the organization, from List organizations. |
| project_id_or_slug | string | Yes | Slug or id of the project, from List projects. |
| statsPeriod | string | No | Relative period, such as 24h or 14d. It overrides start and end. |
| start | string | No | Start of the period, in ISO 8601. |
| end | string | No | End of the period, in ISO 8601. |
| full | boolean | No | True to include the full body of each event, with the stack trace. |
| cursor | string | No | Page 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_project_events. It becomes your agent's tool definition with no conversion.
Other Sentry tools
- List organizationsGETLists the organizations the token reaches in this data storage location, each with id, slug and name. The slug is the organization_id_or_slug the other tools ask for. Returns up to 100.
- List projectsGETLists the projects of an organization, each with id, slug, name and platform. The slug is the project_id_or_slug the project tools ask for. Returns up to 100; narrow with query.
- Get projectGETReturns one project with its name, platform, teams, status and settings.
- List issuesGETLists 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.
- Get issueGETReturns one issue with its title, culprit, status, level, assignee, counts, first and last seen, release and top tags.
- Update issuePUTResolves, archives, reopens, assigns or reprioritizes an issue. Only the fields sent change. To archive, send status ignored with a substatus, and the condition in statusDetails when it is archived_until_condition_met.
- List issue eventsGETLists the events of an issue, 100 per page. With full true each event brings the stack trace, and the page drops to 10.
- Get issue eventGETReturns one event of an issue with the stack trace, tags, context, breadcrumbs and request. Use latest, oldest or recommended as event_id when you have no event id.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
