Get cricket news stories for one series or tournament by series ID
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the news stories attached to a single cricket series, selected by the required numeric `seriesId` path parameter (default 3636). Take the seriesId from the `id` field returned by the series list or series archives 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` (the series name in the example), `storyType` (for example News or Match Features), `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 series 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/series-get-news API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/series-get-news?key=<API_KEY>&seriesId=3636'
Query Result
Use Cases
- Attach editorial coverage to a selected series beside its fixtures and points table, using the same seriesId that drives the schedule and standings views.
- Produce a tournament briefing scoped by seriesId rather than mixing similarly named editions through keyword search, then link each headline to the news detail operation by story id.
- Build a series hub page for a tour or league whose news tab lists headlines and intros, with an empty-state message ready for a series that returns no stories.
- Run a scheduled job that stores the story ids seen per series and flags new ids, so a newsletter or alert highlights only fresh tournament coverage.
- Compare editorial attention across several series by counting stories per seriesId and grouping them by storyType, to see which tournaments attract previews, features and reports.
Frequently asked questions
What does the series news operation return?
It returns the news stories for one series. 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 seriesId?
Use the id field returned by the series list or series archives operations. The default value 3636 is the sample id supplied with the parameter notes, so check in your own series response which tournament it maps to before labelling it in your interface.
Can I page through older series stories?
The supplied evidence documents only the seriesId 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.
Does lastUpdatedTime tell me when the newest story was published?
Not reliably. In the example lastUpdatedTime is a larger number than every pubTime shown, so it looks like a page-level timestamp rather than a story date. The unit of both fields is undocumented, so verify them before using them for sorting or freshness checks.
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 series with no news?
The evidence does not say. Treat a missing or empty storyList as a normal outcome, because coverage depends on the series, and show an empty state instead of treating it as an error.