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 Controller API

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

Viridi Notification 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-controller. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 15 operations across 12 paths, and defines 34 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.

15 operations 12 paths 34 schemas 2 DELETE7 GET4 POST2 PUT

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 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 15

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

notification-controller 15
PUT
/api/notifications/read
Mark all notifications as read (markAllNotificationsAsRead)
markAllNotificationsAsRead 1 param → 200
PUT
/api/notification/{id}/read
Mark notification as read (markNotificationAsRead)
markNotificationAsRead 1 param → 200
GET
/api/notification/settings
Get notification settings (getNotificationSettings)
getNotificationSettings → 200
POST
/api/notification/settings
Save notification settings (saveNotificationSettings)
saveNotificationSettings body → 200
GET
/api/notification/settings/user
Get user notification settings
getUserNotificationSettings → 200
POST
/api/notification/settings/user
Save user notification settings
saveUserNotificationSettings body → 200
POST
/api/notification/request
Create notification request (createNotificationRequest)
createNotificationRequest body → 200
POST
/api/notification/request/preview
Get notification request preview (getNotificationRequestPreview)
getNotificationRequestPreview 1 param body → 200
GET
/api/notifications
Get notifications (getNotifications)
getNotifications 7 params → 200
GET
/api/notifications/unread/count
Get unread notifications count (getUnreadNotificationsCount)
getUnreadNotificationsCount 1 param → 200
GET
/api/notification/requests
Get notification requests (getNotificationRequests)
getNotificationRequests 5 params → 200
GET
/api/notification/request/{id}
Get notification request by id (getNotificationRequestById)
getNotificationRequestById 1 param → 200
DELETE
/api/notification/request/{id}
Delete notification request (deleteNotificationRequest)
deleteNotificationRequest 1 param → 200
GET
/api/notification/deliveryMethods
Get available delivery methods (getAvailableDeliveryMethods)
getAvailableDeliveryMethods → 200
DELETE
/api/notification/{id}
Delete notification (deleteNotification)
deleteNotification 1 param → 200

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are NotificationRequestInfo (15 properties), NotificationRequest (13 properties), Notification (11 properties), Button (7 properties). Each schema is shown below with its type and property counts.

NotificationId
object
2 properties 2 required
Button
object
7 properties
NotificationSettings
object
1 property 1 required
Notification
object
11 properties
NotificationRequest
object
13 properties 1 required
UserId
object
2 properties 2 required
PageDataNotificationRequestInfo
object
4 properties
WebDeliveryMethodNotificationTemplate
2 required
EmailDeliveryMethodNotificationTemplate
2 required
NotificationRequestConfig
object
1 property
NotificationRequestId
object
2 properties 2 required
SlackNotificationDeliveryMethodConfig
1 required
TenantId
object
2 properties 2 required
SmsDeliveryMethodNotificationTemplate
1 required
MobileAppNotificationDeliveryMethodConfig
1 required
UserNotificationSettings
object
1 property 1 required
NotificationRuleId
object
2 properties 2 required
PageDataNotification
object
4 properties
NotificationRequestInfo
object
15 properties 1 required
MobileAppDeliveryMethodNotificationTemplate
2 required
NotificationInfo
object
3 properties 1 required
NotificationPref
object
2 properties 1 required
NotificationTemplateConfig
object
1 property 1 required
SlackDeliveryMethodNotificationTemplate
1 required
NotificationTemplateId
object
2 properties 2 required
NotificationDeliveryMethodConfig
object
1 property 1 required
JsonNode
A value representing the any type (object or primitive)
DeliveryMethodNotificationTemplate
object
3 properties 2 required
NotificationRequestStats
object
4 properties
NotificationTemplate
object
6 properties 3 required
EntityId
object
2 properties 2 required
MicrosoftTeamsDeliveryMethodNotificationTemplate
1 required
DashboardId
object
2 properties 2 required
NotificationRequestPreview
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

viridi-parente-notification-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 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.