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

OpenText Cybersecurity Notifications API

The Notifications API from OpenText Cybersecurity — 3 operation(s) for notifications.

OpenText Cybersecurity Notifications API is one of 29 APIs that OpenText Cybersecurity publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Notification. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and 2 JSON Schemas.

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

Requests are made against a single base URL, https://api.ams.fortify.com.

3 operations 3 paths 5 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Base URL
https://api.ams.fortify.com
Resource Areas
1

Paths & Operations 3

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

Notifications 3
GET
/api/v3/notifications/unread
Get a list of unread notifications
NotificationsV3_GetUnreadNotifications 6 params → 200400401429500
GET
/api/v3/notifications/read
Get a list of read notifications
NotificationsV3_GetReadNotifications 6 params → 200400401429500
POST
/api/v3/notifications/markasread
Marks the notification(s) as read
NotificationsV3_MarkNotificaitonsAsRead body → 204401429500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Notification (7 properties), NotificationListResponse (4 properties), Error (2 properties), MarkNotificaitonsAsReadRequest (1 property). Each schema is shown below with its type and property counts.

NotificationListResponse
object
Generic List Response
4 properties
Notification
object
Notification
7 properties
Error
object
Error
2 properties
ErrorResponse
object
Error Response
1 property
MarkNotificaitonsAsReadRequest
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opentext-cybersecurity-notifications-api-openapi.yml Raw ↑

Other APIs OpenText Cybersecurity publishes across the network.

Webroot Unity API
OpenText Cybersecurity Applications API
OpenText Cybersecurity Attributes API
OpenText Cybersecurity Audit Template API
OpenText Cybersecurity Fortify On Demand Connect Networks API
OpenText Cybersecurity Multi Factor Authorization Code API
OpenText Cybersecurity Releases API
OpenText Cybersecurity Reports API
OpenText Cybersecurity Scans API
OpenText Cybersecurity Tenant Entitlements API
OpenText Cybersecurity Tenant Heat Maps API
OpenText Cybersecurity Tenants API
Where this information came from

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