# Limitations

### Rate limits

To maintain system stability and performance, the Late Bet Score API enforces rate limits on incoming requests. Rate limits specify the maximum number of requests that can be made in a given time frame, typically measured in requests per second (RPS). If the rate limit is exceeded, the API will return a `HTTP 429 Too Many Requests` response, and further requests will be throttled until the rate limit window resets. Implement exponential backoff strategies in your applications to handle rate limiting gracefully. 

<table><thead><tr><th width="199.94781494140625">Requests per second</th></tr></thead><tbody><tr><td>300</td></tr></tbody></table>

***

### Burst

The rate limit controls sustained traffic over time, while the burst limit defines the number of requests the API can handle concurrently, meaning requests run in parallel. If the burst limit is exceeded, the system responds with `HTTP 429 Too Many Requests` . These limits together provide more robust and flexible traffic control, especially in scenarios with variable or unpredictable load.

<table><thead><tr><th width="200.47308349609375">Burst requests </th></tr></thead><tbody><tr><td>200</td></tr></tbody></table>


---

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

```
GET https://docs.sportradar.com/itservices/models/late-bet-score-lbs-api/limitations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.