> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Honeybadger

The Honeybadger connector lets your AI agent act in each user's Honeybadger account. Each user connects their own Honeybadger access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 60 tools.

**Authentication:** Bearer Token
**Categories:** Developer Tools, Monitoring
**Tools:** 60: 36 read, 19 write, 5 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=HONEYBADGER)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Honeybadger connection

   In **AgentKit > Connections**, create a Honeybadger connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'honeybadger'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Honeybadger:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'honeybadger_account_get',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "honeybadger"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Honeybadger:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="honeybadger_account_get",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Honeybadger credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'honeybadger_account_get',
  toolInput: {},
  connector: 'honeybadger',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="honeybadger_account_get",
    tool_input={},
    connection_name="honeybadger",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `honeybadger_account_get`

Get Account · Read-only

Get the Honeybadger account the token belongs to.
Returns the account id, name, plan and settings.
Use honeybadger_account_usage_get for usage numbers.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `honeybadger_account_usage_get`

Get Account Usage · Read-only

Get usage statistics for the account, such as error, Insights and uptime volume against the plan.
Returns usage counts and plan limits for the current period.
Use honeybadger_account_get for the account's name and plan.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `honeybadger_alarm_get`

Get Insights Alarm · Read-only

Get one Insights alarm.
Returns its query, evaluation schedule, trigger_config and current state.
Use honeybadger_alarms_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `alarm_id` (`string`, required): ID of the Insights alarm. Get it from honeybadger_alarms_list. Example: Al3hJk.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"alarm_id":"<alarm_id>","project_id":"<project_id>"}`

### `honeybadger_alarm_history_list`

List Alarm History · Read-only

List an Insights alarm's trigger history, newest first, 25 per page.
Returns each trigger's state, result and timestamp.
Use honeybadger_alarm_get for the alarm's settings.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `alarm_id` (`string`, required): ID of the Insights alarm. Get it from honeybadger_alarms_list. Example: Al3hJk.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.

Example input: `{"alarm_id":"<alarm_id>","project_id":"<project_id>"}`

### `honeybadger_alarms_list`

List Insights Alarms · Read-only

List every Insights alarm on a project.
Returns each alarm's id, name, query, trigger configuration and state.
Use honeybadger_alarm_history_list for when an alarm fired.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_check_in_events_list`

List Check-In Events · Read-only

List a check-in's state-change events (reporting, missing, paused), newest first.
Returns each event's state, created_at and reported payload, plus an older cursor link.
Use this to see when a job missed its schedule.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `check_in_id` (`string`, required): ID of the check-in monitor. Get it from honeybadger_check_ins_list. Example: Ci5xWq.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `created_before` (`number`, optional): Only items created before this Unix timestamp (seconds, not ISO 8601). Take it from links.older; fractional seconds count. Example: 1731024000.
- `limit` (`integer`, optional): Maximum items to return, up to 100. Defaults to 25. Example: 25.

Example input: `{"check_in_id":"<check_in_id>","project_id":"<project_id>"}`

### `honeybadger_check_in_get`

Get Check-In · Read-only

Get one check-in monitor.
Returns its schedule, state, report_url, reported_at and expected_at.
Use honeybadger_check_ins_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `check_in_id` (`string`, required): ID of the check-in monitor. Get it from honeybadger_check_ins_list. Example: Ci5xWq.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"check_in_id":"<check_in_id>","project_id":"<project_id>"}`

### `honeybadger_check_ins_list`

List Check-Ins · Read-only

List a project's check-in monitors for scheduled jobs.
Returns each check-in's id, name, slug, schedule, state (pending, reporting, missing or paused), last report and next expected time.
Use honeybadger_check_in_events_list for a check-in's history.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_dashboard_get`

Get Insights Dashboard · Read-only

Get one Insights dashboard with its widgets.
Returns the title, widget configs with their BadgerQL queries, and layout.
Run a widget's query with honeybadger_insights_query_run.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `dashboard_id` (`string`, required): ID of the Insights dashboard. Get it from honeybadger_dashboards_list. Example: Db8nQw.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"dashboard_id":"<dashboard_id>","project_id":"<project_id>"}`

### `honeybadger_dashboards_list`

List Insights Dashboards · Read-only

List a project's Insights dashboards.
Returns each dashboard's id, title and widgets.
Use honeybadger_dashboard_get for one dashboard.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_deploys_list`

List Deploys · Read-only

List a project's recorded deploys, newest first, optionally by environment or deploy username.
Returns each deploy's id, environment, revision, repository, local_username and created_at, plus cursor links.
Use the environment filter to see one environment's deploys.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `after` (`string`, optional): Cursor for newer items, taken from the links.newer URL of the previous response. Example: eyJpZCI6IjEyMyJ9.
- `before` (`string`, optional): Cursor for older items, taken from the links.older URL of the previous response. Example: eyJpZCI6IjEyMyJ9.
- `environment` (`string`, optional): Exact environment name to match. Ignored when blank. Example: production.
- `limit` (`integer`, optional): Maximum items to return, up to 100. Defaults to 25. Example: 25.
- `local_username` (`string`, optional): Exact deploy username to match. Ignored when blank; combines with environment when both are provided. Example: deploybot.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_environments_list`

List Environments · Read-only

List a project's environments, such as production and staging.
Returns each environment's id, name and notification settings.
Use the names as the environment filter on the occurrence and deploy tools.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_fault_affected_users_list`

List Fault Affected Users · Read-only

List the up to 500 users a fault affected most, ranked by notice count.
Returns each user identifier and its count.
Use q to count only matching notices.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `q` (`string`, optional): Error search query in the syntax of Honeybadger's web UI, such as environment:production, is:resolved or class:ArgumentError. Prefix a filter with - to negate it. Example: environment:production -is:resolved.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_comments_list`

