LogBrew

LogBrew Issues API

Grouped errors: list, read, triage, assign, own, and investigate.

GitHub OpenAPI

Operations 15

GET /api/telemetry/issues Find grouped issues with their priority, assignee, and archive condition #
GET /api/telemetry/issues/assignees List the people and teams that can be assigned a project's issues #
POST /api/telemetry/issues/bulk Apply one triage change to many issues #
GET /api/telemetry/issues/notifications List issue assignments and reopens that concern you #
POST /api/telemetry/issues/notifications/read Mark your issue notifications read up to a time #
GET /api/telemetry/issues/ownership Read a project's ownership rules and CODEOWNERS text #
PUT /api/telemetry/issues/ownership Replace a project's ownership rules and CODEOWNERS text #
GET /api/telemetry/issues/{issue_id} Read one issue #
PATCH /api/telemetry/issues/{issue_id} Resolve, archive, or reopen an issue, or change its priority or assignee #
GET /api/telemetry/issues/{issue_id}/activity Read one issue's history of status, priority, and assignee changes, newest first #
GET /api/telemetry/issues/{issue_id}/correction-verification Check whether a fix stopped an issue in a later release #
GET /api/telemetry/issues/{issue_id}/events List one issue's occurrences, newest first #
GET /api/telemetry/issues/{issue_id}/investigation Investigate one issue: a selected occurrence, breadcrumbs, related issues… #
GET /api/telemetry/issues/{issue_id}/owners Find who owns one issue, and which rule or recent triage says so #
PUT /api/telemetry/issues/{issue_id}/triage-rule Set the severity rule that applies to future events of one issue #

Documentation

📖
Documentation
https://docs.logbrew.co
📖
APIReference
https://logbrew.co/openapi.json

Specifications

⚙
OpenAPI
https://artifacts.apis.io/logbrew/openapi/logbrew-issues-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/logbrew/json-schema/logbrew-issue-correction-verification-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/logbrew/json-schema/logbrew-native-issue-v5-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/logbrew/json-schema/logbrew-account-usage-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/logbrew/json-schema/logbrew-issue-investigation-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/logbrew/json-schema/logbrew-support-ticket-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/logbrew/json-schema/logbrew-metric-investigation-response-schema.json

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/logbrew:logbrew-issues-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

logbrew-issues-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  contact:
    email: support@logbrew.co
    name: LogBrew support
    url: https://logbrew.co
  description: 'Send `Authorization: Bearer ` with an account access token or a project key. `logbrew login` signs in and stores an access token; `logbrew projects keys create` makes project keys. A read key reads one project''s telemetry and nothing else. Without the CLI, get an access token with device sign-in (RFC 8628): `POST /api/auth/device` with a form-encoded `client_id`, show the person the `user_code` and `verification_uri`, then poll `POST /api/auth/device/token` until they approve.


    Every error has the same JSON shape: a stable `code`, a readable `error`, and a `next` step that says how to recover. A `429` response carries `Retry-After`.


    Some operations have several response versions. This document describes the newest one, so send the `response_version` it requires. List operations return pages with `pagination=cursor`. Older versions keep their exact shape for clients that already use them.


    To test an integration without touching production data, create a separate project for it: each project has its own keys and data, and the free plan covers it. `load_sample_data` fills a new project with a connected example issue, logs, and trace that never count toward usage, `remove_sample_data` removes exactly those rows, and `send_test_event` checks a key end to end.'
  summary: Read and manage LogBrew projects, issues, logs, traces, actions, metrics, releases, and product analytics.
  title: LogBrew Issues API
  version: '1'
servers:
- description: LogBrew API
  url: https://api.logbrew.co
tags:


# --- truncated at 32 KB (219 KB total) ---
# Full source: https://artifacts.apis.io/logbrew/openapi/logbrew-issues-api-openapi.yml