Confluent · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Confluent Cloud Statements (query/v1alpha1) API

3 actions 3 updates phrasing extends openapi/confluent-statements-query-v1alpha1-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['/query/v1alpha1'].post
$.paths['/query/v1alpha1/jobs/{statement_id}/status'].get

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 Statements (query/v1alpha1) API
  version: 1.0.0
extends: openapi/confluent-statements-query-v1alpha1-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['/query/v1alpha1'].post
  update:
    x-apievangelist-phrasing:
      intent: Run a SQL query against a Kafka cluster
      effect: read
      questions:
      - How do I run a SQL query over my Kafka topics and get rows back?
      - What happens if my query takes longer than 30 seconds or returns more than 25 MiB?
      - Can I get query results as an Arrow stream instead of JSON?
      instructions:
      - text: Run query {query} on cluster {database_name} in environment {catalog_name}.
        slots:
          query: requestBody.query
          database_name: requestBody.database_name
          catalog_name: requestBody.catalog_name
      - text: Execute SQL {query} against {catalog_name}/{database_name} with options {options}.
        slots:
          query: requestBody.query
          catalog_name: requestBody.catalog_name
          database_name: requestBody.database_name
          options: requestBody.options
      method: generated
      generated: '2026-09-26'
- target: $.paths['/query/v1alpha1/jobs/{statement_id}/status'].get
  update:
    x-apievangelist-phrasing:
      intent: Check status of a background query
      effect: read
      questions:
      - Is my long-running background SQL query still running or finished?
      - What lifecycle state is an async query job in?
      instructions:
      - text: Get the status of query job {statement_id}.
        slots:
          statement_id: path.statement_id
      - text: Check whether background statement {statement_id} has completed.
        slots:
          statement_id: path.statement_id
      method: generated
      generated: '2026-09-26'