> 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-integration/readme/static-data/data-frequency-for-endpoints-restful.md).

# Data Frequency for Endpoints (RESTful)

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

| Sport | REST Endpoint                                                      | Frequency                                |
| ----- | ------------------------------------------------------------------ | ---------------------------------------- |
| Golf  | `https://dde-api.data.imgarena.com/golf/tournaments`               | Every 12hours                            |
| Golf  | `https://dde-api.data.imgarena.com/golf/tournaments/{id}/schedule` | Every minute for the upcoming tournament |

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.


---

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

```
GET https://docs.sportradar.com/golf-integration/readme/static-data/data-frequency-for-endpoints-restful.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.