Docs menu
Forbes API endpoint
Forbes editorial sections API
Lists the current public Forbes navigation taxonomy, including business, money, innovation, leadership, lifestyle, Forbes Vetted, Advisor, Health, and their public subsections. Article promos, account surfaces, games, video-only links, and external hosts are excluded.
GETapiKey3 credits/requestForbesforbes.categoriesResponseDoc
Forbes/forbes/categoriesEndpoint facts
- Method
- GET
- API path
- /forbes/categories
- Auth
- apiKey
- Credits
- 3 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- Forbes
- Response schema
- #/definitions/forbes.categoriesResponseDoc
How this endpoint behaves
Returns Forbes's live public navigation taxonomy. The response is the discovery source for the section parameter accepted by GET /api/v1/forbes/headlines; it includes the current business, money, innovation, leadership, lifestyle, Vetted, Advisor, Health, Asia, and nested public navigation paths.
Parameters:
x-api-keyheader: required API key.
The endpoint excludes article and promotional /sites/ links, account-only surfaces, game/video-only links, external hosts, and links that are not part of the public section navigation. Taxonomy values are live and may change as Forbes updates its menu.
Live monitoring
- Monitored request
- GET /forbes/categories
- Checks passed, 7 days to 14 Oct 2026
- 100%
- Median response time
- 1.84 s
Sampled response
- Request, 14 Oct 2026
- GET /forbes/categories
- Items in sections
- 143
- Fields filled in every checked item
- 3
- Fields empty in some or all items
- 1
| Field | Filled in, of 143 checked | Values in the sample |
|---|---|---|
| name | 143 | “Breaking News” and 137 other values |
| path | 143 | “/news/” and 142 other values |
| url | 143 | forbes.com |
| parent | 140 | “/search/” and 14 other values |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/forbes/categories" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"name": "Business",
"path": "/business/",
"url": "https://www.forbes.com/business/",
"parent": ""
},
{
"name": "Markets",
"path": "/business/markets/",
"url": "https://www.forbes.com/business/markets/",
"parent": "/business/"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/forbes.categoriesResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | forbes.CategoriesResponse | No | ||||
| data.sections | array | No | ||||
| data.sections[].name | string | No | ||||
| data.sections[].parent | string | No | ||||
| data.sections[].path | string | No | ||||
| data.sections[].url | string | No | ||||
| msg | string | No | OK |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 429 | Too Many Requests | #/definitions/app.Response |
| 500 | Internal Server Error | #/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/forbes/categories" \
-H "x-api-key: $CRAWLORA_API_KEY"