> 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-rankings.md).

# Player Rankings

### Player Rankings

Retrieves the official ICC player rankings (batsmen, bowlers, or all-rounders) for a specified format and gender.

**Note:** the actual endpoint URL is `/cricket/v1/rankings` with `type=Batsmen` (or `Bowlers` / `AllRounders`) as a query parameter.

#### Query Parameters

| Parameter | Required | Description                                                                 |
| --------- | -------- | --------------------------------------------------------------------------- |
| `api_key` | Yes      | Your API access token. Use the `{{api_token}}` collection variable.         |
| `type`    | Yes      | The ranking category. Accepted values: `Batsmen`, `Bowlers`, `AllRounders`. |
| `format`  | Yes      | The match format. Accepted values: `Odi`, `T20`, `Test`.                    |
| `gender`  | Yes      | The gender category. Accepted values: `men`, `women`.                       |
| `page`    | No       | Page number for paginated results. Starts at `1`.                           |
| `limit`   | No       | Number of ranking entries to return per page.                               |

#### Response

Returns a ranked list of players with their ICC rating points, ranking position, and player details.

#### 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/rankings":{"get":{"summary":"Player Rankings","description":"## Player Rankings\n\nRetrieves the official ICC player rankings (batsmen, bowlers, or all-rounders) for a specified format and gender.\n\n**Note:** the actual endpoint URL is `/cricket/v1/rankings` with `type=Batsmen` (or `Bowlers` / `AllRounders`) as a query parameter.\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| `type` | Yes | The ranking category. Accepted values: `Batsmen`, `Bowlers`, `AllRounders`. |\n| `format` | Yes | The match format. Accepted values: `Odi`, `T20`, `Test`. |\n| `gender` | Yes | The gender category. Accepted values: `men`, `women`. |\n| `page` | No | Page number for paginated results. Starts at `1`. |\n| `limit` | No | Number of ranking entries to return per page. |\n\n### Response\n\nReturns a ranked list of players with their ICC rating points, ranking position, and player details.\n\n### Authentication\n\nPass your API token via the `api_key` query parameter.","operationId":"playerRankings","parameters":[{"name":"type","in":"query","schema":{"type":"string"},"description":"Batsmen, Bowlers, AllRounders"},{"name":"format","in":"query","schema":{"type":"string"},"description":"Odi, T20, Test"},{"name":"gender","in":"query","schema":{"type":"string"},"description":"men, women"},{"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 Rankings","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":{"format":{"type":"string"},"gender":{"type":"string"},"player_id":{"type":"string"},"player_image":{"type":"string"},"player_name":{"type":"string"},"player_short":{"type":"string"},"rank":{"type":"number"},"rank_type":{"type":"string"},"rating":{"type":"number"},"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-rankings.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.
