429 response. That base is the allowance for a workspace on the Free plan, and a paid workspace gets a multiple of it.
Limits are counted per workspace, not per individual caller. A personal access token’s rate-limit identity is the workspace it belongs to, not its owner, so two people using different tokens for the same workspace share one allowance. Some endpoints additionally scope the limit to one app; others share it across every app in the workspace.
Limits by plan
An endpoint documented at 20 requests per minute therefore allows 60 for a workspace on Pro and 200 for an enterprise workspace. Some enterprise agreements set a custom multiplier that replaces the value above.
Shared allowances
A few endpoints draw on one allowance together, so requests to either one count against the same budget.
1 This allowance is shared across every app in the workspace, not scoped to the app you’re calling for.
2 This allowance is scoped to one app, in addition to the workspace, so it isn’t shared with the workspace’s other apps. It’s also drawn down by version-history activity in the Base44 online app editor for the same app, which isn’t part of this API.
Exceeding rate limits
If you exceed the limit, you’ll get a429 Too Many Requests response. Wait before retrying.
Limits set by another service
Some endpoints answer429 because a service Base44 depends on is rate limiting, not because you passed a Base44 limit. Link custom domain passes through a limit from Base44’s hosting provider, and the Google Ads endpoints pass through limits from Google Ads. The plan multipliers above don’t apply to those.