Bubble Rate Limits
Bubble enforces rate limits on the Data API and Workflow API at the per-app level, with the request-per-minute ceiling determined by the app's subscription plan. In addition to request rate, Bubble meters server-side activity in Workload Units (WU): every API call, database query, scheduled workflow, and plugin invocation consumes a number of WU drawn from the monthly plan allotment. Hard limits also apply to request size, response size, response list length, and workflow timeout. Rate-limited requests return HTTP 429; legacy plans return 429 (and occasionally 503 on capacity-locked legacy infrastructure).
Bubble Rate Limits is the machine-readable rate-limit profile for Bubble on the APIs.io network, in the API Commons Rate Limits shape.
It captures 12 rate-limit definitions, measuring requests_per_minute, bytes, items, seconds, and levels.
Limit state is signalled in the retryAfter response header, 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 7 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and throttledLegacy.
Tagged areas include Rate Limiting, No-Code, Application Platform, and Workload Units.
retryAfter
generated, dated 2026-05-06.
Limits
Policies
Sources
- https://manual.bubble.io/help-guides/maintaining-an-application/performance-and-scaling/hard-limits.md
- https://manual.bubble.io/help-guides/security/api-security.md
- https://manual.bubble.io/help-guides/workload/understanding-workload.md
- https://manual.bubble.io/help-guides/workload/understanding-workload/activity-types.md
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.