> 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/ld-golf-api-endpoints-static/entrylist.md).

# Entrylist

### Overview

Use this endpoint to retrieve the tournament entry list for a given `tournament_id`.

The response includes all teams and the players assigned to each team.

In stroke play, each player is typically returned as a one-player team.

In team and match play, the response includes all teams across all rounds.

The same player can appear in more than one team.

### Request

**URL**

`GET https://golf.livedata.sportradar.com/golf/v1/static/tournaments/{tournament_id}/entry-list`

### Path parameters

| **Name**        | **Type** | **Required** | **Description**        |
| --------------- | -------- | ------------ | ---------------------- |
| `tournament_id` | integer  | Yes          | Tournament identifier. |

### Example request

{% code title="Get a tournament entry list" overflow="wrap" %}

```http
GET /golf/v1/static/tournaments/12345/entry-list HTTP/1.1
Host: golf.livedata.sportradar.com
Authorization: Bearer <JWT_TOKEN>
```

{% endcode %}

{% hint style="info" %}
For team and match play tournaments, one player can belong to multiple returned teams.
{% endhint %}

### Response example

{% code overflow="wrap" expandable="true" %}

```
{
  "teams": [
    {
      "team_id": 1,
      "sr_team_id": "sr:competitor:1",
      "players": [
        {
          "player_id": 22,
          "sr_player_id": "sr:competitor:22",
          "country": "ENG",
          "display_name": "Tommy Fleetwood",
          "first_name": "Tommy",
          "last_name": "Fleetwood",
          "is_amateur": false,
          "player_pga_tour_id": "30911"
        },
        {...}
      ]
    },
    {...}
  ]
}
```

{% endcode %}

### Response fields

| field                                     | type    | description                                | required | required in PGA | old IMGA API equivalent                           |
| ----------------------------------------- | ------- | ------------------------------------------ | -------- | --------------- | ------------------------------------------------- |
| teams                                     | Array   | Array of teams in the tournament           | yes      |                 | array of teams was a root element of the response |
| teams\[].team\_id                         | Integer | Numeric ID of the team                     | yes      |                 | teamNo                                            |
| teams\[].sr\_team\_id                     | String  | SR ID of the team                          | yes      |                 | -                                                 |
| teams\[].players                          | Array   | List of players assigned to the team       | yes      |                 | players                                           |
| teams\[].players\[].player\_id            | Integer | Numeric ID of the player                   | yes      |                 | playerId                                          |
| teams\[].players\[].sr\_player\_id        | String  | SR ID of the player                        | yes      |                 | -                                                 |
| teams\[].players\[].country               | String  | 3-character FIFA country code              | yes      |                 | country                                           |
| teams\[].players\[].display\_name         | String  | Full player name used for display          | yes      |                 | displayName                                       |
| teams\[].players\[].first\_name           | String  | First name of the player                   | yes      |                 | firstName                                         |
| teams\[].players\[].last\_name            | String  | Last name of the player                    | yes      |                 | lastName                                          |
| teams\[].players\[].is\_amateur           | Boolean | Indicates whether the player is an amateur | yes      |                 | isAmateur                                         |
| teams\[].players\[].player\_pga\_tour\_id | String  | PGA Tour player identifier                 | no       | yes             | playerPGATourId                                   |

### Related endpoints

* [Tournaments list](/live-data/live-data-golf-api-design/ld-golf-api-documentation/ld-golf-api-endpoints-static/tournaments-list.md)
* [Single Tournament](/live-data/live-data-golf-api-design/ld-golf-api-documentation/ld-golf-api-endpoints-static/single-tournament.md)
* [Players](/live-data/live-data-golf-api-design/ld-golf-api-documentation/ld-golf-api-endpoints-static/players.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/ld-golf-api-endpoints-static/entrylist.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.