specification: API Commons Rate Limits specificationVersion: '0.1' schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits provider: Restream providerId: restream created: '2026-05-04' # Provenance stamped 2026-08-11: this artifact was written by the API Evangelist # bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35. method: generated modified: '2026-05-05' reconciled: false tags: - Rate Limiting - Live Streaming - Multistreaming description: Restream's developer documentation describes the REST API (channels, events, users), the Streaming Updates WebSocket, and the Chat WebSocket, but does not publish per-second / per-minute rate-limit numbers. The functional product caps that drive consumption (simultaneous channels, embedded-player viewers, team seats) live in the subscription plan rather than as documented HTTP rate limits. sources: - https://developers.restream.io/ - https://restream.io/pricing notes: No public rate-limit numbers are published on the Restream developer portal. Plan-tied caps (simultaneous channels, viewers, seats) belong in plans/. Numbers below reflect what is actually documented. limits: - name: REST API throttling scope: account metric: varies limit: 'see https://developers.restream.io/ — not numerically published' - name: Simultaneous destination channels (plan-bound) scope: account metric: concurrent_streams limit: 'depends on plan: Free 2, Standard 3, Professional 5, Business 8, Enterprise custom' policies: - name: Plan-Bound Concurrency description: The most consequential consumption ceiling is the simultaneous-channel cap defined by the active subscription tier rather than HTTP-level throttling. - name: OAuth2-Scoped Access description: Access to Restream APIs is OAuth2-scoped per user, so limits and behavior should be treated as per-user-account rather than global. maintainers: - FN: Kin Lane email: kin@apievangelist.com