> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/itservices/models/tournament-profiling-api/limitations.md).

# Limitations

### Rate limits

To maintain system stability and performance, the Tournament Profiling API enforces rate limits on incoming requests. 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. 

#### POST Endpoint

<table><thead><tr><th width="199.94781494140625">Requests per minute</th></tr></thead><tbody><tr><td>15</td></tr></tbody></table>

#### GET Endpoint

<table><thead><tr><th width="199.94781494140625">Requests per minute</th></tr></thead><tbody><tr><td>1</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.

#### POST Endpoint

<table><thead><tr><th width="199.94781494140625">Requests</th></tr></thead><tbody><tr><td>15</td></tr></tbody></table>

#### GET Endpoint

<table><thead><tr><th width="199.94781494140625">Requests</th></tr></thead><tbody><tr><td>1</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportradar.com/itservices/models/tournament-profiling-api/limitations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.