Airbrake API

Name: Airbrake API API
Brand: Airbrake API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey27 EndpointsREST

For Agents

Track errors, post deploys, query performance metrics, and manage source maps for applications monitored by Airbrake.

Quickstart

Get started with Airbrake API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"submit an airbrake error notice"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Airbrake API API.

Submit error notices to /api/v3/projects/{project_id}/notices for ingestion into the live error stream

Pull, mute, and delete error groups across projects to triage incidents

Record deployments with /api/v4/projects/{project_id}/deploys to correlate releases with error rates

Upload and manage source maps so stack traces resolve to original sources

GET STARTED

Start building with Airbrake API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Airbrake API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Airbrake API, keeping it validated and agent-ready. Airbrake is an error tracking, performance monitoring, and deploy tracking platform for production applications. This expanded spec exposes 27 endpoints spanning v3 error notice ingestion, v4 project and group management, v5 performance monitoring routes, queue stats, and database query stats. Authentication uses an API key passed as the 'key' query parameter.

Use Cases

Patterns agents use Airbrake API API for, with concrete tasks.

★ Deploy-Error Correlation

Tag every release with a deploy event so spikes in errors are linked back to the change that introduced them. POST /api/v4/projects/{project_id}/deploys at the end of every CI release, then surface the activity feed and group stats to engineers reviewing post-deploy health.

Create a deploy on project 12345 with environment production and revision abc123, then list any error groups created in the last 30 minutes

Source Map Upload Pipeline

Resolve minified JavaScript stack traces back to original source by uploading source maps after every build. POST /api/v4/projects/{project_id}/sourcemaps uploads the map, list and delete operations let you prune stale maps as old bundles are replaced.

Upload sourcemap app.min.js.map for project 12345 referencing the bundle URL https://cdn.example.com/app.min.js

Error Group Triage Dashboard

Build an internal dashboard listing the top error groups across all projects with mute, unmute, and delete actions. GET /api/v4/groups returns groups across the account, /api/v4/projects/{project_id}/groups/{group_id}/stats provides per-group counts, and PUT /api/v4/projects/{project_id}/groups/{group_id}/muted hides resolved noise.

List error groups across all projects, then mute group 999 in project 12345 and record a justification note

AI Agent Incident Responder

An agent watching Airbrake can ingest new error groups, fetch their stats, summarise the stack trace, and post a release deploy event when a fix ships — all without operator intervention. Through Jentic the API key stays in the vault and only scoped operations are exposed.

Search Jentic for 'list airbrake error groups', load the schema, fetch new groups for project 12345, and mute any group with under 5 occurrences in the last hour

Key Endpoints

27 endpoints — jentic publishes the only available openapi specification for airbrake api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v3/projects/{project_id}/notices

Submit an error notice

GET

/api/v4/projects

List projects

POST

/api/v4/projects/{project_id}/deploys

Record a deployment

GET

/api/v4/projects/{project_id}/groups

List error groups for a project

PUT

/api/v4/projects/{project_id}/groups/{group_id}/muted

Mute an error group

POST

/api/v4/projects/{project_id}/sourcemaps

Upload a source map

PUT

/api/v5/projects/{project_id}/routes-stats

Report route performance stats

POST

/api/v3/projects/{project_id}/notices

Submit an error notice

GET

/api/v4/projects

List projects

POST

/api/v4/projects/{project_id}/deploys

Record a deployment

GET

/api/v4/projects/{project_id}/groups

List error groups for a project

PUT

/api/v4/projects/{project_id}/groups/{group_id}/muted

Mute an error group

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Airbrake 'key' query parameter is stored encrypted in the Jentic vault. Agents call Airbrake through Jentic with scoped tokens — the raw key is never appended client-side or visible to the model.

Intent-based discovery

Agents search Jentic by intent (e.g. 'record an airbrake deploy') and Jentic returns the matching operation with its input schema, so the agent does not browse Airbrake docs.

Time to first call

Direct Airbrake integration: 1-2 days for auth, multi-version path handling (v3/v4/v5), and source map upload. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Sentry API

Error tracking and performance monitoring with broader language SDK support

Choose Sentry when the agent needs distributed tracing or session replay alongside errors

Alternative

Rollbar API

Real-time error tracking with deploy correlation and assignment workflows

Choose Rollbar when the agent values per-error item ownership and assignment over Airbrake's group model

Alternative

Bugsnag API

Stability score-driven error monitoring with strong mobile SDK coverage

Choose Bugsnag when targeting mobile apps where stability scores guide release decisions

Complementary

New Relic API

Full-stack APM that pairs with Airbrake for error-and-metric correlation

Use New Relic alongside Airbrake when the agent also needs infrastructure and APM telemetry

FAQs

Specific to using Airbrake API API through Jentic.

Why is there no official OpenAPI spec for Airbrake API?

Airbrake does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Airbrake API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Airbrake API use?

Airbrake uses an API key passed as the 'key' query parameter on every request. Jentic stores the key encrypted in the vault and appends it at call time, so the agent does not see the raw value.

Can I record deploys with the Airbrake API?

Yes. POST /api/v4/projects/{project_id}/deploys accepts environment, revision, repository, username, and version fields, and the deploy is then linked to subsequent error groups for release-correlation analysis.

What are the rate limits for the Airbrake API?

Spec metadata does not declare hard rate limits. Notice ingestion (/api/v3/projects/{project_id}/notices) accepts high volumes; management endpoints under /api/v4 are best used in burst-and-pause patterns.

How do I upload a source map with the Airbrake API through Jentic?

Run pip install jentic, search Jentic for 'upload airbrake source map', load the schema for POST /api/v4/projects/{project_id}/sourcemaps, then execute with the project ID, source map file, and original bundle URL. Jentic injects the API key automatically.

Does the Airbrake API support performance monitoring as well as error tracking?

Yes. The v5 endpoints under /api/v5/projects/{project_id}/routes-stats, /routes-breakdowns, /queries-stats, and /queues-stats accept performance telemetry from instrumented services so route latency and database query timing are reportable alongside errors.