Confluent · OpenAPI Overlay 1.0.0

API Evangelist conversational phrasing for Confluent Cloud Integrations (pim/v1) API

5 actions 5 updates phrasing extends openapi/confluent-integrations-pim-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 5

$.info
$.paths['/pim/v1/integrations'].get
$.paths['/pim/v1/integrations'].post
$.paths['/pim/v1/integrations/{id}'].get
$.paths['/pim/v1/integrations/{id}'].delete

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 Integrations (pim/v1) API
  version: 1.0.0
extends: openapi/confluent-integrations-pim-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: 4
- target: $.paths['/pim/v1/integrations'].get
  update:
    x-apievangelist-phrasing:
      intent: List cloud provider integrations
      effect: read
      questions:
      - Which cloud provider integrations exist in my environment?
      - Can I list provider integrations for just one cloud?
      instructions:
      - text: List provider integrations in environment {environment}.
        slots:
          environment: query.environment
      - text: List {provider} integrations in environment {environment}.
        slots:
          environment: query.environment
          provider: query.provider
      method: generated
      generated: '2026-09-26'
- target: $.paths['/pim/v1/integrations'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a cloud provider integration
      effect: write
      questions:
      - How do I give Confluent Cloud access to my cloud account through a provider integration?
      - What configuration does a new provider integration need?
      instructions:
      - text: Create a {provider} integration named {display_name} in environment {environment}.
        slots:
          provider: requestBody.provider
          display_name: requestBody.display_name
          environment: requestBody.environment
      - text: Set up provider integration {display_name} with config {config}.
        slots:
          display_name: requestBody.display_name
          config: requestBody.config
      method: generated
      generated: '2026-09-26'
- target: $.paths['/pim/v1/integrations/{id}'].get
  update:
    x-apievangelist-phrasing:
      intent: Read a cloud provider integration
      effect: read
      questions:
      - Which resources are using a particular provider integration?
      - Can I fetch one provider integration by ID?
      instructions:
      - text: Show provider integration {id} in environment {environment}.
        slots:
          id: path.id
          environment: query.environment
      - text: Get the config and usages of integration {id} ({environment}).
        slots:
          id: path.id
          environment: query.environment
      method: generated
      generated: '2026-09-26'
- target: $.paths['/pim/v1/integrations/{id}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a cloud provider integration
      effect: destructive
      questions:
      - Why does deleting a provider integration fail while workloads still use it?
      - How do I remove a cloud provider integration?
      instructions:
      - text: Delete provider integration {id} in environment {environment}.
        slots:
          id: path.id
          environment: query.environment
      - text: Remove cloud integration {id} from {environment}.
        slots:
          id: path.id
          environment: query.environment
      method: generated
      generated: '2026-09-26'

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this
  • find_overlaysBrowse and filter every overlay in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/confluent-integrations-pim-v1-api-phrasing-overlay"
All openapi overlays
curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.