Bloomberg Security News Scraper

What does Bloomberg Security News & Movers Scraper do?

Bloomberg Security News & Movers Scraper takes one or more Bloomberg security ids and pushes, for each one, its recent news/video story listing plus the current top movers (most active, gainers, losers) for the same market segment — one dataset row per id.

Why use Bloomberg Security News & Movers Scraper?

• Two calls in one row — news and movers, fetched in parallel per id and merged into a single dataset item
• No API key, no auth — talks directly to Bloomberg's own Android app API with no login or token required
• Fast for lists of tickers — all ids are processed concurrently
• Use cases: news monitoring for a watchlist, market-mover dashboards, feeding a downstream research or alerting pipeline

How it connects to the parent

This Actor talks directly to the same internal API the official Bloomberg Android app uses (cdn-mobapi.bloomberg.com), reverse-engineered live against a real device (Frida, bypassing dual TLS cert pinning and root detection), then independently re-confirmed by calling the API from a plain server with no device involved. Only a fixed user-agent header is required — no signature, no token, no session cookie.

This is the security-news-and-movers slice of Bloomberg All-in-One API, split out as its own focused Actor.

Input

Field	Type	Description
ids	string[]	Required. Bloomberg security ids in symbol:exchange format, e.g. aapl:us. News works for any id. Movers only returns real data for an id that is itself an index id (e.g. ccmp:ind) — see Known limitations below.
moversTemplate	string	INDEX or STOCK, applied to the movers call for every id. Default STOCK. See Known limitations below — as of this writing only INDEX (with an index id) returns real data.

Example (news for a stock, real movers data for an index):

{
    "ids": ["aapl:us", "ccmp:ind"],
    "moversTemplate": "INDEX"
}

Output

One dataset row per id:

{
    "id": "ccmp:ind",
    "news": { "stories": [{ "...": "up to 10 news/video stories" }] },
    "movers": {
        "active": [{ "...": "top active" }],
        "leaders": [{ "...": "top gainers" }],
        "laggards": [{ "...": "top losers" }]
    }
}

Known limitations

• News is capped at 10 stories, server-side. Every pagination param tried against the upstream API (limit/offset/page/count/size/pageSize/maxResults/num) was ignored — there is no working way to page past 10 results. This is a real server-side limit, not a limitation of this Actor.
• Movers behavior differs from the parent's documented claim — re-verified live on 2026-08-31. The parent Actor's client documents movers as working for template=INDEX or template=STOCK, with only COMMODITY/CURRENCY/BOND restricted. Live testing for this Actor found that has changed (or was never quite accurate): template=STOCK now returns {"restricted":true} for every id tried, including plain stock tickers like aapl:us. template=INDEX does return real data, but only when id is itself an index id (confirmed working: ccmp:ind, indu:ind, ukx:ind, dax:ind, nky:ind, rty:ind, cac:ind; confirmed 422 for aapl:us, msft:us, spx:ind, djia:ind). In short: to get real movers data today, pass an index id in ids and set moversTemplate to INDEX. This is a real, live-observed upstream behavior, not a bug in this Actor's request logic.

Pricing

Pay-per-event: $0.0035 per news-item result (FREE plan; BRONZE/SILVER/GOLD/PLATINUM/DIAMOND get automatic discounts based on your Apify plan). Billed per security id processed.