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

Dash0 Manage Notification Channels API

The Manage Notification Channels API from Dash0 — 2 operation(s) for manage notification channels.

Dash0 Manage Notification Channels API is one of 18 APIs that Dash0 publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Manage Notification Channels. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 4 base URLs: https://api.eu-west-1.aws.dash0.com, https://api.eu-central-1.aws.dash0.com, https://api.us-west-2.aws.dash0.com, https://api.europe-west4.gcp.dash0.com.

5 operations 2 paths 35 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.eu-west-1.aws.dash0.com
Resource Areas
1

Paths & Operations 5

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

Manage Notification Channels 5
DELETE
/api/notification-channels/{originOrId}
Delete a notification channel
delete_api-notification-channels-originorid 1 param → 200403default
GET
/api/notification-channels/{originOrId}
Get a specific notification channel
get_api-notification-channels-originorid 1 param → 200default
PUT
/api/notification-channels/{originOrId}
Update a notification channel
put_api-notification-channels-originorid 1 param body → 200403default
GET
/api/notification-channels
List all notification channels for the organization
get_api-notification-channels → 200default
POST
/api/notification-channels
Create a new notification channel
post_api-notification-channels body → 200403default

Schemas 35

The contract defines 35 schemas that model the data the API accepts and returns. The most detailed are AnyValue (5 properties), AttributeFilter (4 properties), NotificationChannelRoutingAsset (4 properties), WebhookConfig (4 properties). Each schema is shown below with its type and property counts.

NotificationChannelRouting
object
2 properties 2 required
DiscordWebhookConfig
object
1 property 1 required
AnyValue
object
AnyValue is used to represent any type of attribute value. AnyValue may contain a primitive value such as a string or integer or it may contain an arbitrary ne…
5 properties
AttributeFilterAnyValue
AttributeFilterAnyValue may contain any AnyValue value.
ErrorResponse
object
1 property 1 required
IncidentIOConfig
object
2 properties 2 required
NotificationChannelDefinition
object
A notification channel configuration wrapped in a CRD-like envelope. Follows the Dash0 resource convention with kind/metadata/spec structure.
3 properties 3 required
OpsgenieConfig
object
2 properties 2 required
TeamsWebhookConfig
object
1 property 1 required
GoogleChatWebhookConfig
object
1 property 1 required
EmailConfig
object
2 properties 1 required
WebhookConfig
object
4 properties 1 required
EmailV2Config
object
2 properties 1 required
NotificationChannelRoutingAssetKind
string
AttributeFilterStringValue
string
AttributeFilterStringValue may contain a primitive value such as a regex pattern or string.
CrdSource
string
Origin of a Dash0 resource. - ui: created interactively in the Dash0 UI. - terraform: managed via the Dash0 Terraform provider. - operator: managed via the Das…
Error
object
3 properties 2 required
NotificationChannelDefinitions
array
SlackBotConfig
object
2 properties 2 required
AttributeFilterKey
string
The attribute key to be filtered.
NotificationChannelType
string
The type of notification channel integration.
AttributeFilterOperator
string
The match operation for filtering attributes. Equality Operators - is - equals (attribute exists and has a matching value) - isnot - not equals (attribute exis…
NotificationChannelRoutingAsset
object
4 properties 4 required
PagerDutyConfig
object
2 properties 2 required
AttributeFilter
object
4 properties 2 required
NotificationChannelSpec
object
4 properties 2 required
Dataset
string
Optional dataset to query across. Defaults to whatever is configured to be the default dataset for the organization.
FilterCriteria
array
Duration
string
NotificationChannelMetadata
object
3 properties 1 required
AllQuietConfig
object
1 property 1 required
IlertConfig
object
1 property 1 required
NotificationChannelAnnotations
object
2 properties
NotificationChannelLabels
object
3 properties
SlackConfig
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dash0-manage-notification-channels-api-openapi.yml Raw ↑

Other APIs Dash0 publishes across the network.

Dash0 Edge Collectors API
Dash0 Manage Agent0 Automations API
Dash0 Manage Alerting API
Dash0 Manage Dashboards API
Dash0 Manage Recording Rules API
Dash0 Manage Sampling Rules API
Dash0 Manage Signal To Metrics (BETA) API
Dash0 Manage SLOs (Private BETA) API
Dash0 Manage Spam Filters API
Dash0 Manage Synthetic Checks API
Dash0 Manage Teams and Members API
Dash0 Manage Time Series Aggregations (Private BETA) API
Where this information came from

This is an independent, third-party profile of Dash0 Manage Notification Channels 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.