BCG APIbcg.com ↗
Retrieve BCG publication articles by slug. Returns title, authors, publish date, full body text, and exhibit/chart image URLs in one structured response.
What is the BCG API?
The BCG.com API exposes 1 endpoint — get_article — that retrieves structured data from BCG publications, returning 5 response fields: article title, author list, publish date, full body text, and URLs for embedded exhibit and chart images. Give it a slug like 2026/digital-infrastructure-playbook and get back a complete, machine-readable representation of the publication without any HTML parsing on your end.
curl -X GET 'https://api.parse.bot/scraper/57e215b8-87ec-4f93-a54e-6e9d4c91e19d/get_article?slug=2026%2Fdigital-infrastructure-playbook' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace bcg-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: BCG Article API — fetch a publication and inspect its content."""
from parse_apis.bcg_com_api import BcgComApi, ArticleNotFound
client = BcgComApi()
# Fetch an article by its URL slug (path after /publications/).
try:
article = client.articles.get(slug="2026/digital-infrastructure-playbook")
except ArticleNotFound:
print("Article not found for the given slug.")
else:
print(article.title)
print("Published:", article.publish_date)
print("Authors:", ", ".join(article.authors))
# Show a snippet of the body text
print(article.body_text[:200])
# List exhibit/chart image URLs embedded in the article
for url in article.exhibit_image_urls:
print("Exhibit:", url)
print("exercised: articles.get")
Retrieves a BCG publication article by its URL slug. Returns the article title, list of authors, publish date, full body text, and URLs of embedded chart/figure/exhibit images (excluding logos, icons, and avatars). The slug is the path portion after /publications/ in the article URL.
| Param | Type | Description |
|---|---|---|
| slugrequired | string | Article slug path after /publications/ in the BCG URL (e.g. '2026/digital-infrastructure-playbook'). |
{
"type": "object",
"fields": {
"title": "Article headline string",
"authors": "Array of author name strings",
"body_text": "Full article body text with paragraphs separated by double newlines",
"publish_date": "ISO 8601 datetime string of publication",
"exhibit_image_urls": "Array of URLs for chart/figure/exhibit images embedded in the article"
},
"sample": {
"data": {
"title": "The Digital Infrastructure Universe Continues to Expand. Here's How to Benefit.",
"authors": [
"Bora Goekbora",
"Matt Kalmus",
"Shashank Modi",
"Alex Wright",
"Clark O’Niell",
"Scott Stemberger",
"Thomas Bumberger",
"Maxime Kern"
],
"body_text": "The rules governing the ownership, valuation, management, and allocation of digital infrastructure have changed dramatically in recent years...",
"publish_date": "2026-08-03T19:22:14.661",
"exhibit_image_urls": [
"https://web-assets.bcg.com/dims4/default/6b64e8b/2147483647/strip/true/crop/3600x2035+0+0/resize/1920x1085!/format/webp/quality/80/?url=http%3A%2F%2Fboston-consulting-group-brightspot.s3.amazonaws.com%2F50%2F1a%2F9a4a8d14459393686c86e8bfe617%2Fthe-digital-infrastructure-universe-continues-to-expand-heres-how-to-benefit-ex01.png"
]
},
"status": "success"
}
}About the BCG API
What the API returns
The get_article endpoint accepts a single required parameter — slug — which is the path segment appearing after /publications/ in any BCG.com article URL. For example, passing 2026/digital-infrastructure-playbook returns the full text of that report. The body_text field delivers the complete article body with paragraphs separated by double newlines, ready for text processing or storage.
Authors, dates, and exhibit images
Each response includes an authors array of name strings and a publish_date in ISO 8601 format, making it straightforward to sort or filter articles by recency or contributor. The exhibit_image_urls array contains direct URLs to the charts, figures, and exhibit images embedded in the article body. Logos, icons, and avatars are excluded, so the array contains only substantive visual content.
Coverage scope
The API covers articles published under BCG's /publications/ URL namespace. The slug format mirrors the BCG URL structure directly, so any publication URL you find on bcg.com can be queried by extracting the path after /publications/. There is no search or listing endpoint; you need a known slug to make a request.
The BCG API is a managed, monitored endpoint for bcg.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when bcg.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official bcg.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate BCG research reports into an internal knowledge base, indexed by
publish_dateandauthors. - Extract
exhibit_image_urlsto pull charts and figures into a slide deck or research dashboard. - Monitor specific BCG publications for updates by checking
publish_dateon a schedule. - Feed
body_textinto an NLP pipeline for topic modeling or entity extraction across consulting reports. - Build a citation tool that surfaces BCG article
titleandauthorsalongside retrieved report content. - Collect structured article metadata for competitive intelligence on BCG's published research themes.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does BCG have an official public developer API?+
What exactly is in the `exhibit_image_urls` array?+
Can I search or list BCG articles without already knowing a slug?+
Does the API return appendices, footnotes, or downloadable PDF content?+
body_text, authors, title, publish_date, and exhibit_image_urls. Appendices, footnotes, and linked PDF files are not part of the current response shape. You can fork it on Parse and revise it to add those fields if the source exposes them.How should the slug be formatted for articles with nested paths?+
/publications/, preserving any subdirectory structure. For the URL bcg.com/publications/2026/digital-infrastructure-playbook, the correct slug is 2026/digital-infrastructure-playbook.