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

InfluxDB NotificationRules API

The NotificationRules API from InfluxDB — 4 operation(s) for notificationrules.

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

Tagged areas include Notification Rules. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an AsyncAPI specification, authentication docs, and a getting-started guide.

This API exposes 9 operations across 4 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0.

Requests are made against the base URL https://cloud2.influxdata.com/api/v2.

9 operations 4 paths 29 schemas 2 DELETE3 GET1 PATCH2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://cloud2.influxdata.com/api/v2
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

InfluxDB NotificationRules API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuthentication). An API key is passed in the header as Authorization (TokenAuthentication). By default, every request must be authenticated.

  • BasicAuthentication — Basic authentication scheme Use the HTTP Basic authentication scheme for InfluxDB /api/v2 API operations that support it: Syntax Authorization: Basic BASE64ENC…
  • TokenAuthentication — Use the [Token authentication](section/Authentication/TokenAuthentication) scheme to authenticate to the InfluxDB API. In your API requests, send an Authorizat…

Paths & Operations 9

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

NotificationRules 9
GET
/api/v2/notificationRules
List all notification rules
GetNotificationRules 6 params → 200default
POST
/api/v2/notificationRules
Add a notification rule
CreateNotificationRule body → 201default
DELETE
/api/v2/notificationRules/{ruleID}
Delete a notification rule
DeleteNotificationRulesID 2 params → 204404default
GET
/api/v2/notificationRules/{ruleID}
Retrieve a notification rule
GetNotificationRulesID 2 params → 200default
PATCH
/api/v2/notificationRules/{ruleID}
Update a notification rule
PatchNotificationRulesID 2 params body → 200404default
PUT
/api/v2/notificationRules/{ruleID}
Update a notification rule
PutNotificationRulesID 2 params body → 200404default
GET
/api/v2/notificationRules/{ruleID}/labels
List all labels for a notification rule
GetNotificationRulesIDLabels 2 params → 200default
POST
/api/v2/notificationRules/{ruleID}/labels
Add a label to a notification rule
PostNotificationRuleIDLabels 2 params body → 201default
DELETE
/api/v2/notificationRules/{ruleID}/labels/{labelID}
Delete label from a notification rule
DeleteNotificationRulesIDLabelsID 3 params → 204404default

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are NotificationRuleBase (23 properties), Error (4 properties), Label (4 properties), StatusRule (4 properties). Each schema is shown below with its type and property counts.

HTTPNotificationRuleBase
object
2 properties 1 required
SMTPNotificationRuleBase
object
4 properties 3 required
Link
string
URI of resource.
TaskStatusType
string
inactive cancels scheduled runs and prevents manual runs of the task.
SlackNotificationRule
LabelsResponse
object
2 properties
SlackNotificationRuleBase
object
3 properties 2 required
StatusRule
object
4 properties
Label
object
4 properties
PagerDutyNotificationRuleBase
object
2 properties 2 required
NotificationRuleDiscriminator
TelegramNotificationRule
Error
object
4 properties 1 required
HTTPNotificationRule
NotificationRuleBase
object
23 properties 5 required
ErrorCode
string
code is the machine-readable error code.
LabelResponse
object
2 properties
PostNotificationRule
NotificationRules
object
2 properties
NotificationRule
NotificationRuleUpdate
object
3 properties
Labels
array
Links
object
URI pointers for additional paged results.
3 properties 1 required
PagerDutyNotificationRule
SMTPNotificationRule
LabelMapping
object
A label mapping contains a label ID to attach to a resource.
1 property 1 required
TagRule
object
3 properties
RuleStatusLevel
string
The state to record if check matches a criteria.
TelegramNotificationRuleBase
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

influxdb-notificationrules-api-openapi.yml Raw ↑

Other APIs InfluxDB publishes across the network.

InfluxDB Authorizations (API tokens) API
InfluxDB Bucket Schemas API
InfluxDB Buckets API
InfluxDB Cells API
InfluxDB Checks API
InfluxDB Config API
InfluxDB Dashboards API
InfluxDB Data I/O endpoints API
InfluxDB DBRPs API
InfluxDB Delete API
InfluxDB Invokable Scripts API
InfluxDB Labels API
Where this information came from

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