How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Sonarly Incidents API

Read incidents and their analysis runs.

Sonarly Incidents API is one of 3 APIs that Sonarly publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Incidents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, rate-limit docs, and an AsyncAPI specification.

This API exposes 3 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 2026-04-30.

Requests are made against a single base URL, https://sonarly.com.

3 operations 3 paths 6 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-04-30
Base URL
https://sonarly.com/api/v1/public
Authentication
HTTP Bearer
Contact
Resource Areas
1

Authentication & Security 1

Sonarly Incidents API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token. For the public API this is a read-only key (sklive); for the setup API it is the setup-scoped token from GET /api/setup/{setupid}/status.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Incidents 3

Read incidents and their analysis runs.

GET
/api/v1/public/incidents
List incidents
listIncidents 6 params → 200401429
GET
/api/v1/public/incidents/{id}
Retrieve an incident
getIncident 1 param → 200401404
GET
/api/v1/public/incidents/{id}/runs
List an incident's analysis runs
listIncidentRuns 1 param → 200401404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are Bug (31 properties), AgentRun (13 properties), ListEnvelope (3 properties). Each schema is shown below with its type and property counts.

Bug
object
A triaged, deduplicated production bug.
31 properties
AgentRunList
AgentRun
object
A single agent analysis/fix run for a bug or incident.
13 properties
ListEnvelope
object
3 properties
IncidentList
Incident
An incident; same shape as Bug.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sonarly-incidents-api-openapi.yml Raw ↑

Other APIs Sonarly publishes across the network.

Sonarly Bugs API
Sonarly Setup API
Where this information came from

This is an independent, third-party profile of Sonarly Incidents API, 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.