Error Tracking API Reference

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

Projects: a DSN for the Sentry SDKs, retention, rate limit and alerts

keys

DSN keys of a project

issues

Issues: events grouped by fingerprint, with counts, users, first and last seen

events

Events of an issue: stack traces (source-mapped), breadcrumbs, request, tags, contexts

traces

Performance traces: a trace’s transactions with their spans as a waterfall, and its errors

profiles

Profiles: where a transaction spent its time, as a flame graph and by function

transactions

Transactions of a project by name and operation: counts, durations, failure rate

releases

Releases created by sentry-cli and the bundler plugins

alert-rules

Alert rules of a project: a trigger (new issue, frequency, users, crash-free rate), filters, and mail or webhook actions (Slack, Teams, Discord, JSON)

queries

Database statements from db spans: time share, calls, slowest calls, N+1, by the fingerprint the database’s query insights use

  • GET /errors/api/projects/{id}/queries
    List a project’s database statements by total time: calls, mean and slowest call, time share, N+1 transactionserrors:GetEvents
  • GET /errors/api/queries
    Read one statement: what sampled requests saw, what the database measured (pg_stat_statements), charts, and the database at one request’s minuteerrors:GetEvents
  • GET /errors/api/projects/{id}/queries/all
    List every statement: measured by the connected databases (every call) and seen in traces, joined by fingerprinterrors:GetEvents

databases

Managed PostgreSQL databases connected to a project: its Queries tab reads their Query insights

release-health

Release health of a project: crash-free sessions and users, adoption, per release

auth-tokens

Tokens for sentry-cli and withSentryConfig

connections

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.