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

Harness Notification Channels API

This contains APIs for Notification Channels

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

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

This API exposes 18 operations across 9 paths, and defines 14 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://app.harness.io, https://{vanity}.

18 operations 9 paths 14 schemas 3 DELETE9 GET3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://app.harness.io
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Harness Notification Channels API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (x-api-key). By default, every request must be authenticated.

  • x-api-key — API key is a token provided while making the API calls. This is used to authenticate the client at the exposed endpoint.

Paths & Operations 18

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

Notification Channels 18

This contains APIs for Notification Channels

GET
/v1/orgs/{org}/projects/{project}/notification-channels
List Notification channels
list-notification-channels 10 params → 200
POST
/v1/orgs/{org}/projects/{project}/notification-channels
Create Notification channel
create-notification-channel 3 params body → 201
GET
/v1/orgs/{org}/projects/{project}/notification-channels/{notification-channel}
Get Notification channel
get-notification-channel 4 params → 200
DELETE
/v1/orgs/{org}/projects/{project}/notification-channels/{notification-channel}
Delete Notification Channel
delete-notification-channel 4 params → 204400
PUT
/v1/orgs/{org}/projects/{project}/notification-channels/{notification-channel}
Update Notification Channel
update-notification-channel 4 params body → 200
GET
/v1/orgs/{org}/notification-channels
List Notification channels at org level
list-notification-channels-org 9 params → 200
POST
/v1/orgs/{org}/notification-channels
Create Notification channel
create-notification-channel-org 2 params body → 201
GET
/v1/notification-channels
List Notification channels at account level
list-notification-channels-account 8 params → 200
POST
/v1/notification-channels
Create Notification channel
create-notification-channel-account 1 param body → 201
GET
/v1/orgs/{org}/notification-channels/{notification-channel}
Get Notification channel
get-notification-channel-org 3 params → 200
DELETE
/v1/orgs/{org}/notification-channels/{notification-channel}
Delete Notification Channel
delete-notification-channel-org 3 params → 204400
PUT
/v1/orgs/{org}/notification-channels/{notification-channel}
Update Notification Channel
update-notification-channel-org 3 params body → 200
GET
/v1/notification-channels/{notification-channel}
Get Notification channel
get-notification-channel-account 2 params → 200
DELETE
/v1/notification-channels/{notification-channel}
Delete Notification Channel
delete-notification-channel-account 2 params → 204400
PUT
/v1/notification-channels/{notification-channel}
Update Notification Channel
update-notification-channel-account 2 params body → 200
GET
/v1/orgs/{org}/validate-channels/{notification-channel}
Validate unique identifier for notification channel
validate-notification-channel-identifier-org 3 params → 200302
GET
/v1/orgs/{org}/projects/{project}/validate-channels/{notification-channel}
Validate Notification Channel Identifier
validate-notification-channel-identifier 4 params → 200302
GET
/v1/validate-channels/{notification-channel}
Validate Notification channel identifier
validate-notification-channel-identifier-account 2 params → 200302

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are NotificationRuleDTO (11 properties), ChannelDTO (11 properties), NotificationChannelDTO (10 properties), NotificationEventConfigDTO (4 properties). Each schema is shown below with its type and property counts.

ChannelType
string
Notification Channel Type
NotificationConditionDTO
object
2 properties
NotificationEventConfigDTO
object
4 properties
ValidateIdentifierDTO
object
1 property
UserGroupDTO1
object
3 properties
NotificationRuleDTO
object
Notification Rule DTO
11 properties
NotificationTemplateInputsDTO
object
3 properties 2 required
NotificationChannelDTO
object
Notification Channel DTO
10 properties 2 required
CustomNotificationTemplateDTO
object
3 properties
WebHookHeaders
object
2 properties
NotificationEventParamsDTO
object
Notification Event Params
1 property
ResourceTypeEnum
string
ChannelDTO
object
11 properties
Status
string
Notification Rule Status

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

harness-notification-channels-api-openapi.yml Raw ↑

Other APIs Harness publishes across the network.

Harness Continuous Integration API
Harness Continuous Delivery and GitOps API
Harness Feature Management and Experimentation API
Harness Cloud Cost Management API
Harness Chaos Engineering API
Harness Security Testing Orchestration API
Harness Internal Developer Portal API
Harness Code Repository API
Harness Service Reliability Management API
Harness Infrastructure as Code Management API
Harness Supply Chain Security API
Harness Software Engineering Insights API
Where this information came from

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