List Fault Comments · Read-only

List the comments on a fault.
Returns each comment's id, body, author and timestamps, plus cursor links.
Use honeybadger_fault_comment_create to add one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `after` (`string`, optional): Cursor for newer items, taken from the links.newer URL of the previous response. Example: eyJpZCI6IjEyMyJ9.
- `before` (`string`, optional): Cursor for older items, taken from the links.older URL of the previous response. Example: eyJpZCI6IjEyMyJ9.
- `limit` (`integer`, optional): Maximum items to return, up to 100. Defaults to 25. Example: 25.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_get`

Get Fault · Read-only

Get one fault (error group) by ID.
Returns the fault's class, message, component, action, environment, counts, state, assignee, tags and URL.
Use honeybadger_fault_notices_list for backtraces and request context.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_notices_list`

List Fault Notices · Read-only

List a fault's notices (individual error occurrences), newest first.
Returns each notice's id, message, backtrace, request, context, environment and created_at, plus older and newer cursor links.
Use this to read backtraces. Use honeybadger_notice_get for one notice by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `after` (`string`, optional): Cursor for newer items, taken from the links.newer URL of the previous response. Example: eyJpZCI6IjEyMyJ9.
- `before` (`string`, optional): Cursor for older items, taken from the links.older URL of the previous response. Example: eyJpZCI6IjEyMyJ9.
- `limit` (`integer`, optional): Maximum items to return, up to 100. Defaults to 25. Example: 25.
- `unmapped` (`boolean`, optional): Return the backtrace as the client reported it instead of source-mapped. Accepts true/false, 1/0, yes/no, on/off. Defaults to false. Example: true.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_occurrences_get`

Get Fault Occurrence Counts · Read-only

Get a fault's occurrence counts over a time window (the last hour by default), bucketed by interval.
Returns [timestamp, count] buckets and meta.window and meta.interval_seconds.
Use honeybadger_project_occurrences_get for the whole project.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `occurred_after` (`number`, optional): Only occurrences after this Unix timestamp (seconds, not ISO 8601). A value before the project's retention window is moved up to it. On the fault list, occurrence counts cover this window. Example: 1730419200.
- `occurred_before` (`number`, optional): Only occurrences before this Unix timestamp (seconds, not ISO 8601). Example: 1731024000.
- `q` (`string`, optional): Error search query in the syntax of Honeybadger's web UI, such as environment:production, is:resolved or class:ArgumentError. Prefix a filter with - to negate it. Example: environment:production -is:resolved.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_faults_list`

List Faults · Read-only

List a project's faults (grouped errors), filtered with error search and time windows and sorted by recency or frequency.
Returns each fault's id, klass, message, environment, notices_count, resolved and ignored state, assignee, tags and timestamps, plus pagination links.
Use this to find errors. Use honeybadger_fault_get for one fault and honeybadger_fault_notices_list for its occurrences.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `created_after` (`number`, optional): Only faults first seen after this Unix timestamp (seconds, not ISO 8601). Example: 1730419200.
- `occurred_after` (`number`, optional): Only occurrences after this Unix timestamp (seconds, not ISO 8601). A value before the project's retention window is moved up to it. On the fault list, occurrence counts cover this window. Example: 1730419200.
- `occurred_before` (`number`, optional): Only occurrences before this Unix timestamp (seconds, not ISO 8601). Example: 1731024000.
- `order` (`string`, optional): recent sorts by last occurrence, frequent by occurrence count. Left out, by creation time. Example: recent. One of: `recent`, `frequent`.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.
- `q` (`string`, optional): Error search query in the syntax of Honeybadger's web UI, such as environment:production, is:resolved or class:ArgumentError. Prefix a filter with - to negate it. Example: environment:production -is:resolved.
- `sort` (`string`, optional): Direction for order. Defaults to desc for recent and frequent, asc for creation time. Example: asc. One of: `asc`, `desc`.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_faults_summary_get`

Get Fault Counts · Read-only

Get a project's fault counts grouped by environment and by resolved or ignored state, with the same filters as the fault list.
Returns total, environment and status counts.
Use this for an overview. Use honeybadger_faults_list for the faults themselves.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `created_after` (`number`, optional): Only faults first seen after this Unix timestamp (seconds, not ISO 8601). Example: 1730419200.
- `occurred_after` (`number`, optional): Only count faults that occurred after this Unix timestamp. Example: 1730419200.
- `occurred_before` (`number`, optional): Only count faults that occurred before this Unix timestamp. Example: 1731024000.
- `q` (`string`, optional): Error search query in the syntax of Honeybadger's web UI, such as environment:production, is:resolved or class:ArgumentError. Prefix a filter with - to negate it. Example: environment:production -is:resolved.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_insights_query_run`

Run Insights Query · Read-only

Run a BadgerQL query against a project's Insights event streams. It changes nothing.
Returns the result rows, field metadata and query statistics.
Use this to analyse logs and events. Use honeybadger_streams_list to pick stream_ids.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `query` (`string`, required): BadgerQL query. Example: fields @ts, message | filter event_type::str == "error" | sort @ts desc | limit 20.
- `stream_ids` (`array`, optional): Streams to search. Omit it, or pass an empty array, to search every stream on the project. Every ID must belong to this project; repeated IDs are deduplicated. Example: ["St1aBc"]
- `timezone` (`string`, optional): Timezone for time bucketing and display. Example: America/New_York.
- `ts` (`string`, optional): Time range for the query. Example: PT3H.

Example input: `{"project_id":"<project_id>","query":"<query>"}`

### `honeybadger_notice_get`

Get Notice · Read-only

