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

Viridi Notification Target Controller API

The notification-target-controller API from Viridi — 4 operation(s) for notification-target-controller.

Viridi Notification Target Controller API is one of 56 APIs that Viridi publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include notification-target-controller. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 4 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version 3.7.0.

Requests are made against a single base URL, https://vista.viridiparente.com.

5 operations 4 paths 16 schemas 1 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.7.0
Base URL
https://vista.viridiparente.com
Authentication
HTTP Loginpassword
Resource Areas
1

Authentication & Security 1

Viridi Notification Target Controller API declares 1 security scheme for authenticating requests. It uses HTTP loginpassword authentication (HTTP_login_form).

  • HTTP_login_form — Enter Username / Password

Paths & Operations 5

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

notification-target-controller 5
POST
/api/notification/target
Save notification target (saveNotificationTarget)
saveNotificationTarget body → 200
POST
/api/notification/target/recipients
Get recipients for notification target config…
getRecipientsForNotificationTargetConfig 2 params body → 200
GET
/api/notification/targets
Get notification targets by ids (getNotificationTargetsByIds)
getNotificationTargets_1_1 7 params → 200
GET
/api/notification/target/{id}
Get notification target by id (getNotificationTargetById)
getNotificationTargetById 1 param → 200
DELETE
/api/notification/target/{id}
Delete notification target by id (deleteNotificationTargetById)
deleteNotificationTargetById 1 param → 200

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are User (12 properties), SlackConversation (6 properties), NotificationTarget (5 properties), PageDataNotificationTarget (4 properties). Each schema is shown below with its type and property counts.

UserId
object
2 properties 2 required
NotificationTarget
object
5 properties 2 required
JsonNode
A value representing the any type (object or primitive)
RoleId
object
2 properties 2 required
PlatformUsersNotificationTargetConfig
1 required
SlackConversation
object
6 properties 3 required
NotificationTargetId
object
2 properties 2 required
MicrosoftTeamsNotificationTargetConfig
2 required
User
object
A JSON value representing the User.
12 properties 2 required
NotificationTargetConfig
object
2 properties 1 required
UsersFilter
object
1 property 1 required
PageDataUser
object
4 properties
TenantId
object
2 properties 2 required
PageDataNotificationTarget
object
4 properties
CustomerId
object
2 properties 2 required
SlackNotificationTargetConfig
1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

viridi-parente-notification-target-controller-api-openapi.yml Raw ↑

Other APIs Viridi publishes across the network.

Viridi Admin Controller API
Viridi Alarm Comment Controller API
Viridi Alarm Controller API
Viridi Asset Controller API
Viridi Asset Profile Controller API
Viridi Audit Log Controller API
Viridi Auth Controller API
Viridi Cbrs Controller API
Viridi Component Descriptor Controller API
Viridi Customer Controller API
Viridi Dashboard Controller API
Viridi Device Connectivity Controller API
Where this information came from

This is an independent, third-party profile of Viridi Notification Target Controller 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.