canonical: https://jentic.com/apis/bugsnag.com/bugsnag

# BugSnag - Data Access API

Jentic publishes the only available OpenAPI specification for BugSnag - Data Access API, keeping it validated and agent-ready. BugSnag is an error monitoring and stability scoring platform from SmartBear, and the Data Access API gives programmatic read and write access to organisations, projects, errors, events, releases, comments, integrations, and saved searches. Across 141 endpoints it covers the full lifecycle from error triage to release health analysis. Use it to push BugSnag data into custom dashboards, automate triage workflows, configure integrations, and run organisation-wide health reports.

## For AI agents

Read and update BugSnag errors, events, projects, releases, comments, and integrations across 141 endpoints to drive triage and release health workflows.

## Scope

Does not handle SDK-side error reporting, billing, or session tracking ingestion - use for reading and managing errors, events, projects, integrations, and saved searches only.

## Capabilities

- List errors on a project, view an error's full detail, and bulk update or delete errors
- Browse the events behind an error, fetch the latest event, and pivot on event fields
- Comment on errors and update or delete those comments programmatically
- List, configure, test, and remove third-party integrations such as Jira or Slack on a project
- Manage saved searches and pull their usage summaries to power custom error views
- Read project trend data to compare error volume across releases or time windows
- List and create projects under an organisation and inspect organisation-level metadata

## Use cases

### Release Health Reporting

Generate post-deploy release health reports by querying GET /projects/{project_id}/trends and GET /projects/{project_id}/errors right after a release. Compare error counts and stability scores against the previous release window and flag regressions automatically. Saved searches can pre-define which errors qualify as release blockers, so the agent only acts on the right subset.

Example prompt: For project_id 12345, fetch trends for the last 24 hours and post a Slack message listing any error whose count grew more than 50% versus the prior window.

### Automated Error Triage

Build a triage bot that listens for new BugSnag errors and routes them. The agent uses GET /projects/{project_id}/errors with filter parameters to find new unassigned errors, applies PATCH /projects/{project_id}/errors/{error_id} to assign or change severity, and posts a comment via POST /projects/{project_id}/errors/{error_id}/comments referencing the responsible deploy.

Example prompt: List unassigned errors created in the last hour for project_id 12345, assign them to engineer alice, and post a comment with the build SHA from CI.

### Custom Integration Provisioning

Standardise project setup by configuring integrations through the API instead of clicking through the dashboard. POST /projects/{project_id}/configured_integrations attaches a Slack, Jira, or webhook integration, and POST /configured_integrations/{id}/test verifies it before going live. Use GET /integrations to discover what is supported.

Example prompt: Configure a Slack integration on a newly created BugSnag project pointing to channel #alerts, then run the test endpoint to confirm delivery.

### AI Agent Incident Responder via Jentic

An on-call agent connected through Jentic can be paged with an error_id, fetch the latest event, summarise the stack trace, and propose a fix or assignment. The agent searches Jentic for view a BugSnag error, loads the GET /projects/{project_id}/errors/{error_id} schema, and chains GET /errors/{error_id}/latest_event for the freshest event payload - all using a vault-stored Personal Auth Token.

Example prompt: Search Jentic for view a BugSnag error, load the schema, fetch the error and its latest event, and post a triage summary as a comment on the error.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /projects/{project_id}/errors | List errors on a project |
| PATCH | /projects/{project_id}/errors/{error_id} | Update an error |
| GET | /errors/{error_id}/latest_event | View the latest event for an error |
| POST | /projects/{project_id}/errors/{error_id}/comments | Comment on an error |
| GET | /projects/{project_id}/trends | List trend data for a project |
| POST | /saved_searches | Create a saved search |
| POST | /projects/{project_id}/configured_integrations | Configure an integration on a project |

## Key resources

- **Errors** — List, view, update, comment on, and delete grouped errors on a project
- **Events** — Inspect individual event payloads, the latest event for an error, and pivot values
- **Projects** — List, create, and configure projects under an organisation
- **Organisations** — Read organisation metadata and list integration connections
- **Saved Searches** — Create, manage, and read usage summaries for saved error searches
- **Integrations** — Discover supported integrations and configure them per project
- **Trends** — Pull error trend data for projects and individual errors
- **Comments** — Add, update, and delete comments on errors

## Why Jentic

- **Setup:** Wiring BugSnag by hand means learning its Personal Auth Token header against api.bugsnag.com and threading the project and error ids through every read, comment, and trend call yourself. Through Jentic you install once, import BugSnag from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** BugSnag puts the project and error ids in the URL path (/projects/{project_id}/errors/{error_id}/...), so a rule can pin your agent to one project: it can read errors, post triage comments, and view trends there and nothing else. You choose the operations it may call, so it can read and comment on errors without being able to add configured integrations unless you add that.
- **Credential handling:** Your BugSnag Personal Auth Token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list BugSnag errors' or 'post a triage comment', and Jentic returns the matching BugSnag operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Bugfender API** — Bugfender focuses on raw remote logging from mobile apps; BugSnag focuses on grouped error monitoring and stability scoring.
- **BugHerd API** — BugHerd captures human-reported visual bugs while BugSnag captures runtime errors automatically.
- **Buildkite API** — Buildkite ships releases whose stability BugSnag then measures.

## FAQ

### Why is there no official OpenAPI spec for BugSnag - Data Access API?

BugSnag does not publish a maintained OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BugSnag - Data Access API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the BugSnag Data Access API use?

BugSnag uses a Personal Auth Token sent in the Authorization header with the prefix token, for example Authorization: token my_auth_token. Through Jentic, the token is stored encrypted in the vault and the header is constructed at execution time, never exposing the secret to the agent.

### Can I update or resolve a BugSnag error through the API?

Yes. PATCH /projects/{project_id}/errors/{error_id} updates a single error's status, severity, or assignment, while PATCH /projects/{project_id}/errors performs bulk updates across many errors at once. DELETE on the same paths removes errors permanently.

### How do I configure a Slack or Jira integration through the BugSnag API?

Call GET /integrations to list supported integration types, then POST /projects/{project_id}/configured_integrations with the integration parameters. Use POST /configured_integrations/{id}/test to verify the configuration is wired correctly before relying on it.

### What are the rate limits for the BugSnag Data Access API?

BugSnag rate-limits the Data Access API per organisation, but the OpenAPI spec does not encode a hard quota. Add retry-with-backoff for HTTP 429 responses, and prefer saved searches plus trend endpoints over high-frequency event polling.

### How do I list BugSnag errors from an AI agent through Jentic?

Run pip install jentic and authenticate with your ak_* key. Search Jentic with list errors on a BugSnag project, load the GET /projects/{project_id}/errors operation, and execute it with project_id. Jentic injects the Authorization header from your stored Personal Auth Token.

### Can I limit what my agent is allowed to do with the BugSnag Data Access API?

Yes. Because BugSnag carries the project and error ids in the URL path (/projects/{project_id}/errors/{error_id}/...), a rule in your own self-hosted Jentic One instance can pin your agent to a single project so it reads errors, posts triage comments, and views trends there and nowhere else. You also choose exactly which operations it may call, so you can let it list errors via GET /projects/{project_id}/errors and comment through POST /projects/{project_id}/errors/{error_id}/comments while blocking it from configuring integrations with POST /projects/{project_id}/configured_integrations. Your rules decide which operations and which stored credential the agent may use, so it never gains access you did not grant.