Developer tools
Sentry in your product and your AI agents, through one API
The Sentry toolkit covers organizations, projects, issues and error events with stack traces, tags and context. Your customer connects once with an API key, and your product or AI agent calls each operation through Connect, which stores the credential and logs every execution.
15 days to try it. No credit card.
POST https://connect.reportei.com/api/tools/sentry_list_organizations/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"query": "<query>"
}
}How it works
From a connected customer to the first Sentry call.
- 1
Your customer connects the account
Your system opens a Connect session for the toolkit and your customer connects their Sentry account. You get the connection id.
- 2
Your product calls the tool
A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.
- 3
Connect handles the rest
It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.
Use cases
What your product does with Sentry.
Show errors inside your product
List a customer's unresolved issues with event and user counts so your SaaS can surface what is breaking, next to the app it monitors.
Close the loop from your tracker
Resolve, archive or assign a Sentry issue when the matching ticket changes state in your product.
Triage with an AI agent
Let an agent read an issue, pull its latest event with the stack trace and the top tag values, and propose who should look at it.
Tools
11 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.
- Get issue tagGETReturns the top values of one tag across the events of an issue, with the count of each, such as the browsers or releases affected.
- List project eventsGETLists the error events of a project, 100 per page. With full true each event brings the stack trace, and the page drops to 10.
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.
Questions about the Sentry toolkit
Do I need to build against the Sentry API?
No. Connect ships 11 Sentry tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.
How does my customer connect their Sentry account?
With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.
Does it work with AI agents?
Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.
Does my customer need a Reportei account?
No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.
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.
