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 Subjects (v1) API

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

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

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

This API exposes 10 operations across 7 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0.

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

10 operations 7 paths 10 schemas 2 DELETE6 GET2 POST

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 Subjects (v1) 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 10

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

Subjects (v1) 10

[![Generally Available](https://img.shields.io/badge/Lifecycle%20Stage-Generally%20Available-%2345c6e8)](section/Versioning/API-Lifecycle-Policy) The API allows you to create, ret…

GET
/subjects/{subject}/versions/{version}
Get schema by version
getSchemaByVersion 4 params → 200404422500400401403429
DELETE
/subjects/{subject}/versions/{version}
Delete schema version
deleteSchemaVersion 3 params → 200404422500400401403429
GET
/subjects/{subject}/versions/{version}/referencedby
List schemas referencing a schema
getReferencedBy 4 params → 200404422500400401403429
GET
/subjects/{subject}/versions/{version}/schema
Get schema string by version
getSchemaOnly_1 3 params → 200404422500400401403429
GET
/subjects/{subject}/versions
List versions under subject
listVersions 5 params → 200404500400401403429
POST
/subjects/{subject}/versions
Register schema under a subject
register 3 params body → 200409422500400401403429
POST
/subjects/{subject}
Lookup schema under subject
lookUpSchemaUnderSubject 4 params body → 200404500400401403429
DELETE
/subjects/{subject}
Delete subject
deleteSubject 2 params → 200404500400401403429
GET
/subjects
List subjects
list 5 params → 200500400401403429
GET
/subjects/{subject}/metadata
Retrieve the latest version with the given metadata.
getLatestWithMetadata 5 params → 200404500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Rule (11 properties), RegisterSchemaRequest (10 properties), Schema (9 properties), Metadata (3 properties). Each schema is shown below with its type and property counts.

RegisterSchemaRequest
object
Schema register request
10 properties
RuleSet
objectnull
Schema rule set
2 properties
SchemaEntity
object
2 properties
RegisterSchemaResponse
object
Schema register response
1 property
SchemaTags
object
2 properties
SchemaReference
object
Schema reference
3 properties
Schema
object
Schema
9 properties
Metadata
objectnull
User-defined metadata
3 properties
Rule
object
Rule
11 properties
ErrorMessage
object
Error message of this operation
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

confluent-subjects-v1-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 Subjects (v1) 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.