Confluent | the Data Streaming Platform · OAuth Scopes

Confluent | the Data Streaming Platform OAuth Scopes

OAuth 2.0 searched

Confluent

the Data Streaming Platform publishes 5 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Confluent

the Data Streaming Platform API on a user’s behalf.

Tokens are issued from https://api.confluent.cloud/sts/v1/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Apache FlinkApache KafkaConfluent CloudConnectorsData StreamingEvent StreamingKafka ConnectksqlDBReal-Time DataRESTSchema RegistryStream Processing

Scopes: 5 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://api.confluent.cloud/sts/v1/oauth2/token /oauth2/token

Flows
clientCredentials

Scopes (5)

Scope	Description	Flows
marketplace::describe
partner:alter	enables partners to alter entitlements	clientCredentials
partner:create	enables partners to create entitlements and signup on behalf of customers	clientCredentials
partner:delete	enables partners to delete entitlements and organizations	clientCredentials
partner:describe	enables partners to read and list entitlements and organizations	clientCredentials

📄 Provider scope reference: https://docs.confluent.io/cloud/current/security/access-control/rbac/predefined-rbac-roles.html

Source

OAuth Scopes

generated: '2026-09-05'
method: searched
source: openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
schemes:
- name: confluent-sts-access-token
  source: openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.confluent.cloud/sts/v1/oauth2/token
  description: Authenticate with Confluent API using this credentials (JSON Web Tokens) following OAuth
    2.0.
- name: external-access-token
  source: openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.confluent.cloud/sts/v1/oauth2/token
  description: Authenticate with Confluent API using this credentials (JSON Web Tokens) following OAuth
    2.0.
- name: oauth
  source: openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /oauth2/token
  description: Authenticate with OAuth 2.0. Currently this is only supported for partner APIs.
scopes:
- scope: marketplace::describe
  sources:
  - openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
- scope: partner:alter
  description: enables partners to alter entitlements
  flows:
  - clientCredentials
  sources:
  - openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
- scope: partner:create
  description: enables partners to create entitlements and signup on behalf of customers
  flows:
  - clientCredentials
  sources:
  - openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
- scope: partner:delete
  description: enables partners to delete entitlements and organizations
  flows:
  - clientCredentials
  sources:
  - openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
- scope: partner:describe
  description: enables partners to read and list entitlements and organizations
  flows:
  - clientCredentials
  sources:
  - openapi/confluent-the-data-streaming-platform-cloud-apis-openapi.yml
docs: https://docs.confluent.io/cloud/current/security/access-control/rbac/predefined-rbac-roles.html
docs_note: 'Confluent publishes no OAuth SCOPES reference page, because scopes are not how this API authorizes.
  Only the partner OAuth scheme declares any (partner:describe / create / alter / delete, plus marketplace::describe),
  and those cover a partner-entitlement surface most callers never touch. Every other request is authorized
  by RBAC ROLE BINDINGS attached to the calling user, service account or identity pool — the predefined
  role list at the docs URL above is the real permission reference for this provider, and it is what an
  integrator should read where they would normally read a scope table. Searched 2026-09-05 and confirmed:
  there is no scope catalogue to add.'
authorization_model: rbac-role-bindings

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set 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 scope set

curl "https://apis.io/api/v1/scopes/confluent-the-data-streaming-platform-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.