Get one error notice by its ID, without needing its project or fault.
Returns the notice's message, backtrace, request, context, environment and fault and project IDs.
Use honeybadger_fault_notices_list to browse a fault's notices.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `uuid` (`string`, required): ID (UUID) of the notice, from honeybadger_fault_notices_list or a notice link. Example: 0b5a0c9e-6d2f-4f5e-9a3b-1c2d3e4f5a6b.
- `unmapped` (`boolean`, optional): Return the backtrace as the client reported it instead of source-mapped. Accepts true/false, 1/0, yes/no, on/off. Defaults to false. Example: true.

Example input: `{"uuid":"<uuid>"}`

### `honeybadger_project_get`

Get Project · Read-only

Get one project by ID.
Returns the project's name, language, settings, environments and counts.
Use honeybadger_projects_list to find the ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_project_occurrences_get`

Get Project Occurrence Counts · Read-only

Get a project's error notice counts over an hour, day, week or month, one count per interval.
Returns a list of [timestamp, count] buckets, with 0 for quiet intervals.
Use honeybadger_projects_occurrences_get for every project at once.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `environment` (`string`, optional): Only count notices from faults in this environment. Example: production.
- `period` (`string`, optional): Window to report over. Both ends are inclusive: hour gives 61 one-minute buckets, day 25 hourly, week 8 daily, month 31 daily. Defaults to hour. Example: hour. One of: `hour`, `day`, `week`, `month`.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_project_stats_get`

Get Project Stats · Read-only

Get statistics for a project.
Returns the project's notice counts by time bucket and environment.
Use honeybadger_project_occurrences_get for counts over a set period.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_projects_list`

List Projects · Read-only

List the projects the token can access, optionally matching an exact name.
Returns each project's id, name, language, environments and settings, plus pagination links.
Use this to find a project_id, which almost every other tool needs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, optional): Exact project name to match. Omit or leave blank to list all accessible projects. Example: Billing API.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.

Example input: `{}`

### `honeybadger_projects_occurrences_get`

Get Occurrence Counts for All Projects · Read-only

Get error notice counts over a period for every project the token can read, ordered by project name.
Returns per-project lists of [timestamp, count] buckets.
Use honeybadger_project_occurrences_get for one project.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `environment` (`string`, optional): Only count notices from faults in this environment. Example: production.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.
- `period` (`string`, optional): Window to report over. Both ends are inclusive: hour gives 61 one-minute buckets, day 25 hourly, week 8 daily, month 31 daily. Defaults to hour. Example: hour. One of: `hour`, `day`, `week`, `month`.

Example input: `{}`

### `honeybadger_site_checks_list`

List Uptime Checks · Read-only

List a site's uptime check results, newest first, optionally in a time window.
Returns each check's location, up state, status code, duration and timestamp, plus cursor links.
Use honeybadger_site_outages_list for outages only.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `site_id` (`string`, required): UUID of the uptime monitoring site. Get it from honeybadger_sites_list. Example: 9f8b6d2e-4c1a-4b7f-9e35-2a6c8d0f1b47.
- `created_after` (`number`, optional): With created_before, limits the list to a window. Alone, returns the items just after it, newest first. A Unix timestamp (seconds, not ISO 8601). Take it from links.newer; fractional seconds count. Example: 1730419200.
- `created_before` (`number`, optional): Only items created before this Unix timestamp (seconds, not ISO 8601). Take it from links.older; fractional seconds count. Example: 1731024000.
- `limit` (`integer`, optional): Maximum items to return, up to 100. Defaults to 25. Example: 25.

Example input: `{"project_id":"<project_id>","site_id":"<site_id>"}`

### `honeybadger_site_get`

Get Uptime Site · Read-only

Get one uptime monitoring site.
Returns the site's url, state, last check time and all check settings.
Use honeybadger_sites_list to find the site ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `site_id` (`string`, required): UUID of the uptime monitoring site. Get it from honeybadger_sites_list. Example: 9f8b6d2e-4c1a-4b7f-9e35-2a6c8d0f1b47.

Example input: `{"project_id":"<project_id>","site_id":"<site_id>"}`

### `honeybadger_site_outages_list`

List Uptime Outages · Read-only

List a site's outages, newest first, optionally in a time window.
Returns each outage's down_at, up_at, status and reason.
Use honeybadger_site_checks_list for every individual check.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `site_id` (`string`, required): UUID of the uptime monitoring site. Get it from honeybadger_sites_list. Example: 9f8b6d2e-4c1a-4b7f-9e35-2a6c8d0f1b47.
- `created_after` (`number`, optional): With created_before, limits the list to a window. Alone, returns the items just after it, newest first. A Unix timestamp (seconds, not ISO 8601). Take it from links.newer; fractional seconds count. Example: 1730419200.
- `created_before` (`number`, optional): Only items created before this Unix timestamp (seconds, not ISO 8601). Take it from links.older; fractional seconds count. Example: 1731024000.
- `limit` (`integer`, optional): Maximum items to return, up to 100. Defaults to 25. Example: 25.

Example input: `{"project_id":"<project_id>","site_id":"<site_id>"}`

### `honeybadger_sites_list`

List Uptime Sites · Read-only

List a project's uptime monitoring sites.
Returns each site's id, name, url, state (up, down or pending), frequency, locations and match settings.
Use honeybadger_site_outages_list or honeybadger_site_checks_list for a site's history.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_status_page_incident_get`

Get Status Page Incident · Read-only

Get one status page incident with its updates.
Returns the title, build_type, current status and severity, and every update.
Use honeybadger_status_page_incident_update_create to post a new update.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `incident_id` (`string`, required): ID of the status page incident. Get it from honeybadger_status_page_incidents_list. Example: In3pKr.
- `status_page_id` (`string`, required): ID of the status page. Get it from honeybadger_status_pages_list. Example: Sp7bMq.

