Confluent · Rate Limits

Confluent Rate Limits

Confluent enforces two distinct kinds of limit and it matters which one an agent hits. Request-rate and concurrency throttling returns 429 with headers; service quotas are resource COUNT ceilings (how many API keys, clusters, topics you may have) which surface as 402/400. Confluent publishes the throttling header contract precisely and the per-endpoint numeric rates not at all.

Confluent Rate Limits is the machine-readable rate-limit profile for Confluent on the APIs.io network, in the API Commons Rate Limits shape.

It captures 6 rate-limit definitions, measuring requests, concurrent-operations, connections-per-second, and api-keys.

Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.

The profile also includes response codes documented for throttled, quotaExceeded, quotaExceededKnownIssue, and serviceUnavailable.

Tagged areas include Rate Limiting, Quotas, Throttling, and Service Quotas.

6 Limits Exhausted: HTTP 429 Quota: 402 limitremainingresetretryAfter
Transcribed from the provider's documentation on 2026-08-27 — Rate Limiting section of info.description in docs.conflue....
View Source
Rate LimitingQuotasThrottlingService Quotas

Limits

Request rate (per user) per-user
requests
Confluent enforces request-rate limits per user but does not publish the numeric rate for any endpoint. The limit is discoverable only at runtime from X-RateLimit-Limit.
Request rate (per organization) per-organization
requests
Concurrency (per user and per organization) per-user, per-organization
concurrent-operations
Unauthenticated request rate per-source-ip
requests
Unauthenticated requests are associated with the originating IP address, not with a user.
Kafka REST Produce v3 connections (Dedicated) per-cluster
connections-per-second · per second
300/second
The one published numeric rate. Each additional CKU on a Dedicated cluster increases the Kafka REST Produce v3 connection limit by 300 requests per second — the documented path to a higher rate, since Confluent states rate limits are otherwise fixed and cannot be increased.
Cloud API keys per organization per-organization
api-keys
3000

Work with this as data

Every rate limit 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 rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit 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 rate limit 
curl "https://apis.io/api/v1/rate-limits/confluent-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?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.