Every operation of the Error Tracking API, under /errors/api. Sign requests with an access key (Authorization: EWS-ACCESS-KEY <id>:<secret>). A successful JSON response is { "success": true, "data": … }.
Projects: a DSN for the Sentry SDKs, retention, rate limit and alerts
DSN keys of a project
Issues: events grouped by fingerprint, with counts, users, first and last seen
Events of an issue: stack traces (source-mapped), breadcrumbs, request, tags, contexts
Performance traces: a trace’s transactions with their spans as a waterfall, and its errors
Profiles: where a transaction spent its time, as a flame graph and by function
Transactions of a project by name and operation: counts, durations, failure rate
Releases created by sentry-cli and the bundler plugins
Alert rules of a project: a trigger (new issue, frequency, users, crash-free rate), filters, and mail or webhook actions (Slack, Teams, Discord, JSON)
Database statements from db spans: time share, calls, slowest calls, N+1, by the fingerprint the database’s query insights use
Managed PostgreSQL databases connected to a project: its Queries tab reads their Query insights
Release health of a project: crash-free sessions and users, adoption, per release
Tokens for sentry-cli and withSentryConfig
Apps and CI environments connected to a project, its managed key and Secrets entry, rotation, upload tokens
Generated from the API description, the same one the API checks requests against and the CLI is built from.