π Overview
Rate limits exist across FNLBβs APIs to prevent spam, abuse, and service overload. The FNLB API uses global rate limiting as well as per-endpoint rate limits to ensure fair usage and protect system stability.π Global Rate Limit
- Limit:
100 requests per 10 seconds - Scope: Per IP Address (globally across all endpoints)
- Reset: Every 10 seconds
429 Too Many Requests error.
π Per-Endpoint Rate Limits
In addition to the global rate limit, some API endpoints may have individual rate limits based on their sensitivity or resource intensity. These limits help prevent misuse of specific endpoints and ensure availability for all users.- Rate limits vary by endpoint.
- Limits are enforced in addition to the global rate limit.
- If a per-endpoint limit is exceeded, a
429error will be returned.
π Exceeding the Limit
When you exceed either a global or per-endpoint rate limit, the server responds with:Retry-Afterheader indicates how many seconds to wait before retrying.
π Best Practices
- Implement retry logic: Automatically back off and retry after the time specified in the
Retry-Afterheader. - Avoid bursts: Spread your requests evenly over time.
- Queue your requests: Use a task queue or request scheduler in your app to prevent accidental spikes.
- Monitor usage: Keep track of your request volume and avoid unnecessary calls.
π§ͺ Example in JavaScript (with Retry)
π‘ Need More Capacity?
If your application needs higher throughput, contact FNLB Support to request increased rate limits.Join Discord
Get help, support, or chat with other developers

