> 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/endpoints-and-entities/endpoints/players.md).
# Players
Retrieve detailed player information via one of our 5 player endpoints.
You can retrieve more detailed information by using the correct includes. Per endpoint you can find the details including base URL, parameters, includes and more.
* **GET All Players:** returns all the players that are accessible within your subscription.
* **GET Player by ID:** returns player information from your requested player ID.
* **GET Players by Country ID:** returns player information from your requested country ID.
* **GET Players Search by Name:** returns all the players that match your search query.
* **GET Last Updated Players:** returns all the players that have received updates in the past two hours.
#### Include options
[`sport`](https://docs.sportmonks.com/v3/core-api/) [`country`](https://docs.sportmonks.com/v3/core-api/) [`city`](https://docs.sportmonks.com/v3/core-api/) [`nationality`](https://docs.sportmonks.com/v3/core-api/) [`transfers`](/v3/endpoints-and-entities/entities/other.md#transfer) [`pendingTransfers`](/v3/endpoints-and-entities/entities/other.md#transfer) [`teams`](/v3/endpoints-and-entities/entities/team-player-squad-coach-and-referee.md#team) [`statistics`](/v3/endpoints-and-entities/entities/statistic.md#playerstatistic) [`latest`](/v3/endpoints-and-entities/entities/fixture.md#fixture) [`position`](https://docs.sportmonks.com/v3/core-api/) [`detailedPosition`](https://docs.sportmonks.com/v3/core-api/) [`lineups`](/v3/endpoints-and-entities/entities/fixture.md#lineup) [`trophies`](/v3/endpoints-and-entities/entities/other.md#participanttrophy) [`metadata`](/v3/endpoints-and-entities/entities/other.md#metadata)
{% hint style="info" %}
The `latest` include on `Player` returns their lineup records for appearances in fixtures played in the last 6 months.
{% endhint %}
**Related Entities:**
Get an overview and explanation of all the fields returned in the API response. The related entities for the player endpoints are:
* [Player](/v3/endpoints-and-entities/entities/team-player-squad-coach-and-referee.md#player)
{% hint style="info" %}
Remember, our historical data will be integrated into the new version of our API gradually. So, the historical data is not yet complete. However, we will be loading more historical data continuously.
{% 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/endpoints-and-entities/endpoints/players.md?ask=&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.
