> 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/match-play-squads.md).

# Match Play Squads

### Overview

Use this endpoint to retrieve squads for a match play team tournament.

The response shows top-level squad assignments such as `USA` and `Europe`.

It does not include individual match pairings.

Use this endpoint when you need team composition for match play tournaments such as the Ryder Cup.

### Request

**URL**

`GET https://golf.livedata.sportradar.com/golf/v1/static/tournaments/{tournament_id}/match-play-squads`

### Path parameters

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

### Example request

{% code title="Get match play squads" overflow="wrap" %}

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

{% endcode %}

{% hint style="info" %}
Use [Match Play Schedule](broken://spaces/OxInYuqpEwbH2S87zaMr/pages/sakkqt8ud886u1WtDf8w) when you need match-level scheduling and pairings.
{% endhint %}

### Response example

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

```
{
  "squads": [
    {
      "name": "USA",
      "squad_id": 12345,
      "sr_squad_id": "sr:competitor:12345",
      "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 | old IMGA API equivalent                            |
| ------------------------------------------ | ------- | ------------------------------------------ | -------- | -------------------------------------------------- |
| squads                                     | Array   | Array of squads in the tournament          | yes      | array of squads was a root element of the response |
| squads\[].squad\_id                        | Integer | Numeric ID of the squad                    | yes      | squadNo                                            |
| squads\[].sr\_squad\_id                    | String  | SR ID of the squad                         | yes      | -                                                  |
| squads\[].name                             | String  | Display name of the squad                  | yes      | squadName                                          |
| squads\[].players                          | Array   | List of players in the squad               | yes      | players                                            |
| squads\[].players\[].player\_id            | Integer | Numeric ID of the player                   | yes      | playerId                                           |
| squads\[].players\[].sr\_player\_id        | String  | SR ID of the player                        | yes      | -                                                  |
| squads\[].players\[].country               | String  | 3-character FIFA country code              | yes      | country                                            |
| squads\[].players\[].display\_name         | String  | Full player name used for display          | yes      | displayName                                        |
| squads\[].players\[].first\_name           | String  | First name of the player                   | yes      | firstName                                          |
| squads\[].players\[].last\_name            | String  | Last name of the player                    | yes      | lastName                                           |
| squads\[].players\[].is\_amateur           | Boolean | Indicates whether the player is an amateur | yes      | isAmateur                                          |
| squads\[].players\[].player\_pga\_tour\_id | String  | PGA Tour player identifier                 | no       | playerPGA                                          |

### 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)
* [Match Play Schedule](broken://spaces/OxInYuqpEwbH2S87zaMr/pages/sakkqt8ud886u1WtDf8w)
* [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/match-play-squads.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.