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

Splunk Observability Cloud Incidents and alerts API

The Incidents and alerts API from Splunk Observability Cloud — 7 operation(s) for incidents and alerts.

Splunk Observability Cloud Incidents and alerts API is one of 49 APIs that Splunk Observability Cloud publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Incidents and alerts. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and an AsyncAPI specification.

This API exposes 10 operations across 7 paths. It is described by OpenAPI 3.2.0, at version 3.7.1.

Requests are made against a single base URL, https://api.{REALM}.observability.splunkcloud.com/v2.

10 operations 7 paths 0 schemas 1 DELETE4 GET1 POST4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.7.1
Base URL
https://api.{REALM}.observability.splunkcloud.com/v2
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Splunk Observability Cloud Incidents and alerts API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-SF-Token (SessionToken). By default, every request must be authenticated.

  • SessionToken — Splunk Observability Cloud session token or org access token.

Paths & Operations 10

Across 7 paths, the API surfaces 10 operations — 1 DELETE, 4 GET, 1 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Incidents and alerts 10
GET
/alertmuting
Retrieve Muting Rules Using Query
6 params → 200
POST
/alertmuting
Create Single Muting Rule
3 params body → 201
GET
/alertmuting/{id}
Retrieve Muting Rule ID
2 params → 200
PUT
/alertmuting/{id}
Update Single Muting Rule
4 params body → 200
DELETE
/alertmuting/{id}
Delete Single Muting Rule
2 params → 200400404
PUT
/alertmuting/{id}/unmute
Unmute Single Muting Rule
2 params → 200
GET
/incident
Retrieve Incidents
5 params → 200
GET
/incident/{id}
Retrieve Incident ID
2 params → 200
PUT
/incident/{id}/clear
Clear Single Incident
2 params → 200
PUT
/incident/clear
Clear Incidents
2 params body → 201400401

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

splunk-observability-incidents-and-alerts-api-openapi.yml Raw ↑

Other APIs Splunk Observability Cloud publishes across the network.

Splunk Observability Cloud MCP Server
Splunk Observability Cloud APM service topology API
Splunk Observability Cloud APM visibility filters API
Splunk Observability Cloud Automated archival API
Splunk Observability Cloud Backfill API
Splunk Observability Cloud Charts API
Splunk Observability Cloud Client Inventory API
Splunk Observability Cloud Dashboard groups API
Splunk Observability Cloud Dashboards API
Splunk Observability Cloud Data links API
Splunk Observability Cloud Detectors API
Splunk Observability Cloud Download APM traces API
Where this information came from

This is an independent, third-party profile of Splunk Observability Cloud Incidents and alerts 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.