Confluent

Confluent User Notifications (notifications/v1) API

[![Early Access](https://img.shields.io/badge/Lifecycle%20Stage-Early%20Access-%2345c6e8)](#section/Versioning/API-Lifecycle-Policy) [![Request Access To User Notifications API v1](https://img.shields.io/badge/-Request%20Access%20To%20User%20Notifications%20API%20v1-%23bc8540)](mailto:ccloud-api-access+notifications-v1-early-access@confluent.io?subject=Request%20to%20join%20notifications/v1%20API%20Early%20Access&body=I%E2%80%99d%20like%20to%20join%20the%20Confluent%20Cloud%20API%20Early%20Access%20for%20notifications/v1%20to%20provide%20early%20feedback%21%20My%20Cloud%20Organization%20ID%20is%20%3Cretrieve%20from%20https%3A//confluent.cloud/settings/billing/payment%3E.) `UserNotification` objects represent in-app notifications scoped to a specific Confluent Cloud user. Each notification carries a severity, references the Confluent Cloud resource it relates to, and tracks whether the user has read it. This API lets you list and retrieve your notifications, mark notifications as read or unread, and fetch an unread-count summary. `read` is the only mutable field on this resource; `PATCH` requests with values for other fields will have those values silently ignored. Two `PATCH` shapes are supported: - `PATCH /user-notifications/{id}` — update a single notification by id. - `PATCH /user-notifications` — update the read state of every notification matching the supplied filter query parameters. The body is a narrow payload (`{ "read": true | false }`) and the same filters accepted by the list endpoint scope which notifications are updated (with the exception of `include`, which is a list-only partial-response selector). The heavier `integrations` and `recommended_actions` fields are populated on single-resource reads (`GET /user-notifications/{id}`) and omitted from list responses by default to keep collection payloads slim. Use the `include` query parameter on the list endpoint to opt in to populating these fields (`?include=integrations,recommended_actions`). Related guide: [Cloud Notifications](https://docs.confluent.io/cloud/current/monitoring/configure-notifications.html#notifications-for-ccloud). ## The User Notifications Model

GitHub OpenAPI

Operations 5

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /notifications/v1/user-notifications List my notifications · List of User Notifications #
Ask an LLM
“What unread critical notifications do I have?”
“Can I filter my notifications by severity, resource or time window?”
Tell an agent
List my unread notifications.
List notifications with severity {severity} in the last {time_range}.
GET /notifications/v1/user-notifications/{id} Read a notification · Read a User Notification #
Ask an LLM
“What recommended actions come with a particular notification?”
“Can I open one notification by its ID?”
Tell an agent
Show notification {id}.
Get the details and recommended actions of notification {id}.
PATCH /notifications/v1/user-notifications/{id} Mark a notification read or unread · Update a User Notification #
Ask an LLM
“How do I mark a single notification as read?”
“Can I flip one notification back to unread?”
Tell an agent
Mark notification {id} as read: {read}.
Set notification {id} back to unread.
PATCH /notifications/v1/user-notifications:mark-all Mark many notifications read or unread · Mark multiple notifications read or unread #
Ask an LLM
“Can I mark all my notifications as read at once?”
“Is it possible to bulk mark only critical notifications as read?”
Tell an agent
Mark all my notifications read: {read}.
Set read to {read} on every notification with severity {severity}.
GET /notifications/v1/user-notifications:summary Get a summary of my notifications · Get notification summary #
Ask an LLM
“How many notifications do I have overall?”
“Can I get a quick summary count of my notifications?”
Tell an agent
Give me a summary of my notifications.
Show my notification counts.

Documentation

📖
APIReference
https://docs.confluent.io/cloud/current/api.html
📖
APIReference
https://api.telemetry.confluent.cloud/docs

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/confluent/refs/heads/main/openapi/confluent-user-notifications-notifications-v1-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/confluent:confluent-user-notifications-notifications-v1-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

confluent-user-notifications-notifications-v1-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Confluent User Notifications (notifications/v1) API
  version: ''
  x-api-id: 46234552-5833-42eb-ba0f-883ad3f70d2b
  x-audience: external-public
  x-logo:
    url: https://assets.confluent.io/m/1661ef5e4ff82d3d/
  description: 'Operations tagged User Notifications (notifications/v1) across 2 of this provider''s published API definitions: confluent-cloud-openapi.yaml, confluent-cloud-full.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.confluent.cloud
  description: Confluent Cloud API
tags:


# --- truncated at 32 KB (93 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/confluent/refs/heads/main/openapi/confluent-user-notifications-notifications-v1-api-openapi.yml