Getstream Rate Limits
Stream applies rate limits per API endpoint and per platform on a rolling 1-minute window. Platforms (Server-side, iOS, Android, Web) have independent counters and do not share quota, so a server-side script hitting a limit does not affect mobile or web clients. Each response returns the current quota in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers, and a 429 status is returned when a limit is exceeded. Per-user endpoints are additionally capped at roughly 60 requests per minute per endpoint and platform; app-level endpoint limits range from about 60 to 10,000 requests per minute. Applications can query their live quotas via GET /rate_limits. WebSocket connections are separately capped at 50 concurrent connections per user in production (3 in development).
Getstream Rate Limits is the machine-readable rate-limit profile for Stream on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring requests and connections.
Limit state is signalled in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Chat, Rate Limiting, Quotas, and Throttling.
X-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-Reset
generated, dated 2026-07-03.
Limits
Policies
Sources
- https://getstream.io/chat/docs/node/rate_limits/
- https://getstream.github.io/protocol/?urls.primaryName=Chat
- https://getstream.io/chat/docs/node/instantiating_the_client/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.