Confluent

Confluent Integrations (pim/v2) API

[![Early Access](https://img.shields.io/badge/Lifecycle%20Stage-Early%20Access-%2345c6e8)](#section/Versioning/API-Lifecycle-Policy) [![Request Access To Provider Integration](https://img.shields.io/badge/-Request%20Access%20To%20Provider%20Integration-%23bc8540)](mailto:ccloud-api-access+pim-v2-early-access@confluent.io?subject=Request%20to%20join%20pim/v2%20API%20Early%20Access&body=I%E2%80%99d%20like%20to%20join%20the%20Confluent%20Cloud%20API%20Early%20Access%20for%20pim/v2%20to%20provide%20early%20feedback%21%20My%20Cloud%20Organization%20ID%20is%20%3Cretrieve%20from%20https%3A//confluent.cloud/settings/billing/payment%3E.) `Provider Integration` objects represent access to public cloud service provider (CSP) resources that may be accessed by Confluent resources (for example, connectors). The API allows you to create, retrieve, update, delete, and validate individual integrations, and also obtain a list of all your provider integrations. Note: The pim/v2 API currently supports only Azure and GCP provider integrations. Related guide: [Provider Integration in Confluent Cloud](https://docs.confluent.io/home/overview.html). ## The Integrations Model

GitHub OpenAPI

Operations 6

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /pim/v2/integrations List cloud provider integrations · List of Integrations #
Ask an LLM
“Which cloud provider integrations exist in my Confluent environment?”
“Can I filter provider integrations by status or cloud provider?”
Tell an agent
List provider integrations in environment {environment}.
List {provider} integrations in {environment} with status {status}.
POST /pim/v2/integrations Create a cloud provider integration · Create an Integration #
Ask an LLM
“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?”
Tell an agent
Create a {provider} integration named {display_name} in environment {environment}.
Create a provider integration {display_name} with config {config}.
GET /pim/v2/integrations/{id} Get one cloud provider integration · Read an Integration #
Ask an LLM
“What is the current status and config of a specific provider integration?”
“How do I read a provider integration by its ID?”
Tell an agent
Get provider integration {id} in environment {environment}.
Show details of integration {id} from environment {environment}.
PATCH /pim/v2/integrations/{id} Update a cloud provider integration · Update an Integration #
Ask an LLM
“Can I rename or change the configuration of an existing provider integration?”
“How do I move a draft provider integration to a new status?”
Tell an agent
Rename provider integration {id} to {display_name}.
Update the config of integration {id} to {config}.
DELETE /pim/v2/integrations/{id} Delete a cloud provider integration · Delete an Integration #
Ask an LLM
“Can I remove a provider integration I no longer use?”
“What happens to connectors when I delete their provider integration?”
Tell an agent destructive · confirm first
Delete provider integration {id} in environment {environment}.
Remove integration {id} from {environment}.
POST /pim/v2/integrations:validate Validate a cloud provider integration · Validate an Integration #
Ask an LLM
“Is my provider integration configured correctly before I rely on it?”
“Can I test a draft integration's cloud configuration without saving it?”
Tell an agent
Validate provider integration {id} in environment {environment}.
Check whether config {config} works for draft integration {id}.

Documentation

📖
APIReference
https://docs.confluent.io/cloud/current/api.html
📖
APIReference
https://api.telemetry.confluent.cloud/docs

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/confluent/refs/heads/main/openapi/confluent-integrations-pim-v2-api-openapi.yml

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/confluent:confluent-integrations-pim-v2-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

GitHub Google LinkedIn

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

OpenAPI Specification

confluent-integrations-pim-v2-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Confluent Integrations (pim/v2) API
  version: ''
  x-api-id: 46234552-5833-42eb-ba0f-883ad3f70d2b
  x-audience: external-public
  x-logo:
    url: https://assets.confluent.io/m/1661ef5e4ff82d3d/
  description: 'Operations tagged Integrations (pim/v2) across 2 of this provider''s published API definitions: confluent-cloud-openapi.yaml, confluent-cloud-full.yaml. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.confluent.cloud
  description: Confluent Cloud API
tags:


# --- truncated at 32 KB (79 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/confluent/refs/heads/main/openapi/confluent-integrations-pim-v2-api-openapi.yml