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

InfluxData NotificationEndpoints API

The NotificationEndpoints API from InfluxData — 4 operation(s) for notificationendpoints.

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

Tagged areas include NotificationEndpoints. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and a getting-started guide.

This API exposes 9 operations across 4 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 2.0.1.

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

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

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.1
Base URL
https://us-east-1-1.aws.cloud2.influxdata.com/api/v2
Authentication
API Key, HTTP Basic
License
Resource Areas
1

Authentication & Security 2

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

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

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.

NotificationEndpoints 9
GET
/notificationEndpoints
List all notification endpoints
GetNotificationEndpoints 4 params → 200default
POST
/notificationEndpoints
Add a notification endpoint
CreateNotificationEndpoint body → 201default
GET
/notificationEndpoints/{endpointID}
Retrieve a notification endpoint
GetNotificationEndpointsID 2 params → 200default
PUT
/notificationEndpoints/{endpointID}
Update a notification endpoint
PutNotificationEndpointsID 2 params body → 200404default
PATCH
/notificationEndpoints/{endpointID}
Update a notification endpoint
PatchNotificationEndpointsID 2 params body → 200404default
DELETE
/notificationEndpoints/{endpointID}
Delete a notification endpoint
DeleteNotificationEndpointsID 2 params → 204404default
GET
/notificationEndpoints/{endpointID}/labels
List all labels for a notification endpoint
GetNotificationEndpointsIDLabels 2 params → 200default
POST
/notificationEndpoints/{endpointID}/labels
Add a label to a notification endpoint
PostNotificationEndpointIDLabels 2 params body → 201default
DELETE
/notificationEndpoints/{endpointID}/labels/{labelID}
Delete a label from a notification endpoint
DeleteNotificationEndpointsIDLabelsID 3 params → 204404default

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are NotificationEndpointBase (11 properties), Label (4 properties), Error (4 properties), Links (3 properties). Each schema is shown below with its type and property counts.

LabelResponse
object
2 properties
PostNotificationEndpoint
Error
object
4 properties 1 required
NotificationEndpoint
NotificationEndpointUpdate
object
3 properties
NotificationEndpointBase
object
11 properties 2 required
TelegramNotificationEndpoint
object
NotificationEndpointType
string
Labels
array
PagerDutyNotificationEndpoint
object
LabelMapping
object
A label mapping contains a label ID to attach to a resource.
1 property 1 required
Links
object
URI pointers for additional paged results.
3 properties 1 required
SlackNotificationEndpoint
object
LabelsResponse
object
2 properties
HTTPNotificationEndpoint
object
Link
string
URI of resource.
NotificationEndpointDiscriminator
Label
object
4 properties
NotificationEndpoints
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

influxdata-notificationendpoints-api-openapi.yml Raw ↑

Other APIs InfluxData publishes across the network.

InfluxData Authorizations (API tokens) API
InfluxData Backup API
InfluxData Bucket Schemas API
InfluxData Buckets API
InfluxData Cells API
InfluxData Checks API
InfluxData Config API
InfluxData Dashboards API
InfluxData Data I/O endpoints API
InfluxData DBRPs API
InfluxData Debug API
InfluxData Delete API
Where this information came from

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