> 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/players.md).

# Players

### Overview

Use this endpoint to retrieve the list of players.

This endpoint returns single competitors only.

It does not return teams or doubles pairings.

Each player includes an SR competitor ID in the format `sr:competitor:{id}`.

### Request

**URL**

`GET https://golf.livedata.sportradar.com/golf/v1/static/players`

### Example request

{% code title="List players" overflow="wrap" %}

```http
GET /golf/v1/static/players HTTP/1.1
Host: golf.livedata.sportradar.com
Authorization: Bearer <JWT_TOKEN>
```

{% endcode %}

{% hint style="info" %}
Use this endpoint for player reference data. Use [Entrylist](/live-data/live-data-golf-api-design/ld-golf-api-documentation/ld-golf-api-endpoints-static/entrylist.md) when you need tournament-specific player assignments.
{% endhint %}

### Response example

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

```
{
  "players": [
    {
      "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",
      "gender": "MALE",
      "birthdate": "2002-02-05"
    },
    { ... }
  ],
  "pagination": {
    "page": 1,
    "page_size": 100,
    "total": 1
  }
}
```

{% endcode %}

### Response fields

| field                            | type    | description                             | required | required in PGA | old IMGA API equivalent                             |
| -------------------------------- | ------- | --------------------------------------- | -------- | --------------- | --------------------------------------------------- |
| players                          | Array   | Array of players                        | yes      |                 | array of players was a root element of the response |
| players\[].id                    | Integer | Numeric ID of the player                | yes      |                 | playerId                                            |
| players\[].sr\_player\_id        | String  | SR ID of the player                     | yes      |                 | -                                                   |
| players\[].country               | String  | 3-character FIFA country code           | yes      |                 | country                                             |
| players\[].display\_name         | String  | Full player name used for display       | yes      |                 | displayName                                         |
| players\[].first\_name           | String  | First name of the player                | yes      |                 | firstName                                           |
| players\[].last\_name            | String  | Last name of the player                 | yes      |                 | lastName                                            |
| players\[].is\_amateur           | Boolean | Indicates whether the player is amateur | yes      |                 | isAmateur                                           |
| players\[].player\_pga\_tour\_id | String  | PGA Tour player identifier              | no       | yes             | playerPGATourId                                     |
| players\[].gender                | String  | Player gender: `MALE` or `FEMALE`.      | yes      |                 | gender                                              |
| players\[].birthdate             | Date    | Player birth date                       | yes      |                 | dateOfBirth                                         |
| pagination                       | Object  | Pagination details for the response.    | yes      |                 | -                                                   |
| pagination.page                  | Integer | Current result page.                    | yes      |                 | -                                                   |
| pagination.page\_size            | Integer | Maximum results returned on this page.  | yes      |                 | -                                                   |
| pagination.total                 | Integer | Total players across all result pages.  | yes      |                 | -                                                   |

### Related endpoints

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