Streamkap · Rate Limits

Streamkap Rate Limits

The Streamkap management REST API is a control-plane API for provisioning and operating sources, destinations, pipelines, and transforms; it is not the data path. Streamkap does not publish fixed public per-endpoint request-rate numbers for the management API. The practical "limits" that govern Streamkap usage are the plan-level data-volume allocations (GB/month) and transform compute (vCPU) rather than API requests per second. Access tokens are short-lived JWTs that must be refreshed, which bounds long-running automation.

Streamkap Rate Limits is the machine-readable rate-limit profile for Streamkap on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, seconds, gigabytes, and vcpu.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Streaming, ETL, CDC, Kafka, and Flink.

4 Limits Throttle: 429
StreamingETLCDCKafkaFlinkRate LimitingQuotasThrottling

Limits

Management API Requests tenant
requests
see provider documentation
Control-plane request-rate limits are not published as fixed public values; reasonable-use limits may apply per tenant.
Access Token Lifetime credential
seconds
expiresIn on token response
Access tokens expire (expiresIn is returned on the token response) and must be refreshed via /authentication/refresh-access-token.
Data Volume account
gigabytes
per plan allocation
Free 500 MB/month; Starter caps at 30 GB/month; Scale includes 150 GB/month; Enterprise unlimited. Overage billed per GB.
Transform Compute account
vcpu
per plan allocation
Free tier includes 24 hours/month shared compute; paid plans bill Streaming Agents at $250 per vCPU/month.

Policies

Token Refresh
Clients should refresh the short-lived JWT before expiry rather than re-authenticating on every call.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 response from the management API.
Plan-Based Capacity
Effective throughput is governed by plan data-volume and transform-compute allocations; raise capacity by upgrading the plan or contacting sales.

Sources