Rate limits

Hub88 applies rate limiting to selected API endpoints to maintain platform stability and ensure fair usage across all operator partners.

A rate limit defines the maximum number of requests that can be made in a set period. If your integration exceeds this limit, the API will return a 429 Too Many Requests response, and you must wait until the time window resets before retrying.

Rate limits are in place to:

• Protect overall API performance and availability.

• Ensure a fair distribution of resources across all Hub88 partners.

• Encourage efficient integration practices (such as caching and scheduled refreshes).

---

Existing Limits

The following endpoints are rate-limited:

• GET /operator/generic/v2/freebet/prepaids/list - maximum 1 request per minute

• GET /operator/generic/v2/game/list - maximum 1 request per minute

These endpoints typically provide data that changes infrequently. For example, the game list rarely updates more than once per day, so frequent polling is unnecessary.

---

Sample Response

If you exceed the limit (1 request per minute), the API will return:

response_body:	Too Many Requests
status:	429

---

Best Practices

To stay within limits and maintain reliable integration:

• Do not poll aggressively - space requests at least one minute apart.

• Cache responses locally - use your cache to serve data to your application without repeatedly calling the API.

• Refresh strategically - only update data when needed (e.g. once per day for the game list).

• Handle 429 responses gracefully - implement retry logic that waits until the time window has reset before sending another request.