Skip to main content

Rate Limits for BetHub Betting API

The BetHub Betting API enforces rate limits to ensure fair usage and to maintain optimal performance for all users. Understanding these limits is essential for integrating our API into your applications effectively, especially when using RapidAPI as your distribution platform.

What Are Rate Limits?​

Rate limits define the number of API requests you can make within a specific period. They are set to prevent excessive use that could impact the API's availability and performance for other users. These limits help ensure that all users have a consistent and reliable experience.

Rate Limits on RapidAPI​

When you access the BetHub Betting API through RapidAPI, your usage is governed by the rate limits defined in the pricing plan you choose. Here’s a breakdown of how these limits work:

Pricing Tiers​

  1. Free Tier:

    • Requests: Up to 1000 requests per hour.
    • Features: Access to basic API endpoints with limited data.
    • Purpose: Ideal for testing and small-scale projects.

  2. Pro Tier:

    • Requests: Up to 20 requests per minute.
    • Features: Access to all API endpoints with standard data.
    • Purpose: Suitable for individual developers and small applications.

  3. Ultra Tier:

    • Requests: Up to 50 requests per minute.
    • Features: Access to all API endpoints with priority support and enhanced data.
    • Purpose: Designed for startups and growing applications.

  4. Mega Tier:

    • Requests: Up to 100 requests per minute.
    • Features: Full API access with dedicated support and custom SLAs.
    • Purpose: Tailored for large-scale applications and enterprises.

How Rate Limiting Works​

  • Request Counting: Each request to an API endpoint is counted towards your daily limit. The limit resets every 24 hours.
  • Exceeded Limits: If you exceed your daily request limit, further requests will be denied until the limit resets.
  • Monitoring Usage: RapidAPI provides a dashboard to monitor your API usage and track your remaining requests in real-time.

Managing Your Usage​

To ensure uninterrupted access to the BetHub Betting API, consider the following best practices:

  • Choose the Right Plan: Select a pricing tier that aligns with your usage needs and anticipated growth.
  • Optimize Requests: Make efficient use of API requests by retrieving only the data you need.
  • Monitor Usage: Regularly check your usage statistics on the RapidAPI dashboard to avoid hitting rate limits unexpectedly.
  • Upgrade as Needed: If your application scales and requires more requests, consider upgrading to a higher-tier plan.

Handling Rate Limit Errors​

If you encounter rate limit errors (HTTP status code 429), your requests have exceeded the allowed limit. Here’s how to handle them:

  • Implement Backoff: Use exponential backoff strategies to retry requests after a delay.
  • Reduce Frequency: Temporarily reduce the frequency of your requests until the limit resets.
  • Contact Support: If you believe you need a higher limit, reach out to our support team for assistance.

Contact and Support​

If you have any questions regarding rate limits or need assistance with your API usage, our support team is here to help:

By understanding and adhering to these rate limits, you can ensure a smooth and efficient experience with the BetHub Betting API. Thank you for choosing BetHub, and we look forward to supporting your journey in sports data analytics!

This rate-limits.md document provides a comprehensive overview of the rate limits applicable to your BetHub Betting API when offered through RapidAPI. It includes information on pricing tiers, managing usage, and handling rate limit errors to help users effectively integrate and utilize your API.