Cnbc News Feed Scraper avatar

Cnbc News Feed Scraper

Pricing

from $1.20 / 1,000 news item chargeds

Go to Apify Store
Cnbc News Feed Scraper

Cnbc News Feed Scraper

Get news feed, trending, and breaking-news content from Cnbc. Talks directly to CNBC's own mobile app API, no login needed. Split from the mature, published cnbc-all-in-one-api for a focused, single-purpose workflow.

Pricing

from $1.20 / 1,000 news item chargeds

Rating

0.0

(0)

Developer

Romy

Romy

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

24 days ago

Last modified

Categories

Share

What does CNBC News Feed Scraper do?

CNBC News Feed Scraper pulls CNBC's news section feeds, trending news/videos, breaking news alerts, special reports, and the "most popular" rail for an article — all in a single batch run — and pushes one self-describing row per feed to the dataset.

It talks directly to the same internal GraphQL backends the official CNBC Android app uses (webql.cnbcfm.com, the native app backend, plus webql-redesign.cnbcfm.com, the website backend, for the most-popular rail), reverse-engineered by live MITM capture against a real device — real Apollo-style persisted-query hashes captured live, never guessed. No CNBC account, no API key, no scraping setup. This is the news-feed slice of CNBC All-in-One API, split out as its own focused Actor covering /news, /trending, /breaking-news, /special-reports, and /most-popular.

Why use CNBC News Feed Scraper?

  • Real, live CNBC data — the same feeds the app's Home screen, Trending tab, and breaking-news banner show, straight from CNBC's own backend
  • One run, many feeds — request any combination of section feeds, trending news/videos, breaking news, special reports, and a most-popular rail in a single call, each landing as its own clearly-labeled dataset row
  • No account needed — every read here works fully anonymously, confirmed by inspecting real captured request headers (no auth token, no cookie)
  • Use cases: news aggregation, market-moving-headline monitoring, media research, building a finance news dashboard

Input

FieldTypeDescription
sectionIdsinteger[]CNBC numeric section ids for /news, e.g. [105230142] (the app's Home feed default). One dataset row per id.
sectionCountintegerItems to fetch per section id. Default 30.
trendingstringnews | videos | both — pull the trending feed(s).
trendingCountintegerTrending news entries to fetch. Default 13. News side only.
trendingStartPeriodstringTrending videos time window. Default 2h. Videos side only, no confirmed enum of other values.
trendingSortBystringTrending videos sort order. Default engaged_minutes. Videos side only.
includeBreakingNewsbooleanPull the current breaking-news alert(s). Default false.
breakingNewsProductstringBreaking news product scope. Default web.
includeSpecialReportsbooleanPull the current special reports list. Default false.
specialReportsPageSizeintegerSpecial reports page size. Default 30.
mostPopularArticleIdintegerIf set, also pulls the "most popular" rail shown on that article's page.

At least one of sectionIds, trending, includeBreakingNews, includeSpecialReports, mostPopularArticleId must be set, or the run fails fast with a clear error.

Example:

{
"sectionIds": [105230142],
"trending": "both",
"includeBreakingNews": true,
"includeSpecialReports": true
}

Output

One dataset row per requested feed, each labeled with a type field so the dataset stays self-describing even when mixing feed types in one run:

{
"type": "news",
"sectionId": 105230142,
"data": { "...": "CNBC's raw sectionsEntries payload" }
}
{
"type": "trending-news",
"data": { "...": "CNBC's raw mostPopularEntries payload" }
}

Other rows: { "type": "trending-videos", "data": ... }, { "type": "breaking-news", "data": ... }, { "type": "special-reports", "data": ... }, { "type": "most-popular", "articleId": ..., "data": ... }.

Known limitations

  • trendingStartPeriod and trendingSortBy are passthrough values captured live from one real app session — there's no in-app UI to enumerate every valid option, so treat non-default values as best-effort.
  • mostPopularArticleId is required to fetch the most-popular rail — its behavior when omitted was not confirmed live, so it isn't offered as an optional global rail here.
  • Full article bodies, video assets, TV schedule, market quotes, and other CNBC endpoints are separate spin-off Actors — this one is feed-listing only. See CNBC All-in-One API for the full endpoint set.

Pricing

Pay per event. Charged news-item ($0.002 on the FREE plan) once per dataset row pushed — one per section, trending list, breaking-news pull, special-reports pull, or most-popular rail. See the Actor's Pricing tab for current rates.