Confluent Contexts (v1) API
[](#section/Versioning/API-Lifecycle-Policy)The API allows you to retrieve information about schema contexts.Related guide: [Manage Schemas in Confluent Cloud](https://docs.confluent.io/cloud/current/sr/schemas-manage.html#manage-schemas-in-ccloud).
Confluent Contexts (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 Contexts (v1). The published artifact set on APIs.io includes an OpenAPI specification and an API reference.
This API exposes 1 operation across 1 path, and defines 1 schema. It is described by OpenAPI 3.2.0.
Requests are made against a single base URL, https://api.confluent.cloud.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 6
Confluent Contexts (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 1
Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.
[](section/Versioning/API-Lifecycle-Policy) The API allows you to retrieve in…
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. The most detailed is ErrorMessage (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Confluent 12
Other APIs Confluent publishes across the network.
This is an independent, third-party profile of Confluent Contexts (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.