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

OpenObserve Incidents API

Alert incident correlation & management operations

OpenObserve Incidents API is one of 33 APIs that OpenObserve publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incidents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 5 operations across 5 paths, and defines 31 schemas. It is described by OpenAPI 3.1.0, at version 0.90.0.

Requests are made against the base URL https://api.openobserve.ai.

5 operations 5 paths 31 schemas 3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.90.0
Base URL
https://api.openobserve.ai
Authentication
API Key, HTTP Basic
License
AGPL-3.0
Resource Areas
1

Authentication & Security 2

OpenObserve Incidents API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (Authorization). It accepts HTTP basic authentication (BasicAuth).

Paths & Operations 5

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

Incidents 5

Alert incident correlation & management operations

GET
/api/v2/{org_id}/alerts/incidents
List alert incidents
ListIncidents 4 params → 200500
GET
/api/v2/{org_id}/alerts/incidents/stats
Get incident statistics
GetIncidentStats 1 param → 200500
GET
/api/v2/{org_id}/alerts/incidents/{incident_id}
Get incident details
GetIncident 2 params → 200404
POST
/api/v2/{org_id}/alerts/incidents/{incident_id}/rca
Trigger RCA analysis for an incident
TriggerIncidentRca 4 params → 200404503
PATCH
/api/v2/{org_id}/alerts/incidents/{incident_id}/update
Update incident fields
UpdateIncident 2 params body → 200403

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are Alert (23 properties), Incident (15 properties), TriggerCondition (10 properties), QueryCondition (9 properties). Each schema is shown below with its type and property counts.

IncidentStatus
string
Incident status lifecycle: Open → Acknowledged → Resolved
GroupingConfig
object
Configuration for alert grouping
4 properties
QueryCondition
object
9 properties
IncidentTopology
object
Alert flow graph showing how alerts cascaded across services over time
4 properties 3 required
EdgeType
string
Type of relationship between alert nodes
Alert
object
23 properties
SearchEventType
string
KeyType
string
Classification of correlation key strength for hierarchical upgrade logic Hierarchy: AlertId (weakest) → Secondary → Primary (strongest) Upgrades only move UP…
CorrelationReason
string
How an alert was correlated to an incident
DeduplicationConfig
object
Per-alert deduplication configuration (from main branch) This is stored on each Alert and specifies which fields to use for fingerprinting. This matches the st…
4 properties
RcaResponse
object
Response for RCA analysis
1 property 1 required
IncidentAlert
object
Alert info within an incident (junction table representation)
6 properties 6 required
Aggregation
object
3 properties 2 required
Condition
object
4 properties 3 required
UpdatePayload
Update payload enum for incident field updates Ensures only one field can be updated per request
IncidentStats
object
Statistics for incidents dashboard
8 properties 7 required
CompareHistoricData
object
1 property 1 required
Incident
object
Main incident entity - a group of correlated alerts
15 properties 9 required
SendStrategy
string
Strategy for sending grouped alert notifications
FrequencyType
string
Operator
string
RowTemplateType
string
AlertEdge
object
Edge in the alert flow graph
3 properties 3 required
IncidentSeverity
string
Incident severity levels (P1 = highest priority)
AggFunction
string
TriggerCondition
object
10 properties
IncidentWithAlerts
Incident with its alerts (for detail view)
ListIncidentsResponse
object
Response for list incidents
2 properties 2 required
QueryType
string
StreamType
string
AlertNode
object
Node in the alert flow graph
6 properties 6 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openobserve-incidents-api-openapi.yml Raw ↑

Other APIs OpenObserve publishes across the network.

OpenObserve Actions API
OpenObserve Alerts API
OpenObserve Clusters API
OpenObserve Dashboards API
OpenObserve Folders API
OpenObserve Functions API
OpenObserve Groups API
OpenObserve Key API
OpenObserve Keys API
OpenObserve KV API
OpenObserve Logs API
OpenObserve MCP API
Where this information came from

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