API throttle rate limits for low‑traffic NetBox instances
0 reputation · 24 Jun 2023, 23:04 UTC
Goal: Reduce resource consumption and hosting costs for a NetBox deployment that serves minimal API traffic by lowering the API request throttle rate.
Constraint: The API_THROTTLE_RATE setting applies globally to all API endpoints, including the browsable UI and external automation scripts, and only takes effect after a service restart; it does not influence background workers such as RQ or scheduled reports.
Uncertainty: Determining a safe minimum throttle value that avoids frequent HTTP 429 responses for legitimate automation and UI interactions while still delivering measurable savings is not clearly defined in the documentation, especially for variable request patterns across different environments.
What is the lowest API_THROTTLE_RATE that typical automation scripts can sustain without encountering throttling errors?
How can administrators safely test the impact of a reduced throttle setting on UI responsiveness before applying it to production?
Does NetBox provide any mechanism to apply different throttle limits to specific API views or clients?
netbox