Confluent

Confluent Config (v1) API

[![Generally Available](https://img.shields.io/badge/Lifecycle%20Stage-Generally%20Available-%2345c6e8)](#section/Versioning/API-Lifecycle-Policy) The API allows you to manage and query schema compatibility settings and cluster configurations. Related guide: [Manage Schemas in Confluent Cloud](https://docs.confluent.io/cloud/current/sr/schemas-manage.html#manage-schemas-in-ccloud).

GitHub OpenAPI

Operations 7

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 /clusterconfig Get Schema Registry cluster config · Get cluster config #
Ask an LLM
“What cluster-wide configuration is my Schema Registry running with?”
“Can I read the cluster config information of Schema Registry?”
Tell an agent
Show the Schema Registry cluster config.
Get the cluster configuration information for my registry.
GET /config/{subject} Get a subject's compatibility settings · Get subject compatibility level #
Ask an LLM
“What compatibility level is set on a particular subject?”
“Can I fall back to the global compatibility level when a subject has none set?”
Tell an agent
Get the compatibility level for subject {subject}.
Show subject {subject}'s compatibility, defaulting to global: {defaultToGlobal}.
PUT /config/{subject} Set a subject's compatibility level · Update subject compatibility level #
Ask an LLM
“How do I change the compatibility level of just one subject?”
“Can I turn on schema normalization for a single subject only?”
Tell an agent
Set subject {subject} to compatibility {compatibility}.
Enable normalization {normalize} on subject {subject}.
DELETE /config/{subject} Revert a subject to the global compatibility · Delete subject compatibility level #
Ask an LLM
“How do I drop a subject's own compatibility setting so it follows the global default?”
“Can I delete the subject-level config for one subject?”
Tell an agent destructive · confirm first
Delete the compatibility config for subject {subject}.
Revert subject {subject} to the global compatibility default.
GET /config Get the global compatibility level · Get global compatibility level #
Ask an LLM
“What is the global compatibility level for my Schema Registry?”
“Which default rule set and metadata apply registry-wide?”
Tell an agent
Show the global compatibility level.
Get the registry-wide compatibility, normalization and rule set defaults.
PUT /config Set the global compatibility level · Update global compatibility level #
Ask an LLM
“How can I change the default compatibility level for every subject?”
“Can I switch on schema normalization registry-wide?”
Tell an agent
Set the global compatibility level to {compatibility}.
Turn global schema normalization to {normalize}.
DELETE /config Reset the global compatibility level · Delete global compatibility level #
Ask an LLM
“Can I remove my custom global compatibility level and go back to the default?”
“What happens if I delete the global compatibility config?”
Tell an agent destructive · confirm first
Delete the global compatibility config.
Reset the registry-wide compatibility level to its default.

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-config-v1-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/confluent/refs/heads/main/json-schema/confluent-config-update-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/confluent/refs/heads/main/json-schema/confluent-config-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/confluent/refs/heads/main/json-schema/confluent-cluster-config-schema.json

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-config-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-config-v1-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Confluent Config (v1) API
  x-refined-note:
  - x-api-id differs across the merged source definitions and was not carried
  - x-audience differs across the merged source definitions and was not carried
  - x-logo differs across the merged source definitions and was not carried
  version: '1.0'
  description: 'Operations tagged Config (v1) across 4 of this provider''s published API definitions: confluent-cloud-openapi.yaml, confluent-cloud-full.yaml, schema-registry-api-spec.yaml, schema-registry-openapi.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 (39 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/confluent/refs/heads/main/openapi/confluent-config-v1-api-openapi.yml