> 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/live-data/live-data-golf-api-design/ld-golf-api-documentation/live-event-types.md).

# Live Event types

List of available live event types and their payloads that could be received via WebSocket or REST endpoints.

### Overview

This section documents the `payload` object for each golf live event type.

WebSocket events wrap this payload in a CloudEvents envelope.

REST history endpoints return the same event object without the outer envelope.

### What to expect

* `event_time` is the on-course timestamp for the action.
* `team_id` and `sr_team_id` identify the active team or side.
* `hole_number` is the visible hole number. `hole_sequence` is the course order.

{% hint style="info" %}
If an event is delivered with `action: DELETE`, the `payload` field is omitted.
{% endhint %}

### Event groups

* [Round Events](/live-data/live-data-golf-api-design/ld-golf-api-documentation/live-event-types/round-events-sportevent.md)
* [Hole Events](/live-data/live-data-golf-api-design/ld-golf-api-documentation/live-event-types/hole-events.md)
* [Standard Stroke Event](/live-data/live-data-golf-api-design/ld-golf-api-documentation/live-event-types/standard-stroke-event.md)
* [Ball Drops and Penalty Events](/live-data/live-data-golf-api-design/ld-golf-api-documentation/live-event-types/ball-drops-and-penalty-events.md)


---

# 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/live-data/live-data-golf-api-design/ld-golf-api-documentation/live-event-types.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.