Skip to content
Changelog

Report a bug

Honeybadger integration: operations for AI agents

Honeybadger connects to Type.com as an integration. This page lists the 102 operations documented for Claude and Codex in Type.com: 47 read, 27 write, 28 destructive.

About Honeybadger

Honeybadger vendor API references, subject to account permissions.

Categories: Developer Tools & IT

How to connect Honeybadger to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

102 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

102 operations listed.

Data API v2 / accounts

  • Read

    Get all accounts

    Returns a list of all accounts the authenticated user belongs to.

    GET /v2/accounts/

  • Read

    Get info for one account

    Returns info about an account, including the quota consumption for the current month. Each of the three sets of quota info is returned as an array of arrays, with one date & count pair for each day of the month, starting at midnight UTC on the first of the month. The different types of stats are as follows:

    GET /v2/accounts/{account_id}

  • Read

    Get a list of account users or user details

    Returns all the users or a single user for the given account:

    GET /v2/accounts/{account_id}/users

  • Read

    Get a list of account users or user details

    Returns all the users or a single user for the given account:

    GET /v2/accounts/{account_id}/users/{user_id}

  • Read

    Get an account invitation list or account invitation details

    Returns a list of account invitations or a single account invitation for the given account:

    GET /v2/accounts/{account_id}/invitations

  • Read

    Get an account invitation list or account invitation details

    Returns a list of account invitations or a single account invitation for the given account:

    GET /v2/accounts/{account_id}/invitations/{invitation_id}

  • Write

    Create an invitation for a user to join an account

    You can specify these fields:

    POST /v2/accounts/{account_id}/invitations

  • Destructive

    Update a user

    The list of valid fields is as follows:

    PUT /v2/accounts/{account_id}/users/{user_id}

  • Destructive

    Remove a user from the account

    Remove a user from the account

    DELETE /v2/accounts/{account_id}/users/{user_id}

  • Destructive

    Update an account invitation

    You can specify either of these fields:

    PUT /v2/accounts/{account_id}/invitations/{invitation_id}

  • Destructive

    Delete an account invitation

    ---

    DELETE /v2/accounts/{account_id}/invitations/{invitation_id}

