To ensure fair usage and system stability, Bleemeo enforces rate limits on API requests. These limits apply to all API consumers: agents, the web panel, and third-party applications.
Rate limits vary by plan and request type:
Plan Requests per Minute Professional Higher limits Starter Standard limits Free Basic limits
Exact limits depend on the endpoint and your usage patterns. The API is designed to accommodate normal monitoring operations without hitting limits.
Rate limits are evaluated across all sources of API traffic for your account:
Bleemeo agents connecting and sending metrics
Web panel requests when you browse dashboards
Custom applications using the REST API
SDK requests from Python or Go clients
Heavy usage in one area can affect your available capacity in others.
When you exceed rate limits, the API returns a 429 Too Many Requests response.
Best practices for handling limits:
Implement exponential backoff — Wait progressively longer between retries
Cache responses — Avoid repeated requests for the same data
Batch operations — Combine multiple actions into fewer requests when possible
Use webhooks — For real-time updates, use webhook notifications instead of polling
Example retry logic (pseudocode):
def api_request_with_retry ( url , max_retries= 5 ) :
for attempt in range ( max_retries ):
response = make_request ( url )
if response.status_code == 429 :
wait_time = 2 ** attempt # 1, 2, 4, 8, 16 seconds
raise Exception ( " Max retries exceeded " )
If your use case requires higher rate limits, contact our support team to discuss custom plans with increased API capacity.