> For the complete documentation index, see [llms.txt](https://docs.hub88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hub88.io/developer-docs/hub88-apis/rate-limits.md).

# 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:

* [**`POST /operator/generic/v2/freebet/prepaids/list`**](/developer-docs/operator-api-reference/freebets-api.md#post-operator-generic-v2-freebet-prepaids-list) - maximum **1 request per minute**
* [**`POST /operator/generic/v2/game/list`**](/developer-docs/operator-api-reference/games-api.md#get-the-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:

```json
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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hub88.io/developer-docs/hub88-apis/rate-limits.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.