> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/definitions/types/position-types.md).

# Position types

This reference lists all position-related type IDs available across the Sportmonks Football API. Player records use two position fields: `position_id` (broad category) and `detailed_position_id` (specific role). Coach and staff records use a separate set of role type\_ids from the same `model_type: position` pool.

### Basic positions (`position_id`)

| type\_id | Name       |
| -------- | ---------- |
| 24       | Goalkeeper |
| 25       | Defender   |
| 26       | Midfielder |
| 27       | Attacker   |
| 28       | Unknown    |

### Detailed positions (`detailed_position_id`)

12 detailed positions in total:

| type\_id | Name               |
| -------- | ------------------ |
| 148      | Centre Back        |
| 149      | Defensive Midfield |
| 150      | Attacking Midfield |
| 151      | Centre Forward     |
| 152      | Left Wing          |
| 153      | Central Midfield   |
| 154      | Right Back         |
| 155      | Left Back          |
| 156      | Right Wing         |
| 157      | Left Midfield      |
| 158      | Right Midfield     |
| 163      | Secondary Striker  |

### Staff roles

Same `model_type: position` pool, used for coaching staff rather than players:

| type\_id | Name              |
| -------- | ----------------- |
| 221      | Coach             |
| 226      | Assistant Coach   |
| 227      | Goalkeeping Coach |
| 228      | Forward Coach     |
| 560      | Caretaker Manager |

{% hint style="info" %}
Confirmed via live testing: Lionel Messi (`player_id: 184798`) has `position_id: 27` (Attacker) and `detailed_position_id: 156` (Right Wing).
{% endhint %}


---

# 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.sportmonks.com/v3/definitions/types/position-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.