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 Topics API

The Topics API from Confluent — 2 operation(s) for topics.

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

Tagged areas include Topics. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 2 base URLs: https://api.confluent.cloud, https://{kafka_cluster_host}.

4 operations 2 paths 3 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Servers
https://api.confluent.cloud
https://{kafka_cluster_host}
Authentication
HTTP Basic, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Confluent Topics API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic authentication using a Confluent Cloud API key (ID:secret)
  • bearerAuth — OAuth 2.0 bearer token (Confluent STS, external OAuth, or partner token)

Paths & Operations 4

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

Topics 4
GET
/kafka/v3/clusters/{cluster_id}/topics
List topics in a cluster
listTopics 1 param → 200
POST
/kafka/v3/clusters/{cluster_id}/topics
Create a topic
createTopic 1 param body → 201
GET
/kafka/v3/clusters/{cluster_id}/topics/{topic_name}
Get topic metadata
getTopic 2 params → 200
DELETE
/kafka/v3/clusters/{cluster_id}/topics/{topic_name}
Delete a topic
deleteTopic 2 params → 204

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are TopicCreateRequest (4 properties), Topic (4 properties), TopicList (1 property). Each schema is shown below with its type and property counts.

Topic
object
4 properties
TopicCreateRequest
object
4 properties 1 required
TopicList
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

confluent-topics-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 Access Points (networking/v1) API
Confluent ACL (v3) API
Confluent Agents (sql/v1) API
Where this information came from

This is an independent, third-party profile of Confluent Topics 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.