Skip to main content
Use Honeybadger through Corsair: one client, typed API calls. Honeybadger is an error tracker that also does uptime monitoring, cron and job check-ins, deploy tracking and event analytics. This plugin wraps the Data API v3. Create an API token in Honeybadger, then store it as the account’s api_key. It is sent as Authorization: Bearer <token>. Three token kinds work: a user API token (hbu_), an account API token (hba_) for automation, or an OAuth access token. A v2 personal auth token does not work with v3. Things to know before you call:
  • Pick the right region. Honeybadger runs a US app and an EU app, and an account lives in one of them. A US token is answered 401 by the EU host and the reverse. The plugin defaults to us; set the account’s region field to eu when the account is on eu-app.honeybadger.io (or pass region: 'eu' to the plugin in code, which applies to every tenant). The token prefix is the same in both, so it cannot be detected.
  • Project-scoped calls need project_id. Everything except projects.list, projects.create, occurrences.list, notices.get, account.* and token.get takes one. A project ID is a short opaque string such as Xk9mZp, not a number, and v3 IDs differ from the v2 ones. Get them from projects.list.
  • Errors branch on a code, not a message. A failure body is { error: { code, message, details } }. The plugin keeps status and code on the thrown error and drops the body, because a validation failure echoes the submitted values. details becomes text in the message, such as which field failed or which scope a 403 needed.
  • Time filters are Unix seconds. created_after, occurred_after and occurred_before take numbers, as the API documents. An ISO string is refused before the request is sent.
  • Bulk fault changes need a bound. faults.resolve, unresolve, ignore and unignore take either fault_ids or all: true. A request with neither is refused here, because the API answers 422 for it. dry_run: true reports what would change without changing it.
  • Pagination differs by collection. Numbered lists (projects, faults, environments, checkIns, sites, streams) take page and per_page, capped at 100. notices, comments and deploys take limit and a before or after cursor, which you read from links.older and links.newer. The rest window on time instead of a cursor: checkIns.events takes limit and created_before, sites.checks and sites.outages take limit, created_after and created_before, and faults.occurrences takes occurred_after and occurred_before.
  • Rate limits are 360 requests an hour per token. A 429 carries Retry-After and is retried three times. concurrent_request and streams_provisioning are also 429s, and both mean try again. The plugin reads Retry-After only, never X-RateLimit-Reset, because the budget resets on the hour, and waiting for that reset would hold the call for most of an hour.
  • A merged fault redirects. After a merge finishes, a read of the old ID answers 301 to the target and the old ID eventually 404s. A write against it answers 409 fault_merged with the target in details.
  • No inbound webhooks. Honeybadger sends no deliveries to an arbitrary URL, so this plugin registers no webhook route. Its notification integrations are per-project and configured in the web UI or through the integrations API, which this plugin does not wrap.
  • Deletes answer 204. They return { deleted: true } plus the IDs that were removed, because the provider sends no body to report.
What you get:
  • 62 typed API operations

Setup

1

Install

2

Add the plugin

corsair.ts
With multiTenancy: true, scope calls with corsair.withTenant(id). See Quick start for KEK + Hub keys, and Multi-tenancy for account isolation.
3

Choose authentication

4

Connect a tenant

Mint a connect link and send the tenant to it. Hub hosts the page and delivers the result to your app — see Connect / OAuth.

Example API calls

Read the unresolved faults in a project
Resolve one fault
See the full list on the API page.

What’s next

API reference

Every honeybadger.api.* operation with input and output types.

Connect / OAuth

createLink, Hub delivery, and tenant connect flows.

Use with agents

Expose this plugin’s operations as MCP tools.