Docs menu
Harvard Business Review API endpoint
HBR Topic Archive API
Returns the newest public Harvard Business Review articles on one topic archive page. topic is a "<group>/<slug>" value -- see hbr-categories for the full known value space.
GETapiKey1 credit/requestHarvard Business Reviewhbr.topicResponseDoc
Harvard Business Review/hbr/topicEndpoint facts
- Method
- GET
- API path
- /hbr/topic
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Harvard Business Review
- Response schema
- #/definitions/hbr.topicResponseDoc
How this endpoint behaves
Query parameter: required topic, a "<group>/<slug>" value from hbr-categories, e.g. subject/strategy, industry/healthcare-sector, or geography/europe.
Returns the newest public Harvard Business Review articles on one topic archive page: title, URL, description, authors, and whether the piece originally appeared in the print magazine (from_magazine).
Sampled response
- Request, 14 Oct 2026
- GET /hbr/topic?topic=subject%2Fstrategy
- Items in items
- 5
- Fields filled in every checked item
- 4
- Fields empty in some or all items
- 1
| Field | Filled in, of 5 checked | Values in the sample |
|---|---|---|
| title | 5 | “Do You Know What Your Customers Value?” and 4 other values |
| url | 5 | hbr.org |
| description | 5 | “Not according to the data. Here’s how to fix that.” and 4 other values |
| authors | 5 | median 2 entries |
| from_magazine | 1 | true in 1 of 1 |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| topic | string | Yes | Harvard Business Review topic slug | subject/strategy | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/hbr/topic?topic=subject%2Fstrategy" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"topic": "subject/strategy",
"items": [
{
"title": "Example fixture open strategy article",
"url": "https://hbr.org/2026/09/example-fixture-open-strategy-article",
"description": "A fixture description of the open strategy article.",
"authors": [
"Jamie Fixture"
],
"from_magazine": false
}
]
},
"msg": "OK"
}Request schema
No body schema
Response schema
#/definitions/hbr.topicResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | hbr.TopicResponse | No | ||||
| data.items | array | No | ||||
| data.items[].authors | array | No | ||||
| data.items[].description | string | No | ||||
| data.items[].from_magazine | boolean | No | ||||
| data.items[].title | string | No | ||||
| data.items[].url | string | No | ||||
| data.topic | string | No | ||||
| msg | string | No | OK |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/hbr/topic?topic=subject%2Fstrategy" \
-H "x-api-key: $CRAWLORA_API_KEY"