> 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/golf/feed-specifications/endpoints-rest/polling-limits.md).

# Polling limits

MG Arena monitor the incoming traffic from our customers and strive to ensure that traffic is controlled, in-keeping with our guidelines and not unnecessarily excessive. We would suggest a polling rate of 5 requests per second, whilst we strive towards implementing rate limiting.

**We recommend the following frequency for your REST requests to ensure that you have the most up-to-date information at all times:**

| REST Endpoint                                                               | Frequency                                |
| --------------------------------------------------------------------------- | ---------------------------------------- |
| `https://dde-api.data.srarena.io/golf/tournaments`                          | Every 12hours                            |
| `https://dde-api.data.srarena.io/golf/tournaments/{id}/schedule`            | Every minute for the upcoming tournament |
| `https://dde-api.data.srarena.io/golf/tournaments/{tournamentId}/entrylist` | Every minute for the upcoming tournament |
| `https://dde-api.data.srarena.io/golf/players`                              | Every 12hours                            |
| `https://dde-api.data.srarena.io/golf/tournaments/liveevents`               | Every second when tournament is live     |

For golf, the initial schedule is received on a Tuesday (2 days before the tournament starts) which will contain the the tee times/groups for rounds 1 and 2. The tee times/groups for rounds 3 and 4 will be released once play for day 2 and 3 are complete. We recommend that you pull the schedule endpoint every Tuesday for the upcoming tournament every minute and after player has finished post round 2 and 3.

### Polling limits

IMG Arena monitor the incoming traffic from our customers and strive to ensure that traffic is controlled, in-keeping with our guidelines and not unnecessarily excessive. We would suggest a polling rate of 10 requests per second measured over a 5 minute interval. Note that this rate limit is across all of our legacy sports and endpoints. If you break this late limit, your requests will start to get throttled, for more information, please contact [support@sportradar.com](mailto:support@imgarena.com)


---

# 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/golf/feed-specifications/endpoints-rest/polling-limits.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.