Per User Account Rate Limit
BDS applies a rate limit at the user account level. This rate limit dictates the total number of requests that can be made across all APIs associated with a user account within a specified time frame. Birdeye’s data APIs are designed to cater to users with varying needs, and as such, we offer different tiers of access with corresponding rate limits. This page outlines the rate limits for each tier: Free, Premium, Business, and Enterprise. View details for each tiers below.📘 Your Rate Limit is Per User Account It’s important to note that the actual rate limit that is applied when you use BDS APIs is PER ACCOUNT rather than per individual API. This means that the rate limit applies to the total number of requests made across all APIs associated with your Birdeye Data Services account.*rps: requests per second *rpm: requests per minute
Per API Rate Limit
For most APIs within Birdeye Data Services, a very high limit is applied and our clients can query as much as their user account rate limit allows. However there are some exceptions for the heavier APIs that have lower rate limit:
Wallet API Group
It’s important to note that endpoints belonging to the Wallet API group have a different rate limit due to their sensitive nature and potential for high-frequency updates. The rate limit for endpoints within the Wallet API group is set to 30 requests per minute (rpm). This stricter rate limit helps to mitigate excessive traffic and maintain optimal performance for these critical endpoints. These endpoints include:Managing Rate Limits:
To ensure optimal performance and prevent exceeding your rate limit, consider the following best practices:- Monitor Usage: Keep track of your API usage to stay within your allotted rate limit. Monitoring tools and dashboards can help you track usage patterns and identify any potential issues.
- Prioritize Requests: Prioritize your API requests based on their importance and frequency. Allocate resources efficiently to ensure critical operations are not hindered by rate limits.
- Implement Backoff Strategies: Implement backoff strategies to gracefully handle rate limit exceeded errors. This may include implementing exponential backoff or retry-after mechanisms to retry failed requests after a delay.
- Upgrade Packages: If you consistently find yourself hitting the rate limit of your current package, consider upgrading to a higher-tier package with a higher rate limit to accommodate your growing needs.