Example input: `{"incident_id":"<incident_id>","status_page_id":"<status_page_id>"}`

### `honeybadger_status_page_incidents_list`

List Status Page Incidents · Read-only

List a status page's incidents, newest first.
Returns each incident's id, title, build_type, current status and severity, and its updates.
Use honeybadger_status_page_incident_create to open one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `status_page_id` (`string`, required): ID of the status page. Get it from honeybadger_status_pages_list. Example: Sp7bMq.
- `after` (`string`, optional): Cursor for newer items, taken from the links.newer URL of the previous response. Example: eyJpZCI6IjEyMyJ9.
- `before` (`string`, optional): Cursor for older items, taken from the links.older URL of the previous response. Example: eyJpZCI6IjEyMyJ9.
- `limit` (`integer`, optional): Maximum items to return, up to 100. Defaults to 25. Example: 25.

Example input: `{"status_page_id":"<status_page_id>"}`

### `honeybadger_status_pages_list`

List Status Pages · Read-only

List the account's status pages.
Returns each status page's id, name, URL and the sites and check-ins it shows.
Use honeybadger_status_page_incidents_list for a page's incidents.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.

Example input: `{}`

### `honeybadger_streams_list`

List Event Streams · Read-only

List a project's Insights event streams: default (events your apps send) and internal (errors, deploys, uptime and check-ins).
Returns each stream's id, name and slug.
Use the IDs as stream_ids in honeybadger_insights_query_run.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_teams_list`

List Teams · Read-only

List the account's teams, optionally matching an exact name.
Returns each team's id, name and project_ids.
Use a team_id when creating a project.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `name` (`string`, optional): Exact team name to match. Omit or leave blank to list all accessible teams. Example: Billing API.
- `page` (`integer`, optional): Page number, starting at 1. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Items per page. Defaults to 25. Example: 25.

Example input: `{}`

### `honeybadger_token_get`

Get Current Token · Read-only

Get the API token making the request and what it can reach.
Returns the token kind, its account_id, its scopes and the project_ids it can access.
Use this first to check which projects and scopes the connected token has.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `honeybadger_check_in_create`

Create Check-In · Write

Create a check-in monitor that alerts when a scheduled job stops reporting, on a simple period or a cron schedule.
Returns the check-in with its id and report_url for the job to request.
Set report_period for simple schedules, or cron_schedule and cron_timezone for cron.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `cron_schedule` (`string`, optional): Cron expression, required when schedule_type is cron. Example: 0 2 * * *.
- `cron_timezone` (`string`, optional): Timezone the cron schedule is evaluated in. A time zone name as the web app lists them, not an IANA identifier — Central Time (US & Canada), not America/Chicago, which is rejected. Required when schedule_type is cron. Null resets it to UTC. Example: UTC.
- `grace_period` (`string`, optional): How long after the expected time before the check-in is considered missing. Same format as report_period; zero is 00:00:00. Null resets it to zero. Example: 15 minutes.
- `name` (`string`, optional): Display name. Null clears it; an unnamed check-in shows its ID. Example: Billing API.
- `report_period` (`string`, optional): How often a report is expected, for simple schedules. Required unless schedule_type is cron, and may not be zero. A duration such as 5 minutes, 1 hour 30 minutes or 01:30:00. Returned in long form: 1 week comes back as 7 days. Example: 1 day.
- `schedule_type` (`string`, optional): simple expects a report every report_period; cron expects reports on cron_schedule. Switching to simple clears cron_schedule; switching to cron clears report_period. Defaults to simple. Example: simple. One of: `simple`, `cron`.
- `slug` (`string`, optional): Short identifier used in the check-in's reporting URL. Null clears it. Renaming it breaks jobs reporting to …/check_in/<ingestion key>/<slug> and changes how PUT /check_ins matches this check-in. Example: nightly-billing.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_check_in_update`

Update Check-In · Write

Update a check-in's name, slug or schedule; send only the fields to change.
Returns the updated check-in.
Changing the slug breaks jobs that report to the old slug URL.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `check_in_id` (`string`, required): ID of the check-in monitor. Get it from honeybadger_check_ins_list. Example: Ci5xWq.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `cron_schedule` (`string`, optional): Cron expression, required when schedule_type is cron. Example: 0 2 * * *.
- `cron_timezone` (`string`, optional): Timezone the cron schedule is evaluated in. A time zone name as the web app lists them, not an IANA identifier — Central Time (US & Canada), not America/Chicago, which is rejected. Required when schedule_type is cron. Null resets it to UTC. Example: UTC.
- `grace_period` (`string`, optional): How long after the expected time before the check-in is considered missing. Same format as report_period; zero is 00:00:00. Null resets it to zero. Example: 15 minutes.
- `name` (`string`, optional): Display name. Null clears it; an unnamed check-in shows its ID. Example: Billing API.
- `report_period` (`string`, optional): How often a report is expected, for simple schedules. Required unless schedule_type is cron, and may not be zero. A duration such as 5 minutes, 1 hour 30 minutes or 01:30:00. Returned in long form: 1 week comes back as 7 days. Example: 1 day.
- `schedule_type` (`string`, optional): simple expects a report every report_period; cron expects reports on cron_schedule. Switching to simple clears cron_schedule; switching to cron clears report_period. Defaults to simple. Example: simple. One of: `simple`, `cron`.
- `slug` (`string`, optional): Short identifier used in the check-in's reporting URL. Null clears it. Renaming it breaks jobs reporting to …/check_in/<ingestion key>/<slug> and changes how PUT /check_ins matches this check-in. Example: nightly-billing.

Example input: `{"check_in_id":"<check_in_id>","project_id":"<project_id>"}`

