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

Confluent Configs (v3) API

[![Generally Available](https://img.shields.io/badge/Lifecycle%20Stage-Generally%20Available-%2345c6e8)](#section/Versioning/API-Lifecycle-Policy)

Confluent Configs (v3) API is one of 127 APIs that Confluent publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Configs (v3). The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 17 operations across 11 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://api.confluent.cloud.

17 operations 11 paths 18 schemas 3 DELETE8 GET3 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.confluent.cloud
Authentication
HTTP Basic, OAuth 2.0, HTTP Basic, HTTP Basic, OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 6

Confluent Configs (v3) API declares 6 security schemes for authenticating requests. It accepts HTTP basic authentication (cloud-api-key). It supports OAuth 2.0 (confluent-sts-access-token) using the clientCredentials flow. It accepts HTTP basic authentication (global-api-key). It accepts HTTP basic authentication (resource-api-key). It supports OAuth 2.0 (external-access-token) using the clientCredentials flow. It supports OAuth 2.0 (oauth) using the clientCredentials flow, exposing 4 scopes.

  • cloud-api-key — Authenticate with Cloud API Keys using HTTP Basic Auth. Treat the Cloud API Key ID as the username and Cloud API Key Secret as the password.
  • confluent-sts-access-token — Authenticate with Confluent API using this credentials (JSON Web Tokens) following OAuth 2.0.
  • global-api-key — Authenticate with Global API Keys using HTTP Basic Auth. Treat the Global API Key ID as the username and Global API Key Secret as the password.
  • resource-api-key — Authenticate with resource-specific API Keys using HTTP Basic Auth. Treat the resource-specific API Key ID as the username and resource-specific API Key Secret…
  • external-access-token — Authenticate with Confluent API using this credentials (JSON Web Tokens) following OAuth 2.0.
  • oauth — Authenticate with OAuth 2.0. Currently this is only supported for partner APIs.

Paths & Operations 17

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

Configs (v3) 17

[![Generally Available](https://img.shields.io/badge/Lifecycle%20Stage-Generally%20Available-%2345c6e8)](section/Versioning/API-Lifecycle-Policy)

GET
/kafka/v3/clusters/{cluster_id}/broker-configs
List Dynamic Broker Configs
listKafkaClusterConfigs 1 param → 2004004014034295XX
POST
/kafka/v3/clusters/{cluster_id}/broker-configs:alter
Batch Alter Dynamic Broker Configs
updateKafkaClusterConfigs 1 param body → 2044004014034295XX
GET
/kafka/v3/clusters/{cluster_id}/broker-configs/{name}
Get Dynamic Broker Config
getKafkaClusterConfig 2 params → 2004004014034295XX
PUT
/kafka/v3/clusters/{cluster_id}/broker-configs/{name}
Update Dynamic Broker Config
updateKafkaClusterConfig 2 params body → 2044004014034295XX
DELETE
/kafka/v3/clusters/{cluster_id}/broker-configs/{name}
Reset Dynamic Broker Config
deleteKafkaClusterConfig 2 params → 2044004014034295XX
GET
/kafka/v3/clusters/{cluster_id}/topics/{topic_name}/configs
List Topic Configs
listKafkaTopicConfigs 2 params → 2004004014034044295XX
POST
/kafka/v3/clusters/{cluster_id}/topics/{topic_name}/configs:alter
Batch Alter Topic Configs
updateKafkaTopicConfigBatch 2 params body → 2044004014034044295XX
GET
/kafka/v3/clusters/{cluster_id}/topics/{topic_name}/configs/{name}
Get Topic Config
getKafkaTopicConfig 3 params → 2004004014034044295XX
PUT
/kafka/v3/clusters/{cluster_id}/topics/{topic_name}/configs/{name}
Update Topic Config
updateKafkaTopicConfig 3 params body → 2044004014034044295XX
DELETE
/kafka/v3/clusters/{cluster_id}/topics/{topic_name}/configs/{name}
Reset Topic Config
deleteKafkaTopicConfig 3 params → 2044004014034044295XX
GET
/kafka/v3/clusters/{cluster_id}/topics/-/configs
List All Topic Configs
listKafkaAllTopicConfigs 1 param → 2004004014034295XX
GET
/kafka/v3/clusters/{cluster_id}/topics/{topic_name}/default-configs
List New Topic Default Configs
listKafkaDefaultTopicConfigs 2 params → 2004004014044295XX
GET
/kafka/v3/clusters/{cluster_id}/groups/{group_id}/configs
List all configs of the group
listKafkaGroupConfigs 2 params → 2004004014044295XX
GET
/kafka/v3/clusters/{cluster_id}/groups/{group_id}/configs/{name}
Get group config
getKafkaGroupConfig 3 params → 2004004014044295XX
PUT
/kafka/v3/clusters/{cluster_id}/groups/{group_id}/configs/{name}
Update group config
updateKafkaGroupConfig 3 params body → 2044004014044295XX
DELETE
/kafka/v3/clusters/{cluster_id}/groups/{group_id}/configs/{name}
Delete group config
deleteKafkaGroupConfig 3 params → 2044004014044295XX
POST
/kafka/v3/clusters/{cluster_id}/groups/{group_id}/configs:alter
Batch Alter Group Configs
updateKafkaGroupConfigBatch 3 params body → 2044004014044295XX

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are Error (8 properties), ConfigSynonymData (3 properties), ResourceMetadata (2 properties), Resource (2 properties). Each schema is shown below with its type and property counts.

ConfigSource
string
AbstractConfigData
AlterConfigBatchRequestData
object
2 properties 1 required
ResourceCollection
object
2 properties 2 required
ResourceCollectionMetadata
object
2 properties 1 required
UpdateGroupConfigRequestData
object
1 property 1 required
GroupConfigData
ResourceMetadata
object
2 properties 1 required
TopicConfigData
UpdateConfigRequestData
object
1 property
ClusterConfigData
ConfigSynonymData
object
3 properties 2 required
ClusterConfigDataList
GroupConfigDataList
Error
object
Describes a particular error encountered while performing an operation.
8 properties
TopicConfigDataList
Resource
object
2 properties 2 required
ClusterConfigType
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

confluent-configs-v3-api-openapi.yml Raw ↑

Other APIs Confluent publishes across the network.

Confluent
Confluent Managed MCP Servers
Confluent ACLs API
Confluent API Keys API
Confluent Clusters API
Confluent Consumer Groups API
Confluent Environments API
Confluent Partitions API
Confluent Service Accounts API
Confluent Topics API
Confluent Access Points (networking/v1) API
Confluent ACL (v3) API
Where this information came from

This is an independent, third-party profile of Confluent Configs (v3) 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.