McKinsey APImckinsey.com ↗
Extract article titles, author lists, publish dates, and full body text from any McKinsey.com article with one GET request.
What is the McKinsey API?
The McKinsey.com API gives developers access to 4 structured fields — title, authors, publish date, and full body text — from any McKinsey article via a single get_article endpoint. Pass a full McKinsey article URL and receive clean, plain-text content ready for downstream analysis, summarization pipelines, or research aggregation without manual copy-pasting.
curl -X GET 'https://api.parse.bot/scraper/ac9a62ce-db1a-4994-b137-54860a3d8045/get_article?url=https%3A%2F%2Fwww.mckinsey.com%2Finstitute-for-economic-mobility%2Four-insights%2Fthe-great-ownership-transfer-a-new-era-of-business-stewardship' \ -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 mckinsey-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: McKinsey article scraper — fetch and inspect a single article."""
from parse_apis.mckinsey_com_api import McKinsey, InvalidUrl
client = McKinsey()
# Fetch article by URL and access typed fields.
try:
article = client.articles.get(
url="https://www.mckinsey.com/institute-for-economic-mobility/our-insights/the-great-ownership-transfer-a-new-era-of-business-stewardship"
)
except InvalidUrl as e:
print("Bad URL:", e.message)
else:
print(article.title)
print("Published:", article.publish_date.isoformat())
print("Authors:", ", ".join(article.authors))
# Show first 200 characters of body text
print(article.body_text[:200])
print("exercised: articles.get")
Fetches a McKinsey article and returns its title, list of authors, publish date, full body text, and URLs of chart/figure/exhibit images embedded in the article. Accepts a full URL or path to any McKinsey article page. The body text is extracted from the embedded page data with HTML tags stripped. Exhibit images are extracted from the article's structured exhibit and image components (desktop versions); logos, icons, and avatars are excluded.
| Param | Type | Description |
|---|---|---|
| urlrequired | string | Full McKinsey article URL (e.g. https://www.mckinsey.com/institute-for-economic-mobility/our-insights/the-great-ownership-transfer-a-new-era-of-business-stewardship) or just the path portion starting with /. |
{
"type": "object",
"fields": {
"title": "Article headline",
"authors": "Array of author names",
"body_text": "Full article body as plain text with HTML stripped",
"publish_date": "ISO 8601 publish date",
"exhibit_images": "Array of absolute URLs for chart/figure/exhibit images embedded in the article body"
},
"sample": {
"data": {
"title": "The Great Ownership Transfer: A new era of business stewardship",
"authors": [
"Ken Yearwood",
"Shelley Stewart III"
],
"body_text": "At a glance\nA once-in-a-generation wave of ownership transitions is imminent.\nBy 2035, about six million small and medium-size businesses (SMBs) will face ownership transitions as baby boomers retire...",
"publish_date": "2026-02-26T00:00:00Z"
},
"status": "success"
}
}About the McKinsey API
What the API Returns
The get_article endpoint accepts one required parameter: url, a full McKinsey.com article URL. It returns four fields: title (the article headline), authors (an array of contributor names as strings), publish_date (in ISO 8601 format), and body_text (the complete article body as plain text with HTML tags stripped).
Endpoint Behavior
Any publicly accessible McKinsey article URL is a valid input — including those under practice area paths like /capabilities/, institute paths like /institute-for-economic-mobility/, or regional variants. The body_text field reflects the full editorial content of the article, not just an excerpt or summary. The authors array will contain zero or more names depending on what the article page attributes.
Scope and Limitations
The API covers article pages only. Structured data such as charts, embedded data tables, report downloads (PDFs), or multimedia transcripts are not reflected in the body_text field — only the readable prose content is returned. Articles behind McKinsey's registration or paywall are not accessible; only publicly viewable pages return data.
The McKinsey API is a managed, monitored endpoint for mckinsey.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when mckinsey.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 mckinsey.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 McKinsey research by topic using
titleandbody_textfor NLP classification pipelines - Track author output over time by collecting
authorsandpublish_dateacross multiple article URLs - Feed
body_textinto summarization or embedding models for internal knowledge bases - Monitor publication cadence on specific practice areas by comparing
publish_datevalues - Build citation databases that store structured article metadata including
title,authors, andpublish_date - Enrich consulting or analyst research tools with primary source text from McKinsey insights
| 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 McKinsey have an official developer API?+
What does the authors field return when an article has no byline?+
authors field returns an empty array when no author attribution is present on the article page. For articles credited to a group (such as 'McKinsey Global Institute'), the array reflects whatever name strings appear in the byline section of that page.Does the API return data from McKinsey reports, PDFs, or podcast transcripts?+
title, authors, publish_date, and body_text for standard editorial articles. PDF reports, podcast episode pages, and video transcript pages are not covered. You can fork this API on Parse and revise it to add endpoints targeting those content types.Can I retrieve a list of all recent McKinsey articles or search by topic?+
get_article endpoint requires a specific article URL as input; there is no search or listing endpoint that returns collections of articles by topic, date range, or author. You can fork this API on Parse and revise it to add a listing or search endpoint.