### `honeybadger_fault_assign`

Assign Fault · Write

Assign a fault to a user on the project.
Returns the fault with its new assignee.
Use honeybadger_fault_unassign to clear the assignee.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `assignee_id` (`string`, required): ID of a user on the project. To unassign, DELETE the same path. Example: Us9tPq.
- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"assignee_id":"<assignee_id>","fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_comment_create`

Create Fault Comment · Write

Add a comment to a fault. @mentions notify the named project members.
Returns the created comment.
Use honeybadger_fault_comment_update to edit it later.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body` (`string`, required): The comment text. @mentions notify the named project members. Example: Fixed in #482, deploying now. @alice can you verify?.
- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"body":"<body>","fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_comment_update`

Update Fault Comment · Write

Replace the text of a comment on a fault.
Returns the updated comment.
Use honeybadger_fault_comments_list to find the comment ID.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `body` (`string`, required): The comment text. @mentions notify the named project members. Example: Fixed in #482, deploying now. @alice can you verify?.
- `comment_id` (`string`, required): ID of the comment on the fault. Get it from honeybadger_fault_comments_list. Example: Cm4vRt.
- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"body":"<body>","comment_id":"<comment_id>","fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_snooze`

Snooze Fault · Write

Snooze a fault's notifications for an hour, day or week, or for 10, 100 or 1000 more occurrences.
Returns the fault with its snooze settings.
Send time or count, not both. Use honeybadger_fault_unsnooze to remove the snooze.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `count` (`integer`, optional): Snooze until this many additional occurrences have been received. Example: 10. One of: `10`, `100`, `1000`.
- `time` (`string`, optional): A duration of an hour, a day or a week. Example: hour. One of: `hour`, `day`, `week`.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_unassign`

Unassign Fault · Write

Remove a fault's assignee.
Returns the fault or no content on success.
Use honeybadger_fault_assign to assign someone.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_unsnooze`

Unsnooze Fault · Write

Remove a fault's snooze so its notifications resume.
Returns the fault or no content on success.
Use honeybadger_fault_snooze to snooze.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_update`

Update Fault · Write

Update a fault's resolved or ignored state, assignee or tags, or set it to resolve on the next deploy.
Returns the updated fault.
Use honeybadger_faults_resolve to change many faults at once.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `assignee_id` (`string`, optional): ID of a user on the project. Null unassigns. Example: Us9tPq.
- `ignored` (`boolean`, optional): true ignores the fault (stops data collection), false stops ignoring it. Example: true.
- `resolve_on_deploy` (`boolean`, optional): Set to true to resolve this fault when the project's next deploy is recorded, in any environment. After that deploy, it reads false again. It has no effect if the fault is resolved or ignored once the rest of this update is applied. If the fault is resolved or ignored before the next deploy, the pending resolution is cancelled. Set it to false to cancel it yourself. Example: true.
- `resolved` (`boolean`, optional): true marks the fault resolved, false reopens it. Example: true.
- `tags` (`array`, optional): Tags for the fault. Replaces the existing tags; an empty list removes them all. Example: ["billing", "p1"]

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_faults_ignore`

Ignore Faults · Write

Mark faults as ignored, which stops data collection for them, by fault_ids, query and time filters, or all.
Returns the number of faults changed; dry_run true only reports.
Use honeybadger_faults_unignore to start collecting again.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `all` (`boolean`, optional): Apply to every fault the other filters match, which with no other filters is every fault in the project. Required to make an unbounded change explicit; ignored when fault_ids names specific faults. Example: false.
- `created_after` (`number`, optional): Only faults created after this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1730419200.
- `dry_run` (`boolean`, optional): Report what the request would change without changing it — no state change, no comments, no timeline entries. The response has the same shape either way, with dry_run echoed back. Example: false.
- `fault_ids` (`array`, optional): IDs of the faults to change. If any ID isn't a fault in this project, nothing changes. Omit to act on everything the query and time filters match; with no filters, that requires "all": true. Example: ["103547218", "103547219"]
- `occurred_after` (`number`, optional): Only faults that occurred after this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1730419200.
- `occurred_before` (`number`, optional): Only faults that occurred before this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1731024000.
- `q` (`string`, optional): Error search query in the syntax of Honeybadger's web UI, such as environment:production, is:resolved or class:ArgumentError. Prefix a filter with - to negate it. Example: environment:production -is:resolved.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_faults_resolve`

Resolve Faults · Write

Mark faults as resolved, by fault_ids or by an error search query and time filters, or every fault with all true.
Returns the number of faults changed; with dry_run true it reports what would change without changing it.
Use honeybadger_fault_update for a single fault. Use honeybadger_faults_unresolve to reopen.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `all` (`boolean`, optional): Apply to every fault the other filters match, which with no other filters is every fault in the project. Required to make an unbounded change explicit; ignored when fault_ids names specific faults. Example: false.
- `created_after` (`number`, optional): Only faults created after this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1730419200.
- `dry_run` (`boolean`, optional): Report what the request would change without changing it — no state change, no comments, no timeline entries. The response has the same shape either way, with dry_run echoed back. Example: false.
- `fault_ids` (`array`, optional): IDs of the faults to change. If any ID isn't a fault in this project, nothing changes. Omit to act on everything the query and time filters match; with no filters, that requires "all": true. Example: ["103547218", "103547219"]
- `occurred_after` (`number`, optional): Only faults that occurred after this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1730419200.
- `occurred_before` (`number`, optional): Only faults that occurred before this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1731024000.
- `q` (`string`, optional): Error search query in the syntax of Honeybadger's web UI, such as environment:production, is:resolved or class:ArgumentError. Prefix a filter with - to negate it. Example: environment:production -is:resolved.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_faults_unignore`

