Rate Limiting
Fello enforces a per-client rate limit on incoming API requests to maintain a stable and reliable service. Exceeding these limits will result in a 429 Too Many Requests response, at which point clients should implement back-off strategies or queue future requests.
Rate Limits
Fello enforces rate limits at both the Custom App (or API Key) level and at the Account level. Each rate limit implementation returns a set of response headers that provide insights into the current rate limit status.
Note: These default rate limits may be increased upon consultation with the Fello team and subsequent approval for elevated limits.
App Level
- GET Endpoints: 100 requests per 10-second window.
- UPDATE Endpoints (including DELETE): 50 requests per 10-second window.
We use sliding window strategy for our 10-second window rate limiter.
Headers
- X-RateLimit-Limit-10: The total number of requests permitted within the current 10-second window.
- X-RateLimit-Remaining-10: The number of requests remaining in the current 10-second window before reaching the limit.
Account Level
An account is permitted up to 350,000 requests per day.
Headers
- X-RateLimit-Limit-day: The total number of requests permitted within the current day.
- X-RateLimit-Remaining-day: The number of remaining requests for the current day before the limit is reached.
Handling Errors
When the rate limit is exceeded, Fello returns a 429 Too Many Requests response. In such cases, consider the following strategies:
- Pause and Retry:
Wait for a brief period before attempting your request again. - Utilize Exponential Backoff:
Incrementally increase the waiting interval between subsequent retries if429responses continue.