Docs menu
Investopedia API endpoint
Investopedia sections API
Returns the full Investopedia section inventory (43 news, investing, banking, personal finance, economy, and reviews sections), each with a slug, display name, and public listing URL. Use a returned slug as the section parameter on GET /investopedia/headlines.
GETapiKey1 credit/requestInvestopediapublicnews.sectionsResponseDoc
Investopedia/investopedia/sectionsEndpoint facts
- Method
- GET
- API path
- /investopedia/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Investopedia
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns every section slug accepted by
investopedia-headlines's section parameter,
each with a display name and its public listing URL. The inventory is
Investopedia's own site navigation (43 sections, confirmed 2026-09-24):
- News:
news,markets-news,company-news,earnings-reports,certificates-deposit-news,mortgage-rates,economic-news,political-news,cryptocurrency-news,live-markets-news,personal-finance-news - Investing:
investing,stocks,cryptocurrency,bonds,etfs,options-and-derivatives-trading,commodities,trading,financial-technology-and-automated-investing,brokers,fundamental-analysis - Banking:
banking,savings-accounts,certificate-of-deposits,money-market-account,checking-accounts - Personal finance:
personal-finance,retirement-planning,student-loans,personal-loans,budgeting-and-savings,mortgage,credit-and-debt,taxes,insurance,financial-literacy-resource-center - Economy:
economy,government-and-policy,monetary-policy,fiscal-policy,economics - Reviews:
financial-product-reviews
Sampled response
- Request, 14 Oct 2026
- GET /investopedia/sections
- Items in sections
- 43
- Fields filled in every checked item
- 3
| Field | Filled in, of 43 checked | Values in the sample |
|---|---|---|
| slug | 43 | |
| name | 43 | “News” and 42 other values |
| url | 43 | investopedia.com |
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/investopedia/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"slug": "markets-news",
"name": "Markets News",
"url": "https://www.investopedia.com/markets-news-4427704"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.sectionsResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.SectionsResponse | No | ||||
| data.sections | array | No | ||||
| data.sections[].name | string | No | ||||
| data.sections[].slug | string | No | ||||
| data.sections[].url | string | No |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/investopedia/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"