Get cricket news stories about one player by player ID

View all Cricket Live Scores, Scorecards & Stats API endpoints →

Returns the news stories associated with a single player, selected by the required numeric `playerId` path parameter (default 8733). Take the playerId from the `id` field returned by the trending players or player search operations. The operation accepts no other parameters, so the supplied evidence documents no paging cursor for it. No live probe was recorded, so the response description comes from a supplied source example that is truncated at 4,000 characters and unverified. In that example the body is an object with an `appIndex` object (`seoTitle`, `webURL`), a `lastUpdatedTime` string and a `storyList` array. Each `storyList` entry is either a `story` object or an `ad` object with `layout`, `name` and `position`, so a client has to skip the ad slots. A story shows `id` (integer), `hline`, `seoHeadline`, `intro`, `context` (a tour or series label in the example), `storyType`, `source`, `imageId`, `pubTime` (a string of epoch-style digits whose unit is not documented), empty `adsType` and `entitlements` objects and a `coverImage` with `caption`, `id` and `source`. Confirm the exact field set, the number of stories returned and the behaviour for a player with no coverage against a live response before depending on them.

API Features

Player-scoped news by playerId One GET with the playerId path parameter returns stories tied to that player, so a player page does not need to scan a general feed for a name match.
Same ID as the player pages playerId is the id value from the trending players and player search operations, the identifier you already use for profile and statistics pages, so a news tab needs no extra mapping.
ID-based lookup avoids name ambiguity Selecting by numeric id removes the ambiguity of text searches, where several players can share a surname or an abbreviation.
Match and tour context per story In the source example each story has hline, intro, context and storyType, so the context field can show the tour or series and storyType can show the article kind, such as a match feature.
Mixed story and ad entries The example storyList interleaves story objects with ad objects holding layout, name and position. Filter on the story key to keep a clean list of articles.
Cover image references on cards Every example story carries imageId and a coverImage object with caption, id and source, which supports a thumbnail and caption on each card.

Live API Demo

GET /api/project/cricbuzz-cricket/players-get-news

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-get-news?key=<API_KEY>&playerId=8733'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does the player news operation return?

It returns news stories for one player. No probe was recorded, so the shape comes from a truncated, unverified source example: an appIndex object, a lastUpdatedTime string and a storyList array whose entries are story objects or ad placeholders.

Where do I get a valid playerId?

Use the id field returned by the trending players or player search operations. The default value 8733 is the sample id supplied with the parameter notes. Searching by id avoids guessing from a player's name.

Can I page through older player stories?

The supplied evidence lists playerId as the only parameter, so no paging cursor such as lastId is documented for this operation. Check how many stories your own response returns and do not assume a full archive.

Why do some storyList entries have no story fields?

In the source example, some entries are ad objects with layout, name and position instead of a story object. Skip them when you build a list. A probe has not confirmed whether ad entries appear in every response.

How do I read the full article for a story?

This operation returns list cards only: headline, intro, context, story type, source and cover image references. Pass the integer id of a story as newsId to the news detail operation to get the article body.

Are the stories always about the requested player?

The operation is documented as news by player, but the evidence does not describe how a story is matched to a player. Some stories may mention the player alongside others, as match features can, so review the headline and context in your own response.

Which response fields are verified?

None of them have been confirmed by a live probe for this operation. The fields named here, such as hline, intro, context, storyType, pubTime and coverImage, come from a source example truncated at 4,000 characters, so check them against your own response.

What happens for a player with no news?

Coverage depends on the player, so an unknown playerId or a player without stories may return an empty or sparse body. The supplied evidence does not show that case, so handle it defensively.

Related operations

Guides

View Subscription Plans →