Confluent · OpenAPI Overlay 1.0.0
API Evangelist conversational phrasing for Confluent Cloud Integrations (pim/v2) API
7 actions
7 updates
phrasing
extends
openapi/confluent-integrations-pim-v2-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.
What the actions change
x-apievangelist-phrasing
Targets 7
$.info
$.paths['/pim/v2/integrations'].get
$.paths['/pim/v2/integrations'].post
$.paths['/pim/v2/integrations/{id}'].get
$.paths['/pim/v2/integrations/{id}'].delete
$.paths['/pim/v2/integrations/{id}'].patch
$.paths['/pim/v2/integrations:validate'].post
OpenAPI Overlay
# 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/v2) API
version: 1.0.0
extends: openapi/confluent-integrations-pim-v2-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: 6
- target: $.paths['/pim/v2/integrations'].get
update:
x-apievangelist-phrasing:
intent: List cloud provider integrations
effect: read
questions:
- Which cloud provider integrations exist in my Confluent environment?
- Can I filter provider integrations by status or cloud provider?
instructions:
- text: List provider integrations in environment {environment}.
slots:
environment: query.environment
- text: List {provider} integrations in {environment} with status {status}.
slots:
provider: query.provider
environment: query.environment
status: query.status
method: generated
generated: '2026-09-26'
- target: $.paths['/pim/v2/integrations'].post
update:
x-apievangelist-phrasing:
intent: Create a cloud provider integration
effect: write
questions:
- How do I set up a new provider integration so Confluent can access my cloud account?
- Can I create an integration in draft status and configure it later?
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: Create a 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/v2/integrations/{id}'].get
update:
x-apievangelist-phrasing:
intent: Get one cloud provider integration
effect: read
questions:
- What is the current status and config of a specific provider integration?
- How do I read a provider integration by its ID?
instructions:
- text: Get provider integration {id} in environment {environment}.
slots:
id: path.id
environment: query.environment
- text: Show details of integration {id} from environment {environment}.
slots:
id: path.id
environment: query.environment
method: generated
generated: '2026-09-26'
- target: $.paths['/pim/v2/integrations/{id}'].delete
update:
x-apievangelist-phrasing:
intent: Delete a cloud provider integration
effect: destructive
questions:
- Can I remove a provider integration I no longer use?
- What happens to connectors when I delete their provider integration?
instructions:
- text: Delete provider integration {id} in environment {environment}.
slots:
id: path.id
environment: query.environment
- text: Remove integration {id} from {environment}.
slots:
id: path.id
environment: query.environment
method: generated
generated: '2026-09-26'
- target: $.paths['/pim/v2/integrations/{id}'].patch
update:
x-apievangelist-phrasing:
intent: Update a cloud provider integration
effect: write
questions:
- Can I rename or change the configuration of an existing provider integration?
- How do I move a draft provider integration to a new status?
instructions:
- text: Rename provider integration {id} to {display_name}.
slots:
id: path.id
display_name: requestBody.display_name
- text: Update the config of integration {id} to {config}.
slots:
id: path.id
config: requestBody.config
method: generated
generated: '2026-09-26'
- target: $.paths['/pim/v2/integrations:validate'].post
update:
x-apievangelist-phrasing:
intent: Validate a cloud provider integration
effect: read
questions:
- Is my provider integration configured correctly before I rely on it?
- Can I test a draft integration's cloud configuration without saving it?
instructions:
- text: Validate provider integration {id} in environment {environment}.
slots:
id: requestBody.id
environment: requestBody.environment
- text: Check whether config {config} works for draft integration {id}.
slots:
config: requestBody.config
id: requestBody.id
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.
Call it yourself
curl for this page
This overlay
curl "https://apis.io/api/v1/overlays/confluent-integrations-pim-v2-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.