Bugsnag
Bugsnag is an application stability monitoring platform that helps software teams detect, diagnose, and fix errors in web, mobile, and back-end applications.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Bugsnag the way a machine reads it — 111 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Bugsnag scores 31.5/100 (thin), with a separate agent-readiness read of 27/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Bugsnag's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bugsnag/"
title="Bugsnag on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bugsnag.svg"
alt="Bugsnag Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/bugsnag/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bugsnag/"
title="Bugsnag on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bugsnag/card.svg"
alt="Bugsnag Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Bugsnag
Each block below is one kind of artifact we hold for Bugsnag. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 16
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
bugsnag Builds API
Notify Bugsnag about application builds and deployments. Build notifications are used to track releases, identify regressions, and associate source control information with erro...
bugsnag Collaborators API
Manage collaborators within an organization or project. Collaborators are users who have access to view and manage Bugsnag data.
bugsnag Comments API
Manage comments on errors. Comments allow team members to discuss and annotate specific errors.
bugsnag CurrentUser API
Access information about the currently authenticated user.
bugsnag Errors API
Access and manage errors within projects. Errors represent groups of similar events that have been detected by Bugsnag.
bugsnag EventFields API
Access event field definitions for projects. Event fields describe the available data dimensions for filtering and searching events.
bugsnag Events API
Access individual error events. Events represent individual occurrences of an error within a project.
bugsnag Notifications API
Send error and exception notifications to Bugsnag. Each notification can contain one or more events representing individual error occurrences.
bugsnag Organizations API
Access and manage organizations. An organization is the top-level entity in Bugsnag that contains projects and collaborators.
bugsnag Pivots API
Access pivot data for errors. Pivots allow you to group and analyze error data by various dimensions such as browser, device, or location.
bugsnag Projects API
Access and manage projects within an organization. Projects represent individual applications being monitored by Bugsnag.
bugsnag Releases API
Access release information for projects. Releases represent deployed versions of your application and their associated error data.
bugsnag Sessions API
Report session data to Bugsnag for stability score calculations. Sessions represent periods of user activity and are used to compute crash-free session and user percentages.
bugsnag Stability API
Access stability metrics for projects. Stability data provides crash-free session and user percentages across releases.
bugsnag Traces API
Send OpenTelemetry trace data to Bugsnag for performance monitoring. Spans represent individual operations and are assembled into traces that visualize request flow and latency.
bugsnag Trends API
Access trend data for errors and projects. Trends provide time-series data showing how error rates and stability change over time.
Scroll within the panel for all 16 ·
Open Collections 22
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONBugsnag Build API
OPEN COLLECTIONBugsnag Build Builds API
OPEN COLLECTIONBugsnag Build Builds Collaborators API
OPEN COLLECTIONBugsnag Build Builds Comments API
OPEN COLLECTIONBugsnag Build Builds CurrentUser API
OPEN COLLECTIONBugsnag Data Access API
OPEN COLLECTIONBugsnag Error Reporting API
OPEN COLLECTIONBugsnag Build Builds Errors API
OPEN COLLECTIONBugsnag Build Builds EventFields API
OPEN COLLECTIONBugsnag Build Builds Events API
OPEN COLLECTIONBugsnag Build Builds Notifications API
OPEN COLLECTIONBugsnag Build Builds Organizations API
OPEN COLLECTIONBugsnag Build Builds Pivots API
OPEN COLLECTIONBugsnag Build Builds Projects API
OPEN COLLECTIONBugsnag Build Builds Releases API
OPEN COLLECTIONBugsnag Session Tracking API
OPEN COLLECTIONBugsnag Build Builds Sessions API
OPEN COLLECTIONBugsnag Build Builds Stability API
OPEN COLLECTIONBugsnag Trace API
OPEN COLLECTIONBugsnag Build Builds Traces API
OPEN COLLECTIONBugsnag Build Builds Trends API
OPEN COLLECTIONScroll within the panel for all 22 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Bugsnag Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Bugsnag Finops
FINOPSFeatures 16
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 16 ·
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Bugsnag Webhook Events
Bugsnag webhooks deliver real-time notifications about error events to a configured callback URL via HTTP POST. The webhook integration sends JSON payloads containing informatio...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Bugsnag Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Bugsnag API Rules
SPECTRALBugsnag API Rules
SPECTRALJSON Schema 45
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ApplicationInfo
JSON SCHEMABreadcrumb
JSON SCHEMABreadcrumbPayload
JSON SCHEMABugsnag Build
JSON SCHEMABuildPayload
JSON SCHEMABuildResponse
JSON SCHEMACollaborator
JSON SCHEMACollaboratorInvite
JSON SCHEMACollaboratorUpdate
JSON SCHEMAComment
JSON SCHEMACommentCreate
JSON SCHEMADeviceInfo
JSON SCHEMABugsnag Error Event
JSON SCHEMAError
JSON SCHEMAErrorItem
JSON SCHEMAErrorResponse
JSON SCHEMAErrorUpdate
JSON SCHEMAEvent
JSON SCHEMAEventField
JSON SCHEMAEventPayload
JSON SCHEMAException
JSON SCHEMAExceptionPayload
JSON SCHEMAExportTraceServiceRequest
JSON SCHEMAExportTraceServiceResponse
JSON SCHEMAKeyValue
JSON SCHEMANotificationPayload
JSON SCHEMANotifier
JSON SCHEMAOrganization
JSON SCHEMAPivot
JSON SCHEMAPivotValue
JSON SCHEMAProject
JSON SCHEMAProjectCreate
JSON SCHEMAProjectUpdate
JSON SCHEMARelease
JSON SCHEMAResourceSpans
JSON SCHEMAScopeSpans
JSON SCHEMASessionCount
JSON SCHEMASessionPayload
JSON SCHEMASpan
JSON SCHEMAStabilityTrend
JSON SCHEMAStackFrame
JSON SCHEMAStackFramePayload
JSON SCHEMAThreadPayload
JSON SCHEMATrend
JSON SCHEMAUser
JSON SCHEMAScroll within the panel for all 45 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Bugsnag Structure
JSON STRUCTURESecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Bugsnag — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/bugsnag · machine-readable index on apis.io
This is an independent, third-party profile of Bugsnag, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.