> For the complete documentation index, see [llms.txt](https://hh-specs.handhistory.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hh-specs.handhistory.org/player-object/player-object-definition/id.md).

# id

#### id

The unique identifier for the player within the hand. This Id is used to identify the player in all other locations of the hand history.  This player identifier is hand history specific and does not need to be the same across hand histories.

{% hint style="info" %}
The player "id" is simliar to the "seat"; however, it should be independent from the seat for the case when a player gets up and a new player is seated in the middle of a hand.  In this case, the players would have different player ids but the same seat number.
{% endhint %}

**Type:** integer

**Example:**

```javascript
"id": 3
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://hh-specs.handhistory.org/player-object/player-object-definition/id.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.