Confluent | the Data Streaming Platform

Confluent | the Data Streaming Platform Resource Preferences (notifications/v1) API

[![General Availability](https://img.shields.io/badge/Lifecycle%20Stage-General%20Availability-%2345c6e8)](#section/Versioning/API-Lifecycle-Policy) `ResourcePreference` objects represent the intent of the customers to enable or disable all notifications at the resource level. A ResourcePreference is created for a specific Confluent Cloud Resource (e.g., a connector) and determines whether the user will receive notifications for that resource. This API allows you to create, retrieve, update and delete resourcePreferences. Related guide: [Cloud Notifications](https://docs.confluent.io/cloud/current/monitoring/configure-notifications.html#notifications-for-ccloud). ## The Resource Preferences 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

POST /notifications/v1/resource-preferences Set notification preference for a resource · Create a Resource Preference #
Ask an LLM
“How do I turn notifications on or off for one specific resource?”
“Can I mute notifications for a single Kafka cluster?”
Tell an agent
Set notification state {current_state} for resource {resource} of type {resource_type}.
Mute notifications for resource {resource}.
GET /notifications/v1/resource-preferences/{id} Get a resource notification preference · Read a Resource Preference #
Ask an LLM
“What notification setting applies to a resource preference I created?”
“Can I read a resource preference by its id?”
Tell an agent
Show resource preference {id}.
Get the notification state of resource preference {id}.
PATCH /notifications/v1/resource-preferences/{id} Update a resource notification preference · Update a Resource Preference #
Ask an LLM
“Can I flip an existing resource preference from muted to enabled?”
“Is it possible to change a resource preference's state?”
Tell an agent
Set resource preference {id} to state {current_state}.
Re-enable notifications on resource preference {id}.
DELETE /notifications/v1/resource-preferences/{id} Delete a resource notification preference · Delete a Resource Preference #
Ask an LLM
“How do I remove a per-resource notification override?”
“Can I delete a resource preference so defaults apply again?”
Tell an agent destructive · confirm first
Delete resource preference {id}.
Remove the notification override with preference id {id}.
GET /notifications/v1/resource-preferences:lookup Look up a resource's notification preference · Lookup a resource preference by filter (returns one) #
Ask an LLM
“What notification preference is set for a given resource and resource type?”
“Can I find a preference by the resource itself instead of its id?”
Tell an agent
Look up the notification preference for resource {resource} of type {resource_type}.
Find the preference for {resource_type} resource {resource}.

Documentation

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

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/confluent-the-data-streaming-platform/refs/heads/main/openapi/confluent-the-data-streaming-platform-resource-preferences-notifications-v1-api-openapi.yml

Other Resources

🔗
ToolCrosswalk
https://raw.githubusercontent.com/api-evangelist/confluent-the-data-streaming-platform/refs/heads/main/mcp/confluent-the-data-streaming-platform-tool-crosswalk.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/confluent-the-data-streaming-platform/refs/heads/main/data-model/confluent-the-data-streaming-platform-data-model.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-the-data-streaming-platform:confluent-the-data-streaming-platform-resource-preferences-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-the-data-streaming-platform-resource-preferences-notifications-v1-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Confluent Cloud Resource Preferences (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: '# Introduction


    Note


    This documents the collection of Confluent Cloud APIs.'
servers:
- url: https://api.confluent.cloud
  description: Confluent Cloud API
tags:


# --- truncated at 32 KB (46 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/confluent-the-data-streaming-platform/refs/heads/main/openapi/confluent-the-data-streaming-platform-resource-preferences-notifications-v1-api-openapi.yml