Suggestion: Higher / Adaptive API Limits to Prevent Error 429

Hi Base44 team,

I wanted to share a suggestion regarding Error 429 (API rate limiting) that I’m currently running into.

My app relies on live server data (game server dashboard), and even with reasonable polling intervals, the current API limits can be hit—especially when multiple endpoints are involved or when users manually refresh.

This results in temporary downtime for users, even though the usage is legitimate and not abusive.

Suggestion ideas that could help:

Offer a higher API limit tier (paid or add-on) for data-heavy dashboards

Introduce adaptive or burst-friendly limits, allowing short spikes without triggering 429

Allow admin-controlled polling intervals or limit tuning from the Base44 side

Optional grace window or soft throttling instead of hard 429 blocks

Better visibility into which calls trigger 429 (endpoint-level insight)

This would greatly help apps that rely on real-time or near real-time data, while still protecting the platform from abuse.

I really like Base44 and what it enables — this change would make it even more suitable for production dashboards and monitoring-style apps.

Thanks for considering, and happy to provide more technical details if helpful.

Best regards,