> For the complete documentation index, see [llms.txt](https://docs.sportsapi360.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportsapi360.com/cricket-docs/cricket-api/all-endpoints-v5/player-list.md).

# Player List

### Player List

Retrieves a paginated list of cricket players, with optional filtering by name, country, and gender.

#### Query Parameters

| Parameter | Required | Description                                                         |
| --------- | -------- | ------------------------------------------------------------------- |
| `api_key` | Yes      | Your API access token. Use the `{{api_token}}` collection variable. |
| `q`       | No       | Search players by name (e.g. `Virat Kohli`).                        |
| `country` | No       | Filter by 2-letter ISO country code (e.g. `in`, `au`, `pk`).        |
| `gender`  | No       | Filter by gender. Accepted values: `male`, `female`.                |
| `page`    | No       | Page number for paginated results. Starts at `1`.                   |
| `limit`   | No       | Number of players to return per page.                               |

#### Response

Returns a paginated list of player objects, each containing the player ID, name, country, gender, and role.

#### Authentication

Pass your API token via the `api_key` query parameter.

```json
{"openapi":"3.0.3","info":{"title":"All Endpoints V5","version":"1.0.0"},"servers":[{"url":"https://apiv5.sportsapi360.com"}],"paths":{"/cricket/v1/players":{"get":{"summary":"Player List","description":"## Player List\n\nRetrieves a paginated list of cricket players, with optional filtering by name, country, and gender.\n\n### Query Parameters\n\n| Parameter | Required | Description |\n|-----------|----------|-------------|\n| `api_key` | Yes | Your API access token. Use the `{{api_token}}` collection variable. |\n| `q` | No | Search players by name (e.g. `Virat Kohli`). |\n| `country` | No | Filter by 2-letter ISO country code (e.g. `in`, `au`, `pk`). |\n| `gender` | No | Filter by gender. Accepted values: `male`, `female`. |\n| `page` | No | Page number for paginated results. Starts at `1`. |\n| `limit` | No | Number of players to return per page. |\n\n### Response\n\nReturns a paginated list of player objects, each containing the player ID, name, country, gender, and role.\n\n### Authentication\n\nPass your API token via the `api_key` query parameter.","operationId":"playerList","parameters":[{"name":"q","in":"query","schema":{"type":"string"},"description":"Search team by name, short name"},{"name":"country","in":"query","schema":{"type":"string"},"description":"2 letter Country ISO Code (example - country=au)"},{"name":"gender","in":"query","schema":{"type":"string"},"description":"Filter team by gender (male, female)"},{"name":"page","in":"query","schema":{"type":"string"},"description":"Page Number for request"},{"name":"limit","in":"query","schema":{"type":"string"},"description":"Number of items to list in each API request"},{"name":"api_key","in":"query","required":true,"schema":{"type":"string"},"description":"API Access token"}],"responses":{"200":{"description":"Player List","headers":{"CF-RAY":{"schema":{"type":"string"}},"Cache-Control":{"schema":{"type":"string"}},"Connection":{"schema":{"type":"string"}},"Content-Encoding":{"schema":{"type":"string"}},"Date":{"schema":{"type":"string"}},"Nel":{"schema":{"type":"string"}},"Report-To":{"schema":{"type":"string"}},"Server":{"schema":{"type":"string"}},"Transfer-Encoding":{"schema":{"type":"string"}},"Vary":{"schema":{"type":"string"}},"X-Request-Id":{"schema":{"type":"string"}},"alt-svc":{"schema":{"type":"string"}},"cf-cache-status":{"schema":{"type":"string"}}},"content":{"application/json":{"schema":{"type":"object","properties":{"data":{"type":"array","items":{"type":"object","properties":{"batting_point":{"type":"number"},"batting_style":{"type":"string"},"birth_date":{"type":"string"},"birth_place":{"type":"string"},"bowling_point":{"type":"number"},"bowling_style":{"type":"string"},"country":{"type":"string"},"country_short":{"type":"string"},"fielding_position":{"type":"string"},"gender":{"type":"string"},"id":{"type":"string"},"image_url":{"type":"string"},"name":{"type":"string"},"playing_role":{"type":"string"},"primary_team":{"type":"string"},"short_name":{"type":"string"},"slug":{"type":"string"},"status":{"type":"string"},"updated_at":{"type":"string"}}}},"meta":{"type":"object","properties":{"api_version":{"type":"string"},"page":{"type":"object","properties":{"has_more":{"type":"boolean"},"limit":{"type":"number"},"page":{"type":"number"},"total":{"type":"number"},"total_pages":{"type":"number"}}},"provider":{"type":"string"},"request_id":{"type":"string"}}},"success":{"type":"boolean"}}}}}}}}}}}
```


---

# 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.sportsapi360.com/cricket-docs/cricket-api/all-endpoints-v5/player-list.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.
