Get cricket news stories about one team by team ID
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the news stories associated with a single cricket team, selected by the required numeric `teamId` path parameter (default 2). Take the teamId from the `teamId` field returned by the teams list operation. 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; for the default teamId 2 the example seoTitle names India. 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` (an interview label or a tour label in the example), `storyType` (for example Interviews or Previews), `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 team with no coverage against a live response before depending on them.
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/teams-get-news API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/teams-get-news?key=<API_KEY>&teamId=2'
Query Result
Use Cases
- Populate a team-news panel alongside that team's schedules and results, using the same teamId that drives the fixtures and squad views.
- Assemble a team-focused editorial queue using teamId rather than collecting unrelated articles with matching team-name words, then open each story through the news detail operation by id.
- Notify supporters of a followed team when a new story id appears for their teamId, comparing the ids from each poll with the set you stored on the previous run.
- Group a team's recent stories by storyType to build filter chips such as interviews and previews on a supporter app or a club-style fan page.
- Feed an analyst or fantasy research dashboard with the latest headlines for each team in an upcoming fixture by calling the operation once per teamId.
Frequently asked questions
What does the team news operation return?
It returns the news stories for one team. 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 teamId?
Use the teamId field returned by the teams list operation. The default value 2 is the sample id supplied with the parameter notes, and the example response for it carries a page title naming India, so confirm the mapping in your own teams response before labelling it.
Can I page through older team stories?
The supplied evidence documents only the teamId path parameter and no paging cursor. How many stories come back, and whether older ones are reachable, has to be confirmed against a live response.
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 any entry that has no story key when you build article cards.
How do I read the full article for a story?
Each story carries an integer id. Pass that id to the news detail operation to request the article body, because this operation returns only the headline, intro and cover image reference.
Are the stories always about the requested team?
The operation is documented as news by team, but the evidence does not say how a story is matched to a team. A story may mention several sides, so read the headline and context before you treat it as exclusive to one team.
Which response fields are verified?
None. There is no recorded probe for this operation, and the source example is cut off at 4,000 characters, so field names, types and the story count are unconfirmed until you inspect a live response.
What happens for a team with no news?
The evidence does not say. Treat a missing or empty storyList as a normal outcome, because coverage depends on the team, and show an empty state instead of treating it as an error.