List the cricket players currently shown in the trending-searches list, with player id, name, team name and face image ID
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the list of cricket players that appear in the trending-searches list. The operation takes no parameters. The source 200 example is an object with a category label (TRENDING SEARCHES in the example) and a player array. Each player entry carries id (a string of digits), name, teamName and faceImageId (an integer). The id values are the identifiers that the player profile, batting and other player operations of this product accept as playerId. No live probe was recorded for this endpoint, so every field described here comes from the source example and is not independently verified. The list length, order and contents depend on coverage and are not documented as fixed, and the example repeats at least one player (the same id appears twice), so deduplicate on id before display.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/cricbuzz-cricket/players-list-trending No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-list-trending?key=<API_KEY>'
Query Result
Use Cases
- Build a trending-player discovery strip that shows name, teamName and a face image, and links each card to the player profile operation by id.
- Seed an editorial research queue with the listed players and store each id, so writers can open the profile, batting and news data for every name from one place.
- Fill a search-box suggestion panel with trending names before the user types, then switch to the player search operation when they look for someone who is not listed.
- Group the list by teamName to show a players-in-the-spotlight block on a national team or franchise hub page, and label it as an editorial list, not a ranking.
- Poll the list on a schedule and compare the id values with the previous snapshot to flag newly listed players for a content calendar.
Frequently asked questions
What does the trending players operation return?
It returns a category label and a player array. Each player has id (a string), name, teamName and faceImageId (an integer), according to the source 200 example. No live probe was recorded, so these fields are source-example fields.
Does this operation take any parameters?
No. It is a GET request with no path or query parameters, so there is nothing to filter or page. Any narrowing by team or format has to be done on your side after the response arrives.
Is the list a popularity ranking or a search-volume report?
No. The response gives no score, count or rank value, and the entry order is not documented as a ranking. Treat it as a list of players that the data source currently highlights, for example as a content-research queue.
Why does the same player appear twice in the example?
The source example contains the same id twice, so duplicates are possible in the payload. Deduplicate on id before rendering a list, and do not assume the number of entries is fixed.
How do I use the id with the other player operations?
Pass the id value as playerId to the player profile operation or the batting statistics operation. The list returns id as a string of digits, while those operations declare playerId as a number, so send the digits unchanged.
Can I use faceImageId as a unique player key?
No. In the source example several different players share the same faceImageId, so it identifies an image, not a person. Use id as the player key and use faceImageId only to request the picture.
What if a trending-player section looks empty or short?
The list depends on current coverage and is not documented with a minimum size, so build the section to handle a short list and fall back to the player search operation when you need a specific name.