Bloomberg Premium Article Scraper

What does Bloomberg Premium Article Scraper do?

Bloomberg Premium Article Scraper takes one or more Bloomberg internal article/story ids and pushes the full article body — structured paragraph/image components, byline, word count — one dataset row per article, plus a single batch summary row (title/thumbnail for the same ids, useful for hydrating feed cards).

It talks directly to the same internal API the official Bloomberg Android app uses (cdn-mobapi.bloomberg.com), reverse-engineered via a real device + Frida (bypassing the app's dual TLS cert pinning and root-detection), then independently re-confirmed by calling the API directly with no device involved. No Bloomberg account, no API key, no scraping setup. This is the article-detail slice of Bloomberg All-in-One API, split out as its own focused Actor.

Why use Bloomberg Premium Article Scraper?

Confirmed live: full article bodies are returned even for articles flagged premium: true. Bloomberg's Android app gates certain stories behind a client-side paywall UI ("You've reached your free article limit" / "Get the story behind the story when you subscribe"), but the premium boolean in the API response is just a flag — it does not gate server-side access at all. The parent Actor's reverse-engineering work confirmed this live: GET /stories/{id} returns the complete, 2000+ word structured body regardless of the premium value. This is a real, confirmed restriction bypass in Bloomberg's own API design, not a bug or an assumption.

• Full article text, every time — byline, word count, and all structured paragraph/image components, for premium-flagged articles included
• Batch summary in the same run — one extra storiesBulletin call returns lightweight title/thumbnail data for the whole id set, useful for hydrating feed/module cards without fetching every full body
• No account needed — every read request works fully anonymously, only a fixed user-agent header is required
• Use cases: full-text archival and search indexing, sentiment/NLP pipelines over premium financial news, monitoring specific tickers' coverage without a Bloomberg Terminal subscription

How it connects to the parent

This Actor reuses only the GET /stories/{id} and GET /stories/bulletin logic proven live by Bloomberg All-in-One API — no new endpoints, fields, or headers were invented. See the parent Actor for the full surface (securities, quotes, financials, search, home feed, media, live TV).

Input

Field	Type	Description
articleIds	string[]	Required. Bloomberg internal article/story ids, e.g. TKAK8NT9NJLU00. Get one from a type: "article" story in a security's news listing or search results (see the parent Actor).

Example:

{
    "articleIds": ["TKAK8NT9NJLU00", "TKALBTT0G1KW00"]
}

Output

One dataset row per article id, plus one final batch summary row:

{
    "id": "TKAK8NT9NJLU00",
    "article": {
        "success": true,
        "title": "...",
        "byline": "...",
        "wordCount": 549,
        "premium": false,
        "components": [{ "role": "p", "parts": [{ "role": "text", "text": "..." }] }]
    }
}

{
    "bulletin": { "...": "batch title/thumbnail summary for all requested article ids" }
}

Known limitations

• Only the article-body and batch-summary endpoints — securities, search, home feed, and media are separate concerns handled by the parent Bloomberg All-in-One API.
• Article ids must be obtained externally (from a news listing, search result, or Bloomberg URL) — this Actor does not discover ids on its own.

Pricing

Pay-per-event: $0.0120 per article result (FREE plan; BRONZE/SILVER/GOLD/PLATINUM/DIAMOND get automatic discounts based on your Apify plan). Billed per article id processed, plus one additional article charge for the batch summary/bulletin row.