Skip to main content

Rate Limiting

Overview​

ReccoBeats enforces rate limits to ensure fair usage and prevent abuse. These rate limits are configured internally.

If you exceed these limits, you'll receive a 429 Too Many Requests response. Please wait before making further requests.

Best Practices​

  • Caching: For high-traffic applications, cache recommendations to reduce the number of requests made to the API.
  • Error Handling: Always include proper error handling to manage API response errors, including rate limiting and invalid requests.
  • Avoid Spam Requests: Make sure your app doesn't bombard the API with excessive requests in a short period of time, as this may result in your key being temporarily blocked.
  • Retry-After Header: Checking the Retry-After header to determine the remaining time before making the next request when a 429 error occurs.