The Japan Times API endpoint
Lists the 60 sections linked from The Japan Times main navigation, which the headlines endpoint accepts, for example `news-japan`, `business-markets`, `sports-sumo`, `culture-film` and `community-voices`. Each entry has a `slug`, a display `name` and a section `url`.
/japantimes/sectionsReturns the 60 public sections linked from the publisher's primary editorial navigation. These values are accepted by japantimes-headlines: news-japan, news-japan-politics, news-japan-society, news-japan-crime-legal, news-japan-science-health, news-japan-explainer, news-japan-history, news-world, news-world-politics, news-world-crime-legal, news-world-science-health, news-world-society, news-asia-pacific, news-asia-pacific-politics, news-asia-pacific-crime-legal, news-asia-pacific-science-health, news-asia-pacific-society, business, business-companies, business-economy, business-markets, business-tech, sports, sports-sumo, sports-soccer, sports-baseball, sports-basketball, sports-tennis, sports-olympics, sports-more-sports, opinion, opinion-editorials, opinion-commentary, tag-geoeconomic-briefing, environment, environment-climate-change, environment-energy, environment-sustainability, environment-wildlife, environment-earth-science, life, life-travel, life-digital, life-food-drink, life-style-design, life-language, life-lifestyle, culture, culture-film, culture-books, culture-music, culture-art, culture-tv-streaming, culture-stage, culture-entertainment-news, community, community-voices, community-issues, community-how-tos, community-our-lives.
Start from the checked request: GET /japantimes/sections. Live check on 2026-10-14: 60 sections returned. Fields present in every checked item: slug, name, url.
Use a returned section value with Get The Japan Times section headlines.
| Field | Filled in, of 60 checked | Values in the sample |
|---|---|---|
| slug | 60 | |
| name | 60 | “JAPAN” and 51 other values |
| url | 60 | japantimes.co.jp |
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/japantimes/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"data": {
"sections": [
{
"slug": "news-japan",
"name": "JAPAN",
"url": "https://www.japantimes.co.jp/news/japan/"
}
]
}
}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 |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/japantimes/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"