List all cricket news story categories with IDs
View all Cricket Live Scores, Scorecards & Stats API endpoints →Returns the catalog of cricket news story categories. The operation takes no path, query or header parameters, so one request returns the whole list. No live probe was recorded, so the response description comes from a supplied source example that parses as a complete JSON object but is unverified. The example is an object with a single `storyType` array. Each entry has an integer `id`, a `name` string and a `description` string. The example lists 15 categories, including News (id 1), Editor's Picks (2), Editorial (3), Interviews (4), Specials (5), Reports (6), Previews (7), Statistics & Analysis (8), Live Blogs (10), Tour Diaries (13), Match Features (18), Features (19), Social Tattle (20), Premium Editorials (21) and Pulse (25). The ids are not contiguous, which is why they should be read from the response instead of being guessed. Use an id from this list when you call the news list by category operation. The set of categories can change over time, so confirm the current list against a live response.
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/news-get-categories No parameters required. Click Query to call the API.
API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/news-get-categories?key=<API_KEY>'
Query Result
Use Cases
- Generate category navigation from the available category records rather than maintaining a guessed enum in the front end.
- Resolve a category identifier before requesting its latest articles through the news list by category operation.
- Populate a filter dropdown on a cricket reading app so fans can switch between interviews, previews, reports and live blogs.
- Map category ids to labels in an analytics job that groups published stories by editorial format for a content report.
- Validate a saved user preference by checking that the stored category id still appears in the current list before loading its feed.
Frequently asked questions
What does the categories operation return?
It returns a JSON object with a storyType array. Each entry has an integer id, a name and a description. No probe was recorded, so this shape comes from a supplied source example and is unverified.
Does the operation need any parameters?
No. It has no path, query or required header inputs from the user, and one GET returns the whole list of categories without paging.
How do I use the category id?
Take the id of the category you want from the response and pass it to the news list by category operation to retrieve that category's stories. Do not hard-code ids, since the list may change.
Which categories appear in the example?
The source example shows 15 entries: News, Editor's Picks, Editorial, Interviews, Specials, Reports, Previews, Statistics & Analysis, Live Blogs, Tour Diaries, Match Features, Features, Social Tattle, Premium Editorials and Pulse.
Are the category ids sequential?
No. In the example the ids are 1 to 8, 10, 13, 18 to 21 and 25. Build lookups from the returned values and never infer a missing id.
Is the list the same for every user and region?
The supplied evidence does not say whether the list varies by region or over time, so refresh it periodically and treat the live response as the source of truth.
Does the response include article counts or links?
Not in the source example. Entries only carry id, name and description, so use the news list operations to get stories and their counts.