Unignore Faults · Write

Stop ignoring faults so Honeybadger records them again, by fault_ids, query and time filters, or all.
Returns the number of faults changed; dry_run true only reports.
Use honeybadger_faults_ignore to ignore.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `all` (`boolean`, optional): Apply to every fault the other filters match, which with no other filters is every fault in the project. Required to make an unbounded change explicit; ignored when fault_ids names specific faults. Example: false.
- `created_after` (`number`, optional): Only faults created after this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1730419200.
- `dry_run` (`boolean`, optional): Report what the request would change without changing it — no state change, no comments, no timeline entries. The response has the same shape either way, with dry_run echoed back. Example: false.
- `fault_ids` (`array`, optional): IDs of the faults to change. If any ID isn't a fault in this project, nothing changes. Omit to act on everything the query and time filters match; with no filters, that requires "all": true. Example: ["103547218", "103547219"]
- `occurred_after` (`number`, optional): Only faults that occurred after this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1730419200.
- `occurred_before` (`number`, optional): Only faults that occurred before this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1731024000.
- `q` (`string`, optional): Error search query in the syntax of Honeybadger's web UI, such as environment:production, is:resolved or class:ArgumentError. Prefix a filter with - to negate it. Example: environment:production -is:resolved.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_faults_unresolve`

Unresolve Faults · Write

Mark faults as unresolved, by fault_ids or by an error search query and time filters, or every fault with all true.
Returns the number of faults changed; dry_run true only reports.
Use honeybadger_faults_resolve to resolve.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `all` (`boolean`, optional): Apply to every fault the other filters match, which with no other filters is every fault in the project. Required to make an unbounded change explicit; ignored when fault_ids names specific faults. Example: false.
- `created_after` (`number`, optional): Only faults created after this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1730419200.
- `dry_run` (`boolean`, optional): Report what the request would change without changing it — no state change, no comments, no timeline entries. The response has the same shape either way, with dry_run echoed back. Example: false.
- `fault_ids` (`array`, optional): IDs of the faults to change. If any ID isn't a fault in this project, nothing changes. Omit to act on everything the query and time filters match; with no filters, that requires "all": true. Example: ["103547218", "103547219"]
- `occurred_after` (`number`, optional): Only faults that occurred after this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1730419200.
- `occurred_before` (`number`, optional): Only faults that occurred before this Unix timestamp. Applied when fault_ids is omitted, alongside q. Example: 1731024000.
- `q` (`string`, optional): Error search query in the syntax of Honeybadger's web UI, such as environment:production, is:resolved or class:ArgumentError. Prefix a filter with - to negate it. Example: environment:production -is:resolved.

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_project_create`

Create Project · Write

Create a new Honeybadger project in the account.
Returns the created project with its id and API key details.
Requires a token with projects:write.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Project name. Example: Billing API.
- `asana_workspace_id` (`string`, optional): Asana workspace used by the project's Asana integration. Null clears it. Example: 1203456789012345.
- `customer_throttle` (`integer`, optional): Notices accepted per minute before throttling kicks in. Null clears it. Example: 100.
- `disable_email_notifications` (`boolean`, optional): Create-only. Members added with the project get email notifications switched off. Not stored or returned. Example: true.
- `disable_public_links` (`boolean`, optional): Disallow shareable public fault links. Null resets it to false. Example: true.
- `language` (`string`, optional): Primary language, used to format backtraces. Null clears it. Example: ruby.
- `purge_days` (`integer`, optional): Days to retain notices. Changing it requires custom retention on the account; without it, only the current value (on create, the default) is accepted. Null clears it. Example: 90.
- `resolve_errors_on_deploy` (`boolean`, optional): Resolve every open fault when a deploy is recorded. Null resets it to true. Example: true.
- `source_url` (`string`, optional): Template for linking a backtrace line to your source host. [file] and [line] are substituted. Null clears it. Example: https://github.com/acme/billing/blob/main/[file]#L[line]
- `team_id` (`string`, optional): Puts the new project in this team. Create-only: afterwards the team's project_ids owns membership. Including it requires team:write in addition to the operation's project scope, and the user must be allowed to manage the team. Without team:write the entire request is rejected with 403 insufficient_scope; no other fields are saved. Example: Tm4rWx.
- `user_search_field` (`string`, optional): Context key identifying the affected user, for when it is not in the default context.user_email or context.user_id. Null clears it. Example: context.account_email.
- `user_url` (`string`, optional): Template for linking a fault's affected user into your own system. [user_id] and [user_email] are substituted. Null clears it. Example: https://admin.example.com/users/[user_id]

Example input: `{"name":"<name>"}`

### `honeybadger_project_update`

Update Project · Write

Update a project's settings; send only the fields to change.
Returns the updated project.
Null clears or resets a nullable setting.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `asana_workspace_id` (`string`, optional): Asana workspace used by the project's Asana integration. Null clears it. Example: 1203456789012345.
- `customer_throttle` (`integer`, optional): Notices accepted per minute before throttling kicks in. Null clears it. Example: 100.
- `disable_public_links` (`boolean`, optional): Disallow shareable public fault links. Null resets it to false. Example: true.
- `language` (`string`, optional): Primary language, used to format backtraces. Null clears it. Example: ruby.
- `name` (`string`, optional): Project name. Example: Billing API.
- `purge_days` (`integer`, optional): Days to retain notices. Changing it requires custom retention on the account; without it, only the current value (on create, the default) is accepted. Null clears it. Example: 90.
- `resolve_errors_on_deploy` (`boolean`, optional): Resolve every open fault when a deploy is recorded. Null resets it to true. Example: true.
- `source_url` (`string`, optional): Template for linking a backtrace line to your source host. [file] and [line] are substituted. Null clears it. Example: https://github.com/acme/billing/blob/main/[file]#L[line]
- `user_search_field` (`string`, optional): Context key identifying the affected user, for when it is not in the default context.user_email or context.user_id. Null clears it. Example: context.account_email.
- `user_url` (`string`, optional): Template for linking a fault's affected user into your own system. [user_id] and [user_email] are substituted. Null clears it. Example: https://admin.example.com/users/[user_id]

Example input: `{"project_id":"<project_id>"}`

### `honeybadger_site_create`

Create Uptime Site · Write

Create an uptime monitoring site that checks a URL from several locations on a schedule.
Returns the created site with its id.
Requires uptime monitoring on the Honeybadger plan.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `url` (`string`, required): Must start with http:// or https://, with no surrounding whitespace. Example: https://www.example.com/health.
- `active` (`boolean`, optional): Whether monitoring is active. After 740 consecutive failed checks the server sets it to false. Null resets it to true. Example: true.
- `frequency` (`integer`, optional): Minutes between checks. The plan sets the most frequent allowed. Null resets it to 5. Example: 1. One of: `1`, `2`, `5`, `15`.
- `locations` (`array`, optional): A set of location names to check from. Null or empty means every location. A set; order is ignored and duplicates are dropped. Example: ["Virginia", "Frankfurt"]
- `match` (`string`, optional): What match_type compares against. Required unless match_type is success, and must be left out with success. Example: ok.
- `match_type` (`string`, optional): How a check decides the site is up: success (any 2xx; leave match out), exact (status code equals match), include or exclude (body does or doesn't contain match), or jmespath (match is a JMESPath expression on the JSON body). Defaults to success. Example: success. One of: `success`, `exact`, `include`, `exclude`, `jmespath`.
- `name` (`string`, optional): Name shown for the site in Honeybadger and on status pages. Example: Billing API.
- `outage_threshold` (`integer`, optional): Consecutive failures before an outage is declared. null means down once failures reach 50% of locations. Example: 10.
- `request_body` (`string`, optional): Body to send with the request, up to 32 KB. Null clears it. Example: {"ping": true}
- `request_headers` (`object`, optional): Headers to send with the request, as header name to value. Replaces the stored headers; null or {} clears them. Example: {"X-Health-Check": "honeybadger"}
- `request_method` (`string`, optional): HTTP method each check sends. Null resets it to GET. Example: GET. One of: `GET`, `POST`, `PUT`, `PATCH`, `DELETE`.
- `timeout` (`integer`, optional): Request timeout in seconds, 1 to 120, default 30, and less than the frequency in seconds. Changing it requires the uptime timeout feature on the account; without it, only the current value (on create, the default) is accepted. Null resets it to the default. Example: 10.
- `validate_ssl` (`boolean`, optional): Fail the check when the TLS certificate does not validate. Null resets it to true. Example: true.

Example input: `{"project_id":"<project_id>","url":"<url>"}`

### `honeybadger_site_update`

Update Uptime Site · Write

Update an uptime monitoring site; send only the fields to change, such as active false to pause it.
Returns the updated site.
Use honeybadger_site_get to read the current settings.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `site_id` (`string`, required): UUID of the uptime monitoring site. Get it from honeybadger_sites_list. Example: 9f8b6d2e-4c1a-4b7f-9e35-2a6c8d0f1b47.
- `active` (`boolean`, optional): Whether monitoring is active. After 740 consecutive failed checks the server sets it to false. Null resets it to true. Example: true.
- `frequency` (`integer`, optional): Minutes between checks. The plan sets the most frequent allowed. Null resets it to 5. Example: 1. One of: `1`, `2`, `5`, `15`.
- `locations` (`array`, optional): A set of location names to check from. Null or empty means every location. A set; order is ignored and duplicates are dropped. Example: ["Virginia", "Frankfurt"]
- `match` (`string`, optional): What match_type compares against. Required unless match_type is success, and must be left out with success. Example: ok.
- `match_type` (`string`, optional): How a check decides the site is up: success (any 2xx; leave match out), exact (status code equals match), include or exclude (body does or doesn't contain match), or jmespath (match is a JMESPath expression on the JSON body). Defaults to success. Example: success. One of: `success`, `exact`, `include`, `exclude`, `jmespath`.
- `name` (`string`, optional): Name shown for the site in Honeybadger and on status pages. Example: Billing API.
- `outage_threshold` (`integer`, optional): Consecutive failures before an outage is declared. null means down once failures reach 50% of locations. Example: 10.
- `request_body` (`string`, optional): Body to send with the request, up to 32 KB. Null clears it. Example: {"ping": true}
- `request_headers` (`object`, optional): Headers to send with the request, as header name to value. Replaces the stored headers; null or {} clears them. Example: {"X-Health-Check": "honeybadger"}
- `request_method` (`string`, optional): HTTP method each check sends. Null resets it to GET. Example: GET. One of: `GET`, `POST`, `PUT`, `PATCH`, `DELETE`.
- `timeout` (`integer`, optional): Request timeout in seconds, 1 to 120, default 30, and less than the frequency in seconds. Changing it requires the uptime timeout feature on the account; without it, only the current value (on create, the default) is accepted. Null resets it to the default. Example: 10.
- `url` (`string`, optional): Must start with http:// or https://, with no surrounding whitespace. Example: https://www.example.com/health.
- `validate_ssl` (`boolean`, optional): Fail the check when the TLS certificate does not validate. Null resets it to true. Example: true.

Example input: `{"project_id":"<project_id>","site_id":"<site_id>"}`

### `honeybadger_status_page_incident_create`

Create Status Page Incident · Write

Open an incident on a status page with at least one update carrying its message, status and severity.
Returns the created incident with its updates.
Updates with should_notify true email the page's subscribers. Use build_type scheduled_maintenance for planned work.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `status_page_id` (`string`, required): ID of the status page. Get it from honeybadger_status_pages_list. Example: Sp7bMq.
- `title` (`string`, required): Incident title shown on the status page. Example: Elevated error rates.
- `updates` (`array`, required): Updates to open the incident with; at least one. Each update has a message, a status (such as investigating, identified, monitoring or resolved, or maintenance_scheduled for planned work), a severity (problem_detected, degraded_performance, partial_outage, outage or operational), and optional start_at, start_now and should_notify (true emails the page's subscribers). Example: [{"status": "investigating", "severity": "partial_outage", "message": "Some requests to the API are failing. We're looking into it."}]
- `build_type` (`string`, optional): How the incident was opened. current is happening now, retroactive records something already over, scheduled_maintenance is planned. Only a scheduled_maintenance incident may have updates starting in the future. Example: current. One of: `current`, `retroactive`, `scheduled_maintenance`.
- `retro_notify_message` (`string`, optional): Message accompanying that announcement. Example: We had a brief API outage earlier today; it is resolved.
- `retro_should_notify` (`boolean`, optional): Announce a retroactive incident when it is created. Example: true.

Example input: `{"status_page_id":"<status_page_id>","title":"<title>","updates":[{"status":"investigating","severity":"partial_outage","message":"Some requests to the API are failing. We're looking into it."}]}`

### `honeybadger_status_page_incident_update_create`

Post Incident Update · Write

Post a new update to a status page incident, such as moving it to identified, monitoring or resolved.
Returns the created update.
Set status resolved and severity operational to close the incident.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `incident_id` (`string`, required): ID of the status page incident. Get it from honeybadger_status_page_incidents_list. Example: In3pKr.
- `status_page_id` (`string`, required): ID of the status page. Get it from honeybadger_status_pages_list. Example: Sp7bMq.
- `message` (`string`, optional): The update's prose. Example: We have identified the cause and are rolling back.
- `severity` (`string`, optional): Incident severity after this update. Example: problem_detected. One of: `problem_detected`, `degraded_performance`, `partial_outage`, `outage`, `operational`.
- `should_notify` (`boolean`, optional): Announce the update on the status page's connected accounts and email the status page's subscribers. Example: true.
- `start_at` (`string`, optional): When the update takes effect. Only a scheduled_maintenance incident may set this in the future. Example: 2026-11-20T02:00:00Z.
- `start_now` (`boolean`, optional): Start the update immediately, ignoring start_at. An update that has already started is left as it is, so sending it again changes nothing. Example: true.
- `status` (`string`, optional): Incident status after this update. Example: maintenance_scheduled. One of: `maintenance_scheduled`, `in_maintenance`, `maintenance_complete`, `investigating`, `identified`, `resolving`, `monitoring`, `resolved`.

Example input: `{"incident_id":"<incident_id>","status_page_id":"<status_page_id>"}`

### `honeybadger_check_in_delete`

Delete Check-In · Destructive

Delete a check-in monitor.
Returns no content on success.
Jobs reporting to it will get errors afterwards.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `check_in_id` (`string`, required): ID of the check-in monitor. Get it from honeybadger_check_ins_list. Example: Ci5xWq.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"check_in_id":"<check_in_id>","project_id":"<project_id>"}`

### `honeybadger_fault_comment_delete`

Delete Fault Comment · Destructive

Delete a comment from a fault.
Returns no content on success.
Use honeybadger_fault_comments_list to find the comment ID.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `comment_id` (`string`, required): ID of the comment on the fault. Get it from honeybadger_fault_comments_list. Example: Cm4vRt.
- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"comment_id":"<comment_id>","fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_delete`

Delete Fault · Destructive

Permanently delete a fault. Its notices stay retrievable by ID until retention removes them.
Returns no content on success.
Use honeybadger_fault_update with ignored true to stop tracking without deleting.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>"}`

### `honeybadger_fault_merge`

Merge Fault · Destructive

Merge the fault in the path into target_fault_id, moving its notices, comments and history; its tags, assignee and state are dropped.
Returns 202 Accepted; the merge runs in the background, then the old fault ID redirects to the target.
Use this for duplicate faults. It cannot be undone.

Read only: no. Destructive: yes. Idempotent (safe to retry): no.

Inputs:

- `fault_id` (`string`, required): ID of the fault (error group), a number sent as a string. Get it from honeybadger_faults_list. Example: 103547218.
- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `target_fault_id` (`string`, required): ID of the fault to keep. The fault in the path is merged into it. Example: 103547219.

Example input: `{"fault_id":"<fault_id>","project_id":"<project_id>","target_fault_id":"<target_fault_id>"}`

### `honeybadger_site_delete`

Delete Uptime Site · Destructive

Delete an uptime monitoring site and its check history.
Returns no content on success.
Use honeybadger_site_update with active false to pause instead.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`string`, required): ID of the Honeybadger project, such as Xk9mZp. Get it from honeybadger_projects_list. Example: Xk9mZp.
- `site_id` (`string`, required): UUID of the uptime monitoring site. Get it from honeybadger_sites_list. Example: 9f8b6d2e-4c1a-4b7f-9e35-2a6c8d0f1b47.

Example input: `{"project_id":"<project_id>","site_id":"<site_id>"}`

## Related

Other Developer Tools connectors ([all 200](/agentkit/connectors/?category=developer-tools)):

- [GitHub](/agentkit/connectors/github/): Scalekit connector, OAuth, 217 tools
- [Datadog](/agentkit/connectors/datadog/): Scalekit connector, API key, 105 tools
- [Linear](/agentkit/connectors/linear/): Scalekit connector, OAuth, 64 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
