The Rate Limits page gives you a real-time view of how your client's Bet Concierge API quota is being consumed in the current rate-limit window. Use it to spot approaching limits before they affect your users.
This page is only available when the Bet Concierge product is enabled for your client. If your client does not have Bet Concierge, this section will not appear in the navigation.
Click Bet Concierge in the top navigation bar. The interface opens directly on the Rate Limits page.
If no client is selected, the page will prompt you to select a client before rate limit data can be displayed.
Each active rate-limit window is displayed as a separate card. A card contains:
Rate limit key — a technical identifier for the window, shown in monospace at the top of the card. The key format is {tokenValidationId}#{storeClientId}.
Requests used — the number of requests consumed out of the total limit for this window (e.g. 1,200 / 10,000).
Usage bar — a horizontal progress bar that fills proportionally to the number of requests consumed. The colour changes based on how close you are to the limit:
| Colour | Meaning |
|---|---|
| Green | Usage is below the configured alert threshold |
| Orange | Usage has reached or exceeded the alert threshold |
| Red | The limit has been reached |
Expires at — the date and time at which the current window resets.
If the page shows no cards, it means no rate-limit data was found for the currently selected client. This can happen when no requests have been made in the current billing window or when the client's tokenValidationId or storeClientId is not yet matched in the rate-limit system.
If loading fails, a message will indicate that the data could not be retrieved. Refreshing the page will retry the request.
Rate limit settings — such as the client request limit, alert threshold, and billing period — are configured in the Bet Concierge tab of the client's organization settings. See Bet Concierge Settings for details.