Airbrake API

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

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey19 EndpointsREST

For Agents

Manage Airbrake projects and error groups, record deploys, and upload source maps for production error tracking.

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:
"list airbrake error groups"

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

Capabilities

What an agent can do with Airbrake API API.

List, fetch, mute, and delete error groups across one or more projects

Record deploy events with environment and revision metadata for release correlation

Upload, list, and delete source maps so minified stack traces resolve cleanly

Pull project-level activity feeds for audit logs and dashboards

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 collects errors generated by other applications and aggregates the results for review. This core spec exposes 19 endpoints across the v4 management surface plus v3 notice creation and v5 performance reporting, covering projects, error groups, deploys, source maps, and project activity feeds. Authentication uses an API key passed as the 'key' query parameter.

Use Cases

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

★ Release Health Monitoring

After every CI release, post a deploy event to /projects/{PROJECT_ID}/deploys, then poll error group stats to detect post-release regressions. The /projects/{PROJECT_ID}/activities feed gives a chronological record that ties deploys, mutes, and resolutions together for release retrospectives.

Record a deploy on project 12345 with environment production and revision sha1234, then check error group stats 30 minutes later and flag any group with rate increase greater than 50%

Error Group Triage Workflow

Automate first-line triage by pulling fresh error groups, fetching stats, and muting groups that match a known-noise pattern. PUT /projects/{PROJECT_ID}/groups/{GROUP_ID}/muted hides a group, /unmuted reverses it, and DELETE removes resolved groups permanently.

List error groups for project 12345, mute any group whose message matches 'NetworkTimeout' and whose count is below 10, and leave a comment in Slack listing what was muted

Source Map Lifecycle Management

Keep source maps aligned with the bundles in production. Upload via POST /projects/{PROJECT_ID}/sourcemaps after every build, list current maps with GET to detect drift, and DELETE old ones once the corresponding bundle is rotated out of the CDN.

Upload sourcemap.js.map for project 12345 with bundle URL https://cdn.example.com/app.v8.js, then delete any previously uploaded source map for app.v6.js

AI Agent Error Triage Assistant

Through Jentic, an agent can pull the freshest error groups, summarise the stack traces, and propose a deploy or mute action. The Airbrake API key stays in the Jentic vault and the agent only handles scoped operations.

Search Jentic for 'list airbrake error groups', load the schema, fetch groups for project 12345, summarise the top 3 by occurrence count, and propose mute actions for the agent to confirm

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/projects

List projects

GET

/projects/{PROJECT_ID}/groups

List error groups for a project

PUT

/projects/{PROJECT_ID}/groups/{GROUP_ID}/muted

Mute an error group

POST

/projects/{PROJECT_ID}/deploys

Record a deployment

POST

/projects/{PROJECT_ID}/sourcemaps

Upload a source map

GET

/projects/{PROJECT_ID}/stats

Get project statistics

GET

/projects/{PROJECT_ID}/activities

List project activity

GET

/projects

List projects

GET

/projects/{PROJECT_ID}/groups

List error groups for a project

PUT

/projects/{PROJECT_ID}/groups/{GROUP_ID}/muted

Mute an error group

POST

/projects/{PROJECT_ID}/deploys

Record a deployment

POST

/projects/{PROJECT_ID}/sourcemaps

Upload a source map

Why though Jentic?

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

Credential isolation

The Airbrake API key is stored encrypted in the Jentic vault. Jentic appends it as the 'key' query parameter at call time, so it never appears in agent prompts or logs.

Intent-based discovery

Agents search Jentic by intent (e.g. 'mute an airbrake error group') and Jentic returns the matching operation and schema directly, no doc browsing required.

Time to first call

Direct Airbrake integration: 1-2 days for auth, project scoping, and CI source map uploads. Through Jentic: under 1 hour.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Sentry API

Error tracking with broader language SDK coverage and built-in tracing

Choose Sentry when distributed tracing or session replay matters as much as the error stream

Alternative

Rollbar API

Real-time error tracking with per-item ownership and assignment workflows

Choose Rollbar when individual error item ownership matters more than group aggregation

Alternative

Bugsnag API

Stability score-driven error monitoring with strong mobile SDK support

Choose Bugsnag for mobile-first applications where stability scores guide releases

Complementary

GitHub API

Pair Airbrake deploy events with GitHub releases for end-to-end traceability

Use GitHub alongside Airbrake when the agent needs to map errors back to commits and PRs

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 authenticates via an API key passed as the 'key' query parameter. Jentic stores the key encrypted in the vault and appends it transparently, so the raw key never enters agent context.

Can I mute an error group with the Airbrake API?

Yes. PUT /projects/{PROJECT_ID}/groups/{GROUP_ID}/muted mutes the group, hiding it from default group listings. Use the matching /unmuted endpoint to reverse the action.

What are the rate limits for the Airbrake API?

The spec does not declare formal rate limits. Management endpoints respond best to burst-and-pause use; for high-volume error ingestion, use the v3 notices endpoint rather than polling group listings.

How do I record a deploy with the Airbrake API through Jentic?

Run pip install jentic, search Jentic for 'record airbrake deploy', load the schema for POST /projects/{PROJECT_ID}/deploys, then execute with the project ID, environment, and revision. Jentic appends the API key automatically.

Can I use the Airbrake API to upload source maps as part of CI?

Yes. POST /projects/{PROJECT_ID}/sourcemaps accepts the source map file and the bundle URL it relates to, so a CI step can upload after every successful build to keep stack-trace resolution accurate.