Nasuni Notifications API
The Notifications API from Nasuni — 3 operation(s) for notifications.
Nasuni Notifications API is one of 30 APIs that Nasuni publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Notification. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a changelog.
This API exposes 3 operations across 3 paths, and defines 24 schemas. It is described by OpenAPI 3.2.0, at version 1.0.
Requests are made against 6 base URLs: https://hostname/api/v1, https://hostname/api/v1.1, https://hostname/api/v1.2, https://am1.portal.api.nasuni.com, https://eu1.portal.api.nasuni.com, https://ap1.portal.api.nasuni.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 6
Nasuni Notifications API declares
6 security schemes
for authenticating requests.
An API key is passed in the header as Authorization (AuthToken).
An API key is passed in the header as x-service-key (ServiceKeyHeader).
An API key is passed in the header as x-service-secret (ServiceSecretHeader).
An API key is passed in the header as x-user-key (UserKeyHeader).
It accepts HTTP bearer tokens (JWT) (HTTPBearer).
It supports OAuth 2.0 (OAuth2ClientCredentials) using the clientCredentials flow.
AuthToken— This header is required to make authenticated requests. The value format is: Token [yourauthtoken]ServiceKeyHeader— Service key for programmatic API access. Must be used together with x-service-secret.ServiceSecretHeader— Service secret for programmatic API access. Must be used together with x-service-key.UserKeyHeader— User key for user-specific API access.HTTPBearer— Bearer token obtained from /auth/token endpoint.OAuth2ClientCredentials— Standard OAuth2 Client Credentials flow (RFC 6749 §4.4). Send clientid (service key) and clientsecret (service secret) as form-encoded body parameters to the t…
Paths & Operations 3
Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.
Schemas 24
The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are NotificationDto (14 properties), Notification_3 (11 properties), Notification_2 (11 properties), Notification (11 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Nasuni 12
Other APIs Nasuni publishes across the network.
This is an independent, third-party profile of Nasuni 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.