Confluent · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Confluent Cloud Compatibility (v1) API

3 actions 3 updates phrasing extends openapi/confluent-compatibility-v1-api-openapi.yml
Generated by API Evangelist Written by API Evangelist tooling for Confluent's API. It is a proposal applied on top of the contract, not a document Confluent publishes.
View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-phrasing

Targets 3

$.info
$.paths['/compatibility/subjects/{subject}/versions/{version}'].post
$.paths['/compatibility/subjects/{subject}/versions'].post

OpenAPI Overlay

Raw ↑ 
# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Confluent Cloud Compatibility (v1) API
  version: 1.0.0
extends: openapi/confluent-compatibility-v1-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 2
- target: $.paths['/compatibility/subjects/{subject}/versions/{version}'].post
  update:
    x-apievangelist-phrasing:
      intent: Test a schema against one subject version
      effect: read
      questions:
      - Is my new schema compatible with one specific version of a subject?
      - Can I get verbose reasons when a schema fails a compatibility check against a version?
      instructions:
      - text: Test schema {schema} for compatibility with subject {subject} version {version}.
        slots:
          schema: requestBody.schema
          subject: path.subject
          version: path.version
      - text: Check {schema} against version {version} of {subject} with verbose={verbose}.
        slots:
          schema: requestBody.schema
          version: path.version
          subject: path.subject
          verbose: query.verbose
      method: generated
      generated: '2026-09-26'
- target: $.paths['/compatibility/subjects/{subject}/versions'].post
  update:
    x-apievangelist-phrasing:
      intent: Test a schema against all versions of a subject
      effect: read
      questions:
      - Would this schema pass the same compatibility check as registering it under the subject?
      - Is my schema compatible with every version already under a subject?
      instructions:
      - text: Test schema {schema} against all versions of subject {subject}.
        slots:
          schema: requestBody.schema
          subject: path.subject
      - text: Check whether {schema} could be registered under {subject} without breaking compatibility.
        slots:
          schema: requestBody.schema
          subject: path.subject
      method: generated
      generated: '2026-09-26'