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 Schema Registry Subjects API

The Subjects API from Confluent Schema Registry — 6 operation(s) for subjects.

Confluent Schema Registry Subjects API is one of 5 APIs that Confluent Schema Registry publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Subjects. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 1 JSON Schema.

This API exposes 9 operations across 6 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 7.6.0.

Requests are made against a single base URL, http://localhost:8081.

9 operations 6 paths 3 schemas 2 DELETE5 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
7.6.0
Base URL
http://localhost:8081
Contact
Resource Areas
1

Paths & Operations 9

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

Subjects 9
GET
/subjects
List registered subjects
listSubjects 2 params → 200500
GET
/subjects/{subject}/versions
List versions under subject
listVersions 2 params → 200404
POST
/subjects/{subject}/versions
Register schema under subject
registerSchema 2 params body → 200409422
GET
/subjects/{subject}/versions/{version}
Get schema by version
getSchemaByVersion 3 params → 200404
DELETE
/subjects/{subject}/versions/{version}
Delete schema version
deleteSchemaVersion 3 params → 200404
GET
/subjects/{subject}/versions/{version}/schema
Get raw schema by version
getSchemaOnly 2 params → 200
GET
/subjects/{subject}/versions/{version}/referencedby
Get schemas that reference this schema
getReferencedBy 2 params → 200
POST
/subjects/{subject}
Check if schema is registered under subject
lookUpSchemaUnderSubject 3 params body → 200404
DELETE
/subjects/{subject}
Delete subject and all versions
deleteSubject 2 params → 200

Schemas 3

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

RegisterSchemaRequest
object
3 properties 1 required
Schema
object
6 properties
ErrorMessage
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

confluent-schema-registry-subjects-api-openapi.yml Raw ↑

Other APIs Confluent Schema Registry publishes across the network.

Confluent Schema Registry Compatibility API
Confluent Schema Registry Mode API
Confluent Schema Registry Schemas API
Confluent Schema Registry Server API
Where this information came from

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