How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Confluent

Confluent Connectors (connect/v1) API

[![General Availability](https://img.shields.io/badge/Lifecycle%20Stage-General%20Availability-%2345c6e8)](#section/Versioning/API-Lifecycle-Policy)API for Managed Connectors or Custom Connectors in Confluent Cloud.The API allows you to list, create, get, update and delete a Managed Connector or Custom Connector in Confluent Cloud.Connect metrics are available through the [Metrics v2 API](https://api.telemetry.confluent.cloud/docs#tag/Version-2).Related guide: [Confluent Cloud API and Managed Connectors](https://docs.confluent.io/cloud/current/connectors/connect-api-section.html).

Documentation Provider Profile APIs.io OpenAPI GitHub

Confluent Connectors (connect/v1) API is one of 127 APIs that Confluent publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Connectors (connect/v1). The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 7 operations across 4 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0.

Requests are made against a single base URL, https://api.confluent.cloud.

7 operations 4 paths 6 schemas 1 DELETE4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.confluent.cloud
Authentication
HTTP Basic, OAuth 2.0, HTTP Basic, HTTP Basic, OAuth 2.0, OAuth 2.0
Resource Areas
1

Authentication & Security 6

Confluent Connectors (connect/v1) API declares 6 security schemes for authenticating requests. It accepts HTTP basic authentication (cloud-api-key). It supports OAuth 2.0 (confluent-sts-access-token) using the clientCredentials flow. It accepts HTTP basic authentication (global-api-key). It accepts HTTP basic authentication (resource-api-key). It supports OAuth 2.0 (external-access-token) using the clientCredentials flow. It supports OAuth 2.0 (oauth) using the clientCredentials flow, exposing 4 scopes.

  • cloud-api-key — Authenticate with Cloud API Keys using HTTP Basic Auth. Treat the Cloud API Key ID as the username and Cloud API Key Secret as the password.
  • confluent-sts-access-token — Authenticate with Confluent API using this credentials (JSON Web Tokens) following OAuth 2.0.
  • global-api-key — Authenticate with Global API Keys using HTTP Basic Auth. Treat the Global API Key ID as the username and Global API Key Secret as the password.
  • resource-api-key — Authenticate with resource-specific API Keys using HTTP Basic Auth. Treat the resource-specific API Key ID as the username and resource-specific API Key Secret…
  • external-access-token — Authenticate with Confluent API using this credentials (JSON Web Tokens) following OAuth 2.0.
  • oauth — Authenticate with OAuth 2.0. Currently this is only supported for partner APIs.

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Connectors (connect/v1) 7

[![General Availability](https://img.shields.io/badge/Lifecycle%20Stage-General%20Availability-%2345c6e8)](section/Versioning/API-Lifecycle-Policy) API for Managed Connectors or C…

GET
/connect/v1/environments/{environment_id}/clusters/{kafka_cluster_id}/connectors
List of Connectors
listConnectv1Connectors 2 params → 200401404429500
POST
/connect/v1/environments/{environment_id}/clusters/{kafka_cluster_id}/connectors
Create a Connector
createConnectv1Connector 2 params body → 201400401429500
GET
/connect/v1/environments/{environment_id}/clusters/{kafka_cluster_id}/connectors?expand=info,status,id
List of Connectors with Expansions
listConnectv1ConnectorsWithExpansions 3 params → 200401404429500
GET
/connect/v1/environments/{environment_id}/clusters/{kafka_cluster_id}/connectors/{connector_name}/config
Read a Connector Configuration
getConnectv1ConnectorConfig 3 params → 200401404429500
PUT
/connect/v1/environments/{environment_id}/clusters/{kafka_cluster_id}/connectors/{connector_name}/config
Create or Update a Connector Configuration
createOrUpdateConnectv1ConnectorConfig 3 params body → 200400401404429500
GET
/connect/v1/environments/{environment_id}/clusters/{kafka_cluster_id}/connectors/{connector_name}
Read a Connector
readConnectv1Connector 3 params → 200401404429500
DELETE
/connect/v1/environments/{environment_id}/clusters/{kafka_cluster_id}/connectors/{connector_name}
Delete a Connector
deleteConnectv1Connector 3 params → 200401404429500

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are connect.v1.ConnectorWithOffsets (5 properties), connect.v1.Connector (4 properties), connect.v1.ConnectorExpansion (3 properties), connect.v1.ConnectorError (1 property). Each schema is shown below with its type and property counts.

connect.v1.ConnectorExpansion
object
Name of connector
3 properties
connect.v1.ConnectorWithOffsets
object
5 properties 2 required
connect.v1.Offsets
array
Array of offsets which are categorised into partitions.
connect.v1.ConnectorError
object
1 property
connect.v1.Connector
object
4 properties 2 required
connect.v1.ConnectorExpansionMap
object

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

confluent-connectors-connect-v1-api-openapi.yml Raw ↑

Other APIs Confluent publishes across the network.

Confluent
AE Profile APIs.io
Confluent Managed MCP Servers
AE Profile APIs.io
Confluent ACLs API
AE Profile APIs.io
Confluent API Keys API
AE Profile APIs.io
Confluent Clusters API
AE Profile APIs.io
Confluent Consumer Groups API
AE Profile APIs.io
Confluent Environments API
AE Profile APIs.io
Confluent Partitions API
AE Profile APIs.io
Confluent Service Accounts API
AE Profile APIs.io
Confluent Topics API
AE Profile APIs.io
Confluent Access Points (networking/v1) API
AE Profile APIs.io
Confluent ACL (v3) API
AE Profile APIs.io
#Connectors (connect/v1)
← Back to C APIs
API Details
ID
confluent:confluent-connectors-connect-v1-api
Base URL
https://api.confluent.cloud
Docs
https://www.confluent.io/
Provider
Confluent
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=confluent-connectors-connect-v1-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/confluent-connectors-connect-v1-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Confluent Connectors (connect/v1) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.