# Search Data API

## Player Search

> \## Endpoint Description\
> \
> This endpoint allows users to search for cricket players by their name. It retrieves player information based on the query parameter provided in the request.\
> \
> \### Request\
> \
> \- \*\*Method\*\*: GET\
> &#x20;   \
> \- \*\*URL\*\*: \`<https://apiv3.sportsapi360.com/cricket/api/v2/search/player\\`\\>
> &#x20;   \
> \- \*\*Query Parameters\*\*:\
> &#x20;   \
> &#x20;   \- \`query\` (string): The name of the player to search for. For example, \`Virat Kohli\`.\
> &#x20;       \
> \
> \### Response\
> \
> The response will return a JSON array containing player details that match the search query. Each player object in the response may include the following fields:\
> \
> \- \`name\`: The name of the player.\
> &#x20;   \
> \- \`fullName\`: The full name of the player.\
> &#x20;   \
> \- \`playerID\`: A unique identifier for the player.\
> &#x20;   \
> \- \`birthPlace\`: The birthplace of the player.\
> &#x20;   \
> \- \`playerRank\`: The rank of the player (if available).\
> &#x20;   \
> \- \`image\`: A URL to the player's image.\
> &#x20;   \
> \
> \### Notes\
> \
> \- Ensure that the \`query\` parameter is properly encoded if it contains spaces or special characters.\
> &#x20;   \
> \- The response may contain multiple player objects or none, depending on the search results.\
> &#x20;   \
> \- Some fields in the response may be empty or null if the information is not available.\
> &#x20;   \
> \
> This endpoint is useful for applications that require player information for display or analytics purposes.

```json
{"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Search Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/search/player":{"get":{"tags":["Search Data API"],"summary":"Player Search","description":"## Endpoint Description\n\nThis endpoint allows users to search for cricket players by their name. It retrieves player information based on the query parameter provided in the request.\n\n### Request\n\n- **Method**: GET\n    \n- **URL**: `https://apiv3.sportsapi360.com/cricket/api/v2/search/player`\n    \n- **Query Parameters**:\n    \n    - `query` (string): The name of the player to search for. For example, `Virat Kohli`.\n        \n\n### Response\n\nThe response will return a JSON array containing player details that match the search query. Each player object in the response may include the following fields:\n\n- `name`: The name of the player.\n    \n- `fullName`: The full name of the player.\n    \n- `playerID`: A unique identifier for the player.\n    \n- `birthPlace`: The birthplace of the player.\n    \n- `playerRank`: The rank of the player (if available).\n    \n- `image`: A URL to the player's image.\n    \n\n### Notes\n\n- Ensure that the `query` parameter is properly encoded if it contains spaces or special characters.\n    \n- The response may contain multiple player objects or none, depending on the search results.\n    \n- Some fields in the response may be empty or null if the information is not available.\n    \n\nThis endpoint is useful for applications that require player information for display or analytics purposes.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"query","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}}
```

## Team Search

> \## API Endpoint: Search Team\
> \
> \### Purpose\
> \
> This endpoint allows users to search for cricket teams based on a specified query. It is particularly useful for retrieving team information, such as the team's name, ID, short name, and associated image.\
> \
> \### Request\
> \
> \- \*\*Method:\*\* GET\
> &#x20;   \
> \- \*\*URL:\*\* \`<https://apiv3.sportsapi360.com/cricket/api/v2/search/team\\`\\>
> &#x20;   \
> \
> \#### Query Parameters\
> \
> \- \*\*query\*\* (string, required): The name or part of the name of the cricket team you want to search for. For example, to search for the England cricket team, you would use \`query=England\`.\
> &#x20;   \
> \
> \### Expected Response Format\
> \
> The response will be a JSON array containing objects that represent the teams matching the search criteria. Each object will include the following fields:\
> \
> \- \*\*name\*\* (string): The full name of the cricket team.\
> &#x20;   \
> \- \*\*teamID\*\* (string): A unique identifier for the team.\
> &#x20;   \
> \- \*\*shortName\*\* (string): A shorter version of the team's name.\
> &#x20;   \
> \- \*\*image\*\* (string): A URL or path to an image representing the team.\
> &#x20;   \
> \
> \### Additional Notes\
> \
> \- Ensure that the \`query\` parameter is URL-encoded if it contains special characters.\
> &#x20;   \
> \- The response may return an empty array if no teams match the search criteria.\
> &#x20;   \
> \- This endpoint is useful for applications that require dynamic team information based on user input.

```json
{"openapi":"3.0.0","info":{"title":"CRICKET API V3","version":"1.0.0"},"tags":[{"name":"Search Data API"}],"servers":[{"url":"https://apiv3.sportsapi360.com"}],"security":[{"apikeyAuth":[]}],"components":{"securitySchemes":{"apikeyAuth":{"type":"http","scheme":"x-api-key"}}},"paths":{"/cricket/api/v2/search/team":{"get":{"tags":["Search Data API"],"summary":"Team Search","description":"## API Endpoint: Search Team\n\n### Purpose\n\nThis endpoint allows users to search for cricket teams based on a specified query. It is particularly useful for retrieving team information, such as the team's name, ID, short name, and associated image.\n\n### Request\n\n- **Method:** GET\n    \n- **URL:** `https://apiv3.sportsapi360.com/cricket/api/v2/search/team`\n    \n\n#### Query Parameters\n\n- **query** (string, required): The name or part of the name of the cricket team you want to search for. For example, to search for the England cricket team, you would use `query=England`.\n    \n\n### Expected Response Format\n\nThe response will be a JSON array containing objects that represent the teams matching the search criteria. Each object will include the following fields:\n\n- **name** (string): The full name of the cricket team.\n    \n- **teamID** (string): A unique identifier for the team.\n    \n- **shortName** (string): A shorter version of the team's name.\n    \n- **image** (string): A URL or path to an image representing the team.\n    \n\n### Additional Notes\n\n- Ensure that the `query` parameter is URL-encoded if it contains special characters.\n    \n- The response may return an empty array if no teams match the search criteria.\n    \n- This endpoint is useful for applications that require dynamic team information based on user input.","parameters":[{"name":"x-api-key","in":"header","schema":{"type":"string"}},{"name":"query","in":"query","schema":{"type":"string"}}],"responses":{"200":{"description":"OK","headers":{},"content":{"application/json":{"schema":{"type":"object"}}}}}}}}}
```


---

# Agent Instructions: 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:

```
GET https://docsv3.sportsapi360.com/cricket-docs/api-collection-cricket/search-data-api.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
