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

Sageox Notifications API

Read, manage, and stream real-time notifications. Supports SSE (Server-Sent Events) for live delivery, bulk operations (mark read, delete), and preference-based filtering. Notifications originate from workflows, recordings, and system events.

Sageox Notifications API is one of 23 APIs that Sageox 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.

This API exposes 14 operations across 11 paths, and defines 3 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against 3 base URLs: http://localhost:3000, https://test.sageox.ai, https://sageox.ai.

14 operations 11 paths 3 schemas 2 DELETE7 GET2 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Servers
http://localhost:3000
https://test.sageox.ai
https://sageox.ai
Authentication
HTTP Bearer
Contact
SageOx Team
License
MIT
Resource Areas
1

Authentication & Security 1

Sageox Notifications API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — JWT token obtained from the auth service (/api/auth/token). Token is validated using JWKS from the auth service. Required claims: sub (userid), email, name, ti…

Paths & Operations 14

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

Notifications 14

Read, manage, and stream real-time notifications. Supports SSE (Server-Sent Events) for live delivery, bulk operations (mark read, delete), and preference-based filtering. Notific…

GET
/api/v1/notifications
List notifications
getNotifications 2 params → 200401500
POST
/api/v1/notifications
Create notification
createNotification body → 200400401500
DELETE
/api/v1/notifications/{id}
Delete notification
deleteNotification 1 param → 200400401404500
PUT
/api/v1/notifications/{id}/read
Mark notification as read or unread
updateNotificationRead 1 param body → 200400401404500
GET
/api/v1/notifications/stream
Server-Sent Events stream for real-time notifications
streamNotifications → 200401500
GET
/api/v1/notifications/stats
Get notification statistics
getNotificationStats → 200401500
POST
/api/v1/notifications/read-all
Mark all notifications as read
markAllNotificationsRead → 200401500
GET
/api/v1/notifications/grouped
Get grouped notifications
getGroupedNotifications 3 params → 200401500
GET
/api/v1/notifications/group-items
Get notification group items
getNotificationGroupItems 5 params → 200400401500
DELETE
/api/v1/notifications/bulk
Bulk delete notifications
bulkDeleteNotifications body → 200400401500
GET
/api/v1/notifications/preferences
Get notification preferences
getNotificationPreferences → 200401500
PUT
/api/v1/notifications/preferences
Update notification preferences
updateNotificationPreferences body → 200400401500
GET
/api/v1/notifications/preferences/master
Get master notification toggles
getMasterNotificationToggles → 200401500
PUT
/api/v1/notifications/preferences/master
Update master notification toggles
updateMasterNotificationToggles body → 200400401500

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are NotificationDTO (12 properties), PaginationMeta (4 properties), ErrorResponse (2 properties). Each schema is shown below with its type and property counts.

PaginationMeta
object
Pagination metadata included in all list responses. Use offset + limit for the next page; stop when hasMore is false.
4 properties 4 required
NotificationDTO
object
A user notification. Notifications are created by workflows, recordings, and system events, and delivered via polling or SSE streaming.
12 properties 10 required
ErrorResponse
object
Standard error response returned by all endpoints on failure.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

sageox-notifications-api-openapi.yml Raw ↑

Other APIs Sageox publishes across the network.

Sageox Admin API
Sageox AgentX API
Sageox API Keys API
Sageox Auth API
Sageox CLI API
Sageox Devices API
Sageox Firmware Admin API
Sageox Firmware OTA API
Sageox Git API
Sageox Guidance API
Sageox Health API
Sageox LLM API
Where this information came from

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