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

Weka Alerts API

The Alerts API from Weka — 8 operation(s) for alerts.

Weka Alerts API is one of 45 APIs that Weka publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Alerts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 8 operations across 8 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 5.1.

Requests are made against a single base URL, /api/v2.

8 operations 8 paths 1 schemas 4 GET4 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
5.1
Base URL
https://api.docs.weka.io/api/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 8

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

Alerts 8
GET
/alerts
Get all cluster alerts
getAlerts 1 param → 200401
GET
/alerts/types
List all possible alert types
getAlertsTypes → 200401
GET
/alerts/description
List alert descriptions and recommended actions
getAlertDescription → 200401
GET
/alerts/muteList
List all active alert mute rules
getAlertMutes → 200401
PUT
/alerts/{alert_type}/mute
Mute alerts by type
muteAlertByType 1 param body → 200400401
PUT
/alerts/{alert_type}/muteAdd
Add parameters to alert mute
muteAlertAdd 1 param body → 200400401
PUT
/alerts/{alert_type}/muteRemove
Remove parameters from alert mute
muteAlertRemove 1 param body → 200400401
PUT
/alerts/{alert_type}/unmute
Unmute alerts by type
unmuteAlertByType 1 param → 200400401

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is alert (6 properties). Each schema is shown below with its type and property counts.

alert
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weka-alerts-api-openapi.yml Raw ↑

Other APIs Weka publishes across the network.

Weka Active Directory API
Weka Catalog API
Weka Cluster API
Weka Containers API
Weka DataService API
Weka Default network API
Weka Drive API
Weka Events API
Weka Failure domains API
Weka Filesystem API
Weka Filesystem group API
Weka Health API
Where this information came from

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