> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/concepts/participant-team-and-player.md). # Participants, Teams & Players This guide explains how participants, teams, and players are defined in TRADE, so you can accurately work with fixture data across different sports. ### **Participant** In TRADE, a participant is any entity that directly competes in a fixture. The participant can be either a team (e.g., Manchester City in football) or an individual (e.g., Rafael Nadal in tennis). The `participant id` always refers to the entity playing directly under the fixture—this can be a team or, in individual sports, a player. For example: * In football, the participants are the two teams. * In tennis, the participants are the two players. ### **Team** A team is a specific type of participant representing a group of players competing together (e.g., Real Madrid in football). In team sports, the team is the participant, and its `participant id` is the team id. Teams can have multiple players associated with them. ### **Player** A player is an individual entity who plays under a team in team sports. Players are not considered participants themselves in the context of the fixture—they are linked to a team (participant) and are referenced in player markets or lineups. For example: * In football, Harry Kane is a player for the participant (team) Bayern Munich. * In tennis, there are no "players" under a team; the tennis player is the participant. **Key Clarification** * In individual sports (like tennis), the participant is always the player, and there is no team or player entity under the participant. * In team sports, the participant is the team, and players are entities under the team, used for lineups and player-specific markets. --- # 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.lsports.eu/u/trade/concepts/participant-team-and-player.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.