Data API v2 / alarms

  • Read

    Get an alarm list or alarm details

    The list endpoint returns results in a `results` array. The detail endpoint returns a single alarm:

    GET /v2/projects/{project_id}/alarms

  • Read

    Get an alarm list or alarm details

    The list endpoint returns results in a `results` array. The detail endpoint returns a single alarm:

    GET /v2/projects/{project_id}/alarms/{alarm_id}

  • Read

    Get alarm trigger history

    Returns the alarm’s past evaluations that changed its state:

    GET /v2/projects/{project_id}/alarms/{alarm_id}/history

  • Write

    Create an alarm

    Returns `201 Created` with the alarm JSON shown above.

    POST /v2/projects/{project_id}/alarms

  • Destructive

    Update an alarm

    Returns `204 No Content` on success. The request body uses the same fields as [Create an alarm](https://docs.honeybadger.io/api/alarms/#create-an-alarm). The submitted definition replaces the existing one, so include every field — even the ones you aren’t changing.

    PUT /v2/projects/{project_id}/alarms/{alarm_id}

  • Destructive

    Delete an alarm

    Returns `204 No Content` on success.

    DELETE /v2/projects/{project_id}/alarms/{alarm_id}

Data API v2 / check-ins

  • Read

    Get a check-in list or check-in details

    Returns a list of check-ins or a single check-in for a project. There are two different types of check-ins, simple or cron, and the response varies a bit between the two types.

    GET /v2/projects/{project_id}/check_ins

  • Read

    Get a check-in list or check-in details

    Returns a list of check-ins or a single check-in for a project. There are two different types of check-ins, simple or cron, and the response varies a bit between the two types.

    GET /v2/projects/{project_id}/check_ins/{check_in_id}

  • Write

    Create a check-in

    This endpoint returns either the simple or cron check-in response described above, depending on the type of check-in you create.

    POST /v2/projects/{project_id}/check_ins

  • Write

    Update a check-in

    The fields listed in the previous section other than `schedule_type` can be updated. In other words, the schedule type can’t be changed. The `report_period` field is only valid for simple check-ins, and the `cron_schedule` and `cron_timezone` fields are only valid for cron check-ins.

    PUT /v2/projects/{project_id}/check_ins/{check_in_id}

  • Destructive

    Update all check-ins

    Caution

    PUT /v2/projects/{project_id}/check_ins

  • Destructive

    Delete a check-in

    ---

    DELETE /v2/projects/{project_id}/check_ins/{check_in_id}

Data API v2 / comments

  • Read

    Get a comment list or comment details

    Returns a list of comments or a single comment for the given fault with the following format:

    GET /v2/projects/{project_id}/faults/{fault_id}/comments

  • Read

    Get a comment list or comment details

    Returns a list of comments or a single comment for the given fault with the following format:

    GET /v2/projects/{project_id}/faults/{fault_id}/comments/{comment_id}

  • Write

    Create a comment

    The `body` field is the only field that can be included in the payload.

    POST /v2/projects/{project_id}/faults/{fault_id}/comments

  • Write

    Update a comment

    Update a comment

    PUT /v2/projects/{project_id}/faults/{fault_id}/comments/{comment_id}

  • Destructive

    Delete a comment

    ---

    DELETE /v2/projects/{project_id}/faults/{fault_id}/comments/{comment_id}

Data API v2 / dashboards

  • Read

    Get a dashboard list or dashboard details

    The list endpoint returns results in a `results` array. The detail endpoint returns a single dashboard:

    GET /v2/projects/{project_id}/dashboards

  • Read

    Get a dashboard list or dashboard details

    The list endpoint returns results in a `results` array. The detail endpoint returns a single dashboard:

    GET /v2/projects/{project_id}/dashboards/{dashboard_id}

  • Write

    Create a dashboard

    Returns `201 Created` with the dashboard JSON shown above.

    POST /v2/projects/{project_id}/dashboards

  • Destructive

    Update a dashboard

    Returns `204 No Content` on success. The request body uses the same fields as [Create a dashboard](https://docs.honeybadger.io/api/dashboards/#create-a-dashboard). The submitted `widgets` array replaces the existing one, so include every widget you want to keep.

    PUT /v2/projects/{project_id}/dashboards/{dashboard_id}

  • Destructive

    Delete a dashboard

    Returns `204 No Content` on success.

    DELETE /v2/projects/{project_id}/dashboards/{dashboard_id}

Data API v2 / deployments

  • Read

    Get a deploy list or deploy details

    Returns a list of deploys or a single deploy for the given project with the following format:

    GET /v2/projects/{project_id}/deploys

  • Read

    Get a deploy list or deploy details

    Returns a list of deploys or a single deploy for the given project with the following format:

    GET /v2/projects/{project_id}/deploys/{deploy_id}

  • Destructive

    Delete a deploy

    ---

    DELETE /v2/projects/{project_id}/deploys/{deploy_id}

Data API v2 / environments

  • Read

    Get all environments

    Returns a list of all recorded environments in this project.

    GET /v2/projects/{project_id}/environments

  • Read

    Get a single environment’s details

    Get a single environment’s details

    GET /v2/projects/{project_id}/environments/{environment_id}

  • Write

    Create an environment

    You can specify these fields within the `environment` object:

    POST /v2/projects/{project_id}/environments

  • Destructive

    Update an environment

    You can specify any of these fields within the `environment` object:

    PUT /v2/projects/{project_id}/environments/{environment_id}

  • Destructive

    Delete an environment

    Returns an empty response (204 No Content) if successful.

    DELETE /v2/projects/{project_id}/environments/{environment_id}

Data API v2 / faults

  • Read

    Get a fault list or fault details

    Returns a list of faults or a single fault for the given project with the following format:

    GET /v2/projects/{project_id}/faults

  • Read

    Get a fault list or fault details

    Returns a list of faults or a single fault for the given project with the following format:

    GET /v2/projects/{project_id}/faults/{fault_id}

  • Read

    Get a count of faults

    Returns a total count of all the errors for a project and counts of errors grouped by environment, resolution status, and ignored status. The counts can be filtered by these parameters:

    GET /v2/projects/{project_id}/faults/summary

  • Read

    Get a count of occurrences for a fault

    Provides the number of times errors have been encountered for a particular fault.

    GET /v2/projects/{project_id}/faults/{fault_id}/occurrences

  • Read

    Get a list of notices

    Returns a list of notices for the given fault with the following format:

    GET /v2/projects/{project_id}/faults/{fault_id}/notices

  • Read

    Get a list of affected users

    Returns a list of the users who were affected by an error:

    GET /v2/projects/{project_id}/faults/{fault_id}/affected_users

  • Write

    Pausing and unpausing faults

    You can pause notifications for a period of time or for the number of occurrences of a fault. This doesn’t affect the resolved/unresolved status. If a fault is resolved while paused, new occurrences will still mark it as unresolved — you just won’t be notified about it. For time-based pauses, notifications resume on the first occurrence received after the time period has elapsed. For count-based pauses, notifications resume on the occurrence that exhausts the count. In both cases, a notification will be sent even if the fault was already reopened by an earlier occurrence during the pause.

    POST /v2/projects/{project_id}/faults/{fault_id}/unpause

  • Write

    Pausing and unpausing faults

    You can pause notifications for a period of time or for the number of occurrences of a fault. This doesn’t affect the resolved/unresolved status. If a fault is resolved while paused, new occurrences will still mark it as unresolved — you just won’t be notified about it. For time-based pauses, notifications resume on the first occurrence received after the time period has elapsed. For count-based pauses, notifications resume on the occurrence that exhausts the count. In both cases, a notification will be sent even if the fault was already reopened by an earlier occurrence during the pause.

    POST /v2/projects/{project_id}/faults/unpause

  • Write

    Bulk-resolving faults

    You can mark all faults for a project as resolved using this endpoint:

    POST /v2/projects/{project_id}/faults/resolve

  • Write

    Linking faults to existing 3rd-party issues

    This associates an existing GitHub issue, Pivotal Tracker story, etc. with a fault. Once associated, the error detail page in the UI will include a link to the associated issue. The `channel_id` portion of the payload can be obtained from the [integrations](https://docs.honeybadger.io/api/projects#get-a-list-of-integrations-for-a-project) API endpoint. The `data` portion of the payload varies depending on which type of integration is being referenced:

    POST /v2/projects/{project_id}/faults/{fault_id}/link

  • Destructive

    Update a fault

    The following fields can be updated:

    PUT /v2/projects/{project_id}/faults/{fault_id}

  • Destructive

    Delete a fault

    Delete a fault

    DELETE /v2/projects/{project_id}/faults/{fault_id}

  • Destructive

    Pausing and unpausing faults

    You can pause notifications for a period of time or for the number of occurrences of a fault. This doesn’t affect the resolved/unresolved status. If a fault is resolved while paused, new occurrences will still mark it as unresolved — you just won’t be notified about it. For time-based pauses, notifications resume on the first occurrence received after the time period has elapsed. For count-based pauses, notifications resume on the occurrence that exhausts the count. In both cases, a notification will be sent even if the fault was already reopened by an earlier occurrence during the pause.

    POST /v2/projects/{project_id}/faults/{fault_id}/pause

  • Destructive

    Unlinking faults

    This removes the link to an associated GitHub issue, Pivotal Tracker story, etc. The `channel_id` portion of the payload can be obtained from the [integrations](https://docs.honeybadger.io/api/projects/#get-a-list-of-integrations-for-a-project) API endpoint.

    POST /v2/projects/{project_id}/faults/{fault_id}/unlink

Data API v2 / projects

  • Read

    Get a project list or project details

    Returns a list or a single project with the following format:

    GET /v2/projects

  • Read

    Get a project list or project details

    Returns a list or a single project with the following format:

    GET /v2/projects/{project_id}

  • Read

    Get a count of occurrences for all projects or a single project

    Provides the number of times errors have been encountered in your project or across all your projects.

    GET /v2/projects/occurrences

  • Read

    Get a count of occurrences for all projects or a single project

    Provides the number of times errors have been encountered in your project or across all your projects.

    GET /v2/projects/{project_id}/occurrences

  • Read

    Get a list of integrations for a project

    Returns a list of integrations (a.k.a. channels) for a project:

    GET /v2/projects/{project_id}/integrations

  • Read

    Get report data

    The following endpoints provide the data that is displayed on the Reports tab for a project.

    GET /v2/projects/{project_id}/reports/notices_by_class

  • Read

    Get report data

    The following endpoints provide the data that is displayed on the Reports tab for a project.

    GET /v2/projects/{project_id}/reports/notices_by_location

  • Read

    Get report data

    The following endpoints provide the data that is displayed on the Reports tab for a project.

    GET /v2/projects/{project_id}/reports/notices_by_user

  • Read

    Get report data

    The following endpoints provide the data that is displayed on the Reports tab for a project.

    GET /v2/projects/{project_id}/reports/notices_per_day

  • Write

    Create a project

    Here is a list of the fields that can be provided:

    POST /v2/projects

  • Destructive

    Update a project

    The fields listed in the prior section are also available when updating a project.

    PUT /v2/projects/{project_id}

  • Destructive

    Delete a project

    Delete a project

    DELETE /v2/projects/{project_id}

Data API v2 / insights

  • Read

    Query Insights data

    This endpoint executes a BadgerQL query against your project’s Insights data and returns the results.

    POST /v2/projects/{project_id}/insights/queries

Reporting API v1

  • Write

    Introduction

    To report a check-in, simply send a GET request to the endpoint URL you received when creating the check-in:

    GET /v1/check_in/{check_in_id}

  • Write

    Introduction

    To report a check-in, simply send a GET request to the endpoint URL you received when creating the check-in:

    GET /v1/check_in/{project_api_key}/{slug}

  • Write

    Check-in payloads

    Business-tier accounts can send additional check-in details via POST. The payload is optional and must be under 20KB.

    POST /v1/check_in/{check_in_id}

  • Write

    Report deployment — GET example (method conflict)

    Make a POST request to `https://api.honeybadger.io/v1/deploys` with the following parameters:

    GET /v1/deploys

  • Write

    POST /v1/deploys

    Make a POST request to `https://api.honeybadger.io/v1/deploys` with the following parameters:

    POST /v1/deploys

  • Write

    Report Insights events

    Events you send to this API will appear in [Honeybadger Insights](https://docs.honeybadger.io/guides/insights), where you can query and visualize the events.

    POST /v1/events

  • Write

    Report an exception

    Your JSON payload should be submitted as the body of a POST request to <https://api.honeybadger.io/v1/notices>, with the following headers:

    POST /v1/notices

  • Write

    Overview

    To upload your source map files to Honeybadger, POST them to `https://api.honeybadger.io/v1/source_maps` with the following parameters:

    POST /v1/source_maps

Data API v2 / status-pages

  • Read

    Get all status pages

    Returns a list of all status pages in this account.

    GET /v2/accounts/{account_id}/status_pages

  • Read

    Get a single status page’s details

    Get a single status page’s details

    GET /v2/accounts/{account_id}/status_pages/{status_page_id}

  • Write

    Create a status page

    You can specify these fields within the `status page` object:

    POST /v2/accounts/{account_id}/status_pages

  • Write

    Update a status page

    You can specify one or more of these fields within the `status page` object:

    PUT /v2/accounts/{account_id}/status_pages/{status_page_id}

  • Destructive

    Delete a status page

    Returns an empty response (204 No Content) if successful.

    DELETE /v2/accounts/{account_id}/status_pages/{status_page_id}

Data API v2 / streams

  • Read

    Get all streams

    Returns a list of the project’s streams.

    GET /v2/projects/{project_id}/streams

Data API v2 / teams

  • Read

    Get a team list or team details

    Returns a list of teams

    GET /v2/teams

  • Read

    Get a team list or team details

    Returns a list of teams

    GET /v2/teams/{team_id}

  • Read

    Get a list of team members or team member details

    Returns all the members or a single team member for the given team:

    GET /v2/teams/{team_id}/team_members

  • Read

    Get a team invitation list or team invitation details

    Returns a list of team invitations or a single team invitation for the given team:

    GET /v2/teams/{team_id}/team_invitations

  • Read

    Get a team invitation list or team invitation details

    Returns a list of team invitations or a single team invitation for the given team:

    GET /v2/teams/{team_id}/team_invitations/{team_invitation_id}

  • Write

    Create a team

    You can specify these fields:

    POST /v2/teams

  • Write

    Update a team

    Update a team

    PUT /v2/teams/{team_id}

  • Write

    Create a team invitation

    You can specify these fields:

    POST /v2/teams/{team_id}/team_invitations

  • Destructive

    Delete a team

    Delete a team

    DELETE /v2/teams/{team_id}

  • Destructive

    Update a team member

    The list of valid fields is as follows:

    PUT /v2/teams/{team_id}/team_members/{team_member_id}

  • Destructive

    Delete a team member

    Delete a team member

    DELETE /v2/teams/{team_id}/team_members/{team_member_id}

  • Destructive

    Update a team invitation

    You can specify either of these fields:

    PUT /v2/teams/{team_id}/team_invitations/{team_invitation_id}

  • Destructive

    Delete a team invitation

    ---

    DELETE /v2/teams/{team_id}/team_invitations/{team_invitation_id}

Data API v2 / uptime

  • Read

    Get a site list or site details

    Returns a list of sites or a single sites for the given project with the following format:

    GET /v2/projects/{project_id}/sites

  • Read

    Get a site list or site details

    Returns a list of sites or a single sites for the given project with the following format:

    GET /v2/projects/{project_id}/sites/{site_id}

  • Read

    Get a list of outages for a site

    Returns a list of outages with the following format:

    GET /v2/projects/{project_id}/sites/{site_id}/outages

  • Read

    Get a list of uptime checks for a site

    Returns a list of uptime checks with the following format:

    GET /v2/projects/{project_id}/sites/{site_id}/uptime_checks

  • Write

    Create a site

    Here is a list of the fields that can be specified:

    POST /v2/projects/{project_id}/sites

  • Destructive

    Update a site

    Update requests can change the same fields as create requests.

    PUT /v2/projects/{project_id}/sites/{site_id}

  • Destructive

    Delete a site

    Delete a site

    DELETE /v2/projects/{project_id}/sites/{site_id}

See How connections work for access and permissions, or browse all integrations.