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

Root (fka Slim.ai) Notifications API

The Notifications API from Root (fka Slim.ai) — 4 operation(s) for notifications.

Root (fka Slim.ai) Notifications API is one of 20 APIs that Root (fka Slim.ai) 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 and an API reference.

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

Requests are made against a single base URL, https://api.root.io.

4 operations 4 paths 8 schemas 2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.root.io
Authentication
HTTP Basic
Terms of Service
Resource Areas
1

Authentication & Security 1

Root (fka Slim.ai) Notifications API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (BasicAuth).

Paths & Operations 4

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

Notifications 4
GET
/v3/notifications
List notifications
5 params → 200
POST
/v3/notifications/read_all
Mark all notifications as seen
→ 204
GET
/v3/notifications/unread-count
Count unread notifications
→ 200
PATCH
/v3/notifications/{notificationID}
Patch a notification (mark seen/unseen)
1 param body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are NotificationData (6 properties), NotificationResponse (5 properties), Cursor (4 properties), ListNotificationsResponse (2 properties). Each schema is shown below with its type and property counts.

Cursor
object
4 properties
v3.CVESeverity
string
ListNotificationsResponse
object
2 properties
NotificationResponse
object
5 properties
FixedCVE
object
2 properties
PatchNotificationRequest
object
1 property 1 required
NotificationData
object
6 properties
UnreadCountResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

root-fka-slimai-notifications-api-openapi.yml Raw ↑

Other APIs Root (fka Slim.ai) publishes across the network.

Root (fka Slim.ai) Accounts API
Root (fka Slim.ai) API Keys API
Root (fka Slim.ai) Authentication API
Root (fka Slim.ai) AVR API
Root (fka Slim.ai) Billing API
Root (fka Slim.ai) Core - Discovered Packages V3 API
Root (fka Slim.ai) CveFeed API
Root (fka Slim.ai) Discovery API
Root (fka Slim.ai) Invitations API
Root (fka Slim.ai) Organizations API
Root (fka Slim.ai) OSVFeed API
Root (fka Slim.ai) Package API
Where this information came from

This is an independent, third-party profile of Root (fka Slim.